Remove OnchainKit and MiniKit references from base-chain docs (#1206)

* Remove OnchainKit and MiniKit references from base-chain docs
* removed appchains reference as well

* remove snippet reference

* remove reference link

* remove appchains reference

Author: hughescoin

docs/base-account/basenames/basenames-wagmi-tutorial.mdx

@@ -86,7 +86,6 @@ In your project folder, create the apis directory and add a basenames.tsx file:
 
 <Note title="What's happening in the code?">
 `convertReverseNodeToBytes()`: This function is creating the reverse node so we can look up a name given an address. Each address gets its own reverse record in our registry that's created in a deterministic way.
-You can see the implementation of `convertReverseNodeToBytes()` on [GitHub](https://github.com/coinbase/onchainkit/blob/main/packages/onchainkit/src/identity/utils/convertReverseNodeToBytes.ts)
 `BasenameTextRecordKeys`: Metadata (e.g., github, twitter, etc.) are stored as text records so we can look them up based on the enum key.
 </Note>
 

docs/base-chain/quickstart/deploy-on-base.mdx

@@ -167,7 +167,7 @@ This will return the initial value of the Counter contract's `number` storage va
 
 ## Next Steps
 
-- Use [Onchainkit](https://onchainkit.com) to connect your frontend to your contracts! Onchainkit is a library of ready-to-use React components and Typescript utilities.
+- Use [wagmi](https://wagmi.sh) or [viem](https://viem.sh) to connect your frontend to your contracts.
 - Learn more about interacting with your contracts in the command line using Foundry from our [Foundry tutorial](/learn/foundry/deploy-with-foundry).
 
 

docs/base-chain/quickstart/why-base.mdx

@@ -43,7 +43,6 @@ Some of the tooling that makes this possible:
 
 - **Base Account:** Onboard your users quickly and securely. Users never have to worry about seed phrases again.
 - **Coinbase Developer Platform:** Access specialized developer services for onchain development, such as free node software, sponsored transactions, and other tools to help you fine-tune your application.
-- **OnchainKit:** A React component library (TypeScript) to help you build apps faster.
 - **Basenames:** More than just human-readable text to replace an address—Basenames are the front page to a builder’s onchain profile.
 - **Verifications:** Enable unique experiences for users with verified credentials.
 

docs/base-chain/tools/base-products.mdx

@@ -3,28 +3,15 @@ title: "Base Products"
 ---
 
 <CardGroup cols={2}>
-  <Card title="OnchainKit" icon="square-1" href="https://docs.base.org/onchainkit/getting-started">
-    Ready-to-use, full-stack components to make building onchain faster and
-    easier.
-  </Card>
-  <Card title="MiniKit" icon="square-2" href="https://docs.base.org/base-app/build-with-minikit/overview">
-    Build mini apps to increase your distribution and find traction.
-  </Card>
-  <Card title="AgentKit" icon="square-3" href="https://docs.cdp.coinbase.com/agent-kit/welcome">
+  <Card title="AgentKit" icon="square-1" href="https://docs.cdp.coinbase.com/agent-kit/welcome">
     A toolkit for building onchain AI agents.
   </Card>
-  <Card title="Smart Wallet" icon="square-4" href="https://docs.base.org/smart-wallet/quickstart">
+  <Card title="Smart Wallet" icon="square-2" href="https://docs.base.org/smart-wallet/quickstart">
     A single sign-on for the open internet. No app or
     extension required.
   </Card>
-  <Card title="Appchains" icon="square-5" href="https://docs.cdp.coinbase.com/base-appchains/introduction/welcome">
-    Scale your app with a dedicated chain on Base.
-  </Card>
-  <Card title="Paymaster" icon="square-6" href="https://docs.cdp.coinbase.com/paymaster/introduction/welcome">
+  <Card title="Paymaster" icon="square-3" href="https://docs.cdp.coinbase.com/paymaster/introduction/welcome">
     Account Abstraction endpoints to send transactions and sponsor gas.
   </Card>
-  <Card title="OnchainTestKit" icon="square-7" href="https://docs.base.org/onchainkit/guides/testing-with-onchaintestkit">
-    End-to-end testing framework for blockchain applications.
-  </Card>
 </CardGroup>
 

docs/snippets/prompt-library.mdx

@@ -38,15 +38,6 @@ Cursor Rules allow you to provide consistent context to Cursor AI, making it mor
 
 4. Save your rules file and Cursor will apply these rules to its AI suggestions
 
-### Setting Up an OnchainKit Project
-To create a new OnchainKit project:
-```
-npm create onchain@latest
-```
-After creating your project, prompt to generate comprehensive documentation for your new OnchainKit project.
-
-
-
 ## Creating Project Documentation
 A comprehensive instructions file helps AI tools understand your project better. This should be created early in your project and updated regularly.
 
@@ -72,14 +63,12 @@ Example: ❌ "Help me with my code"
 
 **Ready-to-Use Prompt:**
 ```
-I'm working on a onchainkit project using [frameworks/libraries]. I need your help with:
+I'm working on a project using [frameworks/libraries]. I need your help with:
 
 1. Problem: [describe specific issue]
 2. Current approach: [explain what you've tried]
 3. Constraints: [mention any technical limitations]
 4. Expected outcome: [describe what success looks like]
-
-Here's the relevant documentation @https://docs.base.org/onchainkit/llms.txt
 ```
 
 **Ask for Iterations**
@@ -97,27 +86,6 @@ Let's approach this step by step:
 Please start with step 1 now.
 ```
 
-## Working with OnchainKit
-### Leveraging LLMs.txt for Documentation
-The OnchainKit project provides optimized documentation in the form of LLMs.txt files. These files are specifically formatted to be consumed by AI models:
-1. Use OnchainKit Documentation
-2.Find the component you want to implement
-3.Copy the corresponding LLMs.txt url
-4.Paste it into your prompt to provide context
-
-Example LLMs.txt Usage:
-```
-I'm implementing a swap component with OnchainKit. Here's the relevant LLMs.txt:
-
-@https://docs.base.org/onchainkit/llms.txt
-
-Based on this documentation, please show me how to implement a wallet connector that:
-1. Swap from base usdc to base th
-2. Handles connection states properly
-3. Includes error handling
-4. Follows best practices for user experience
-```
-
 **Component Integration Example**
 
 Ready-to-Use Prompt for Token Balance Display:
@@ -211,7 +179,7 @@ I notice you suggested two approaches. To clarify, I'd prefer to use the first a
 - Break complex tasks into steps: Iterative approaches often work better for complex problems
 - Request explanations: Ask the AI to explain generated code or concepts you don't understand
 - Use formatting for clarity: Structure your prompts with clear sections and formatting
-- Reference documentation: When working with specific libraries like OnchainKit, share relevant documentation
+- Reference documentation: When working with specific libraries, share relevant documentation
 - Test and validate: Always review and test AI-generated code before implementing
 - Build on previous context: Refer to earlier parts of your conversation when iterating
 - Provide feedback: Let the AI know what worked and what didn't to improve future responses