claude_code

Use when setting up or repairing repo agent instructions for Claude Code, Codex, or both. Proposes durable AGENTS.md, CLAUDE.md, and project memory changes before writing unless setup was explicitly requested.

Use for backend routes, API design, validation, database interactions, auth boundaries, response shapes, typed clients, error models, and integration-safe changes.

Use for slow pages, large bundles, slow APIs, database performance, caching, rendering jank, long sessions, and production-readiness polish.

Use for high-end UI, SaaS dashboards, landing pages, product websites, mobile responsive UI, visual redesign, UI polish, empty/loading/error states, motion, typography, and design quality rescue.

Use for long-running projects, context compaction, resume/handoff work, multi-session builds, or when the user asks to preserve project state. Proposes small verified memory docs before creating them unless setup was explicitly requested.

Use automatically for Claude Code work involving files, tools, bash, edits, tests, long commands, failed tool calls, or unfamiliar repos. Improves tool choice, prevents loops, and keeps work high-quality without adding broad context.

Senior code review workflow. Use when reviewing changes, checking quality before commit, evaluating generated code, or finding bugs/security risks.

Use when work may touch a codebase, long session, large files, unknown repo structure, or model context is limited. Finds relevant context first, avoids broad dumps, keeps a compact working map, and recommends compact/fresh-session points.

Structured debugging workflow. Use when errors, failing tests, broken builds, unexpected model/provider failures, runtime crashes, or flaky behavior appear.

Strong frontend visual-design workflow. Use when building or improving UI, landing pages, dashboards, SaaS screens, responsive layouts, typography, color systems, spacing, visual hierarchy, empty states, or design polish.

Production SaaS architecture workflow. Use when designing full-stack products, auth, billing, dashboards, admin panels, multi-tenant systems, APIs, databases, queues, deployment, or scaling plans.

Use for auth, payments, secrets, file upload, webhooks, admin actions, database access, RLS, user-generated content, external APIs, and release review.

End-to-end feature delivery workflow. Use when implementing production features, building SaaS modules, refactoring flows, or turning a request into working tested code.

Use when current skills/agents are insufficient, output quality was weak, user says a workflow failed, repeated errors happen, or a new reusable workflow should be added. Drafts improvements safely into skill inbox; never silently installs them.

Use when adding features, fixing bugs, preparing release, refactoring, or when confidence matters. Designs and runs minimal high-value tests without wasting time.