agentic-workflow-designUse when the user wants to design an AI agent, multi-step LLM workflow, tool-using assistant, or automation with LLM calls — or is deciding whether they need an "agent" at all. Picks the simplest workable pattern, defines tools, control flow, guardrails, and failure handling before any code.
ai-app-securityUse when the user is building or reviewing an application that uses LLMs and needs to think about security, safety, or abuse — prompt injection, data leakage, tool permissions, untrusted documents, cost abuse, content risks. Runs a structured threat model referencing the OWASP Top 10 for LLM Applica
ai-code-reviewUse when the user has code generated by an AI assistant (or copied from one) and wants to understand it, check it, or decide whether to trust it before merging or running it. Reviews for correctness, hallucinated APIs, security, and maintainability — and makes sure the user can explain the code.
ai-evalsUse when the user needs to test or measure LLM output quality — building an eval set, writing graders, LLM-as-judge, regression testing prompts or models, or deciding whether a change made things better. Trigger on "how do I know if this prompt is better", "test my AI feature", "evals".
learning-roadmapUse when the user asks what to learn to move into AI engineering or building with AI, how to structure their learning, which skills matter, or how to build a portfolio. Builds a project-driven roadmap from the user's actual background, time budget, and goal.
llm-api-builderUse when the user is writing code that calls an LLM API or SDK — chat/messages calls, streaming, tool/function calling, structured JSON output, retries, cost and token management. Guides them to build it themselves with production habits, and checks current provider docs instead of trusting memory f
prompt-engineeringUse when the user is writing, debugging, or improving a prompt or system prompt for an LLM feature, or asks why a model output is inconsistent. Reviews prompts against a concrete checklist, proposes targeted changes, and insists on testing them against examples rather than vibes.
prototype-shipping-coachUse when the user wants to build and ship an AI prototype or side project, is stuck in tutorials or planning, or keeps expanding scope. Coaches scoping to a one-week slice, a build plan, daily check-ins, and a demo — the user builds it.
rag-basicsUse when the user wants an LLM to answer questions over their own documents or data — retrieval-augmented generation, embeddings, vector databases, chunking, "chat with my docs", or when a RAG system gives wrong or unsupported answers. Teaches a baseline-first build and how to diagnose retrieval vs.