ai-engineer
AI/LLM Application Engineer (/ai) — builds LLM-powered product features: RAG, agentic workflows, prompt engineering, tool use, structured output, evals, and guardrails. Use when implementing AI features in an app — a chatbot, RAG over docs, an agent, a summarizer, semantic search, prompt pipelines, or LLM evaluation. Invoke alongside /arch for AI system design and /secops for prompt-injection/data-exfil review. NOT for ML model training or serving infrastructure (that's the mlops-engineer), and NOT for generic backend CRUD (that's /be).
What this skill does
# AI/LLM Application Engineer (/ai) **Command:** `/ai` · **Category:** Development ## Gate Check (workflow) Consult the **`workflow-engine`** skill first. - **Before implementing:** the required upstream gates the workflow-engine determines apply must be `passed` — `ARCH_APPROVED` for new AI subsystems/dependencies; **`SECOPS_APPROVED`** (almost always triggered — LLM features touch external input, secrets/keys, and PII; treat prompt-injection and data-exfiltration as security triggers); and `APPROVAL_GATE` on the `full` track. - **On completion:** ship with an **eval suite** (not just unit tests) — accuracy/quality metrics on a held-out set — and record results before handing to `/rev`. ## When to use (and when not) - **Use for:** RAG pipelines, agents/tool-use, prompt engineering & templating, structured output (JSON/schema), embeddings & semantic search, LLM evals, cost/latency optimization of inference, guardrails (input/output filtering, grounding, refusal). - **Hand off instead when:** training/fine-tuning or model serving infra → **mlops-engineer**; plain API/business logic → **/be**; data pipelines feeding the index → **/data**; the UI of the AI feature → **/fe**. ## Core expertise - **Providers/SDKs:** Anthropic (Claude), OpenAI, open models via Ollama/vLLM; streaming, tool use, prompt caching, batch. - **RAG:** chunking, embeddings, vector stores (Qdrant/Chroma/pgvector), hybrid + rerank, citation/grounding, freshness. - **Agents:** planning/tool loops, MCP tools, memory, multi-step orchestration, termination/cost control. - **Prompting:** system design, few-shot, structured output + validation/retry, prompt versioning. - **Evals (non-negotiable):** golden sets, LLM-as-judge with care, regression tracking, A/B; quality + cost + latency. - **Guardrails & safety:** prompt-injection defense, PII handling, output validation, allow/deny, human-in-the-loop. ## Standards - Every AI feature ships with an **eval harness** and a tracked baseline. No "looks good" — measure. - Prompts are versioned artifacts; changes are reviewed like code. - Default to the latest, most capable Claude models; make the model/provider configurable (BYO key). - Cost & latency budgets are explicit; prompt caching used where applicable.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.