API design guidance for resources, validation, error envelopes, pagination, and compatibility. Use when defining or reviewing HTTP APIs and service interfaces.
Backend architecture and API design guidance for service boundaries, validation, persistence, and caching. Use when building or refactoring backend flows and server-side systems.
Destructive-action warning workflow. Use when operations may delete files, rewrite git history, discard changes, or modify high-risk infrastructure and data paths.
Checkpoint workflow for capturing current state, decisions, and remaining work. Use before context switching, handing off work, or pausing a long-running task.
Shared implementation standards for maintainable, safe, and readable code. Use when writing or reviewing code to keep naming, structure, validation, and error-handling expectations consistent.
Multi-source research workflow for current topics that require citations, synthesis, and explicit confidence. Use for technical, product, market, or ecosystem investigations with evidence requirements.
Parallel execution workflow for worktrees, sub-agents, and tmux-style task orchestration. Use when independent tasks can be split safely across isolated execution lanes.
Documentation lookup workflow for current library and API behavior using primary docs and trusted references. Use when implementation depends on up-to-date APIs or version-specific behavior.