changed title for clarity

Author: soheimam

…ilderkits/onchainkit/guides/ai-guide.mdx …onchainkit/guides/ai-prompting-guide.mdxapps/base-docs/docs/pages/builderkits/onchainkit/guides/ai-guide.mdx renamed to apps/base-docs/docs/pages/builderkits/onchainkit/guides/ai-prompting-guide.mdx apps/base-docs/docs/pages/builderkits/onchainkit/guides/ai-guide.mdx renamed to apps/base-docs/docs/pages/builderkits/onchainkit/guides/ai-prompting-guide.mdx

@@ -1,5 +1,5 @@
 ---
-title: 'Developer's Guide to Effective AI Prompting'
+title: 'AI Prompting Guide'
 description: Learn practical AI prompting techniques to enhance your coding workflow and get better results from AI coding assistants.
 author: sohey
 ---
@@ -25,10 +25,10 @@ This is why providing relevant context upfront is crucial \- the AI can only wor
 
 To get the most out of AI assistants:
 
-1. **Prioritize relevant information**: Focus on sharing the most important details first
-2. **Remove unnecessary content**: Avoid pasting irrelevant code or documentation
-3. **Structure your requests**: Use clear sections and formatting to make information easy to process
-4. **Reference external resources**: For large codebases, consider sharing only the most relevant files
+1. **Prioritize relevant information**: Focus on sharing the most important details first.
+2. **Remove unnecessary content**: Avoid pasting irrelevant code or documentation.
+3. **Structure your requests**: Use clear sections and formatting to make information easy to process.
+4. **Reference external resources**: For large codebases, consider sharing only the most relevant files.
 
 For larger projects, create and reference a central documentation file that summarizes key information, rather than repeatedly explaining the same context.
 
@@ -72,12 +72,12 @@ A comprehensive instructions file helps AI tools understand your project better.
 ```
 Create a detailed instructions.md file for my project with the following sections:
 
-1. Overview: Summarize the project goals, problem statements, and core functionality
-2. Tech Stack: List all technologies, libraries, frameworks with versions
-3. Project Structure: Document the file organization with explanations
-4. Coding Standards: Document style conventions, linting rules, and patterns
-5. User Stories: Key functionality from the user perspective
-6. APIs and Integrations: External services and how they connect
+1. Overview: Summarize the project goals, problem statements, and core functionality.
+2. Tech Stack: List all technologies, libraries, frameworks with versions.
+3. Project Structure: Document the file organization with explanations.
+4. Coding Standards: Document style conventions, linting rules, and patterns.
+5. User Stories: Key functionality from the user perspective.
+6. APIs and Integrations: External services and how they connect.
 ```
 
 :::info
@@ -111,8 +111,6 @@ Here's the relevant code:
 [paste your code]
 ```
 
-###
-
 ### **Ask for Iterations**
 
 Start simple and refine through iterations rather than trying to get everything perfect in one go.
@@ -121,10 +119,10 @@ Start simple and refine through iterations rather than trying to get everything
 
 ```
 Let's approach this step by step:
-1. First, implement a basic version of [feature] with minimal functionality
-2. Then, we'll review and identify areas for improvement
-3. Next, let's add error handling and edge cases
-4. Finally, we'll optimize for performance
+1. First, implement a basic version of [feature] with minimal functionality.
+2. Then, we'll review and identify areas for improvement.
+3. Next, let's add error handling and edge cases.
+4. Finally, we'll optimize for performance.
 
 Please start with step 1 now.
 ```
@@ -148,10 +146,10 @@ I'm implementing a swap component with OnchainKit. Here's the relevant LLMs.txt:
 @https://docs.base.org/builderkits/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
+1. Swap from Base USDC to Base ETH.
+2. Handles connection states properly.
+3. Includes error handling.
+4. Follows best practices for user experience.
 ```
 
 ### **Component Integration Example**
@@ -162,10 +160,10 @@ Based on this documentation, please show me how to implement a wallet connector
 I need to implement a new feature in my project.
 
 1. Shows the connected wallet's balance of our {ERC20 token}.
-2. It Updates when the balance changes.
-3. Handles loading and error states appropriately
-4. Follows our project's coding standards
-5. Update our instructions.md to reflect this new implementation
+2. It updates when the balance changes.
+3. Handles loading and error states appropriately.
+4. Follows our project's coding standards.
+5. Update the instructions.md to reflect this new implementation.
 
 ```
 

apps/base-docs/sidebar.ts

@@ -78,8 +78,8 @@ export const sidebar: Sidebar = [
                 link: '/builderkits/onchainkit/guides/using-ai-powered-ides',
               },
               {
-                text: 'AI Guide',
-                link: '/builderkits/onchainkit/guides/ai-guide',
+                text: 'AI Prompting Guide',
+                link: '/builderkits/onchainkit/guides/ai-prompting-guide',
               },
             ],
           },