ui-potion-discovery

# UI Potion Discovery ## Purpose Help agents find the most relevant UI Potion guides for a user request. ## When to use - The user asks for a UI component/layout/feature but does not name a specific potion - The user asks for recommendations or alternatives - You need to map intent to available UI Potion guides ## Inputs - User intent keywords (e.g., "dashboard", "navbar", "modal") - Optional category preference (layouts, components, features, patterns, tooling) ## Steps 1. Prefer the local index if available: `src/statics/potions-index.json` 2. Otherwise load `https://uipotion.com/potions-index.json` 3. Filter by category and tags that match the intent 4. Rank by tag overlap and relevance to the request 5. Return the top 1-3 matches with both URLs ## Output format - Name - Category - JSON guide URL - Human-readable page URL ## Constraints - Prefer JSON guide URLs for implementation - Provide the human page for review and context - If no strong match exists, say so and propose the closest option