Use when the user asks to audit the codebase for performance issues, find unnecessary re-renders, identify wasteful network requests, look for missing caching, find eager fetches or waterfall requests, detect expensive main-thread compute, or find code-splitting opportunities. Triggers: "performance audit", "audit performance", "find perf issues", "look for unnecessary re-renders", "check for duplicate requests", "find missing caching", "perf check", "why is the app slow".
Use when the user asks to audit the codebase for AI-introduced smells, vibe-check the project, find code that needs cleanup, look for duplication / oversized components / unnecessary casts / unsynchronized state / untested behavior. Triggers: "vibe check", "vibe-check the codebase", "audit the code", "find AI smells", "what's rotten", "code health check".
Use when the user asks to plan a feature or change by breaking it into GitHub Issues for this repo's ticket tracker. Triggers: "plan this feature", "break this into tickets", "create tickets for", "draft tickets", "what tickets do we need".
Use when the user asks to work on a ticket, find the next ticket, pick up unblocked work, implement an issue, or claim a GitHub issue in this repo's ticket-driven workflow. Triggers: "work on a ticket", "what should I work on", "implement issue #N", "next ticket", "start a unit of work", "find unblocked work".