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.