docs: rewrite weak Ask AI callout prompts and remove devkey routing prompt

Audited all 19 [!ASKAI] callouts by firing each against the prod
/docs/ask endpoint and grading the response. Five callouts produced
low-value answers (page paraphrase, dangling "this" referent, or AI
admitting it lacked the information); one was a duplicate.

- guide/integration/devkey: remove vue-router prompt (AI replied "I
  don't have information about this")
- guide/tooling/vuetify-cli: reframe analyze prompt around output +
  team sharing rather than the leading "migration planning" framing
- guide/tooling/ai-tools: shift llms.txt prompt to agent configuration
  (the comparison table directly above the callout already covers
  llms.txt vs llms-full.txt)
- guide/fundamentals/composables: replace generic when-to-use prompt
  with a concrete Selection -> createSelection conversion request
- guide/fundamentals/building-frameworks: fix dangling "this" referent
  by naming createSingle + useProxyRegistry explicitly
- guide/essentials/using-the-docs: replace duplicate createSelection
  vs createGroup prompt with composable-discovery question

Author: johnleider

apps/docs/src/pages/guide/essentials/using-the-docs.md

@@ -440,7 +440,7 @@ The documentation uses callout boxes to highlight important information:
 
 > [!WARNING] Cautions and common mistakes to avoid.
 
-> [!ASKAI] What's the difference between createSelection and createGroup?
+> [!ASKAI] How do I find the right composable for what I'm building?
 
 > [!TOUR] using-the-docs
 

apps/docs/src/pages/guide/fundamentals/building-frameworks.md

@@ -198,7 +198,7 @@ Accordion with expand/collapse-all using `createGroup` and tri-state support.
 
 :::
 
-> [!ASKAI] How does this compare to v0's built-in Tabs component?
+> [!ASKAI] How does building a Tabs UI manually with createSingle and useProxyRegistry compare to v0's built-in Tabs component?
 
 ## Pattern B: Component Wrappers
 

apps/docs/src/pages/guide/fundamentals/composables.md

@@ -51,7 +51,7 @@ selection.select('a')
 > [!TIP]
 > Components and composables are interchangeable. Every component uses a composable internally—you can always drop to the composable for more control.
 
-> [!ASKAI] How do I choose between composables and components for my use case?
+> [!ASKAI] Show me how to convert a Selection component usage to createSelection while keeping the same behavior.
 
 ## Quick Reactivity Note
 

apps/docs/src/pages/guide/integration/devkey.md

@@ -159,5 +159,3 @@ Once DevKey is running locally, explore the pieces it relies on:
 | Build your own components on top of v0 | [Building Frameworks](/guide/fundamentals/building-frameworks) |
 | Customize the theme | [Theming](/guide/features/theming) |
 | Add SSR | [Nuxt](/guide/integration/nuxt) |
-
-> [!ASKAI] How do I add a new page to DevKey with vue-router?

apps/docs/src/pages/guide/tooling/ai-tools.md

@@ -33,7 +33,7 @@ v0 provides machine-readable documentation files following the [llms.txt](https:
 | <a href="/llms-full.txt" target="_blank" class="v0-link whitespace-nowrap">llms-full.txt↗</a> | {{ llmsStats.llmsFull.sizeFormatted }} | Complete documentation | Deep understanding, code generation |
 | <a href="/SKILL.md" target="_blank" class="v0-link">SKILL.md↗</a> | ~5KB | Patterns & anti-patterns | Claude Code, Cursor, Windsurf |
 
-> [!ASKAI] When should I use llms.txt vs llms-full.txt?
+> [!ASKAI] How do I configure my AI agent to consume llms-full.txt?
 
 ## Usage
 

apps/docs/src/pages/guide/tooling/vuetify-cli.md

@@ -308,7 +308,7 @@ Use `--reporter json` to integrate with CI/CD pipelines or custom tooling:
 vuetify analyze --reporter json --output report.json
 ```
 
-> [!ASKAI] How can I use the analyze command to plan a Vuetify migration?
+> [!ASKAI] What does the analyze command output and how do I share the report with my team?
 
 ### upgrade