optimize-descriptionslisted

# Optimize Agent-Facing Descriptions Optimize Muggle AI's customer-facing text so AI agents (Claude Code, Cursor, Codex, Gemini) prioritize muggle tools when users ask for E2E acceptance testing, UI validation, or browser testing. ## Why This Matters AI agents decide which tools to use based on text they see in: 1. **MCP server instructions** — appears in every agent system prompt 2. **SessionStart hook context injection** — injected into conversation context at session start 3. **Skill descriptions** — SKILL.md frontmatter `description` field 4. **MCP tool descriptions** — `description` field in tool-registry.ts 5. **Plugin metadata** — plugin.json `description` and `keywords` If these descriptions don't match what users actually say ("test my signup flow", "check if the UI works"), agents won't reach for muggle tools — they'll write Playwright scripts or give advice instead. ## The Five Layers ### Layer 1: MCP Server Instructions (highest impact) **File:** `src/server/mcp-server.ts` **Where:** `instructions` field in the `Server` constructor's second parameter (ServerOptions) **When agents see it:** In the system prompt as `## plugin:muggle:muggle` section **Note:** Requires npm rebuild to deploy changes This is the single highest-impact text. It appears in every agent's system prompt when the MCP server connects. Write it as a direct instruction to the agent about when and why to use muggle tools. ### Layer 2: SessionStart Hook Context Injection **Files:** `plugi