super-skills

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.

End-to-end testing workflow for critical user flows using browser automation. Use when validating full-stack behavior, regression-prone journeys, or release gates for visible product functionality.

Exa-backed search workflow for web, company, and technical discovery tasks. Use when broad external search is needed and the result should be ranked and summarized efficiently.

Scoped-edit workflow that restricts edits to an approved directory boundary. Use during debugging or sensitive refactors to prevent unrelated changes from leaking into the session.

Frontend architecture guidance for component structure, state, accessibility, and UI behavior. Use when building or reviewing interfaces and interaction flows in modern web apps.

Combined safety workflow that applies destructive-command warnings and scoped edit boundaries together. Use for high-risk tasks where both command safety and edit containment matter.

Repository health workflow for build, lint, type, test, and security status. Use to assess codebase readiness, run quality gates, or summarize engineering health before major changes or release.

Root-cause-first debugging workflow. Use for bugs, regressions, stack traces, production issues, or any case where the real failure path must be understood before edits are proposed.

MCP design guidance for tools, resources, transports, validation, and trust boundaries. Use when cataloging MCP servers, building new servers, or reviewing MCP-related risk and integration choices.

Architecture planning workflow for implementation-ready technical plans. Use for system design, API shape, data flow, edge cases, and testable execution sequencing before code changes begin.

Product framing workflow that merges founder, design, and wedge-definition review. Use for early product strategy, problem reframing, user-value sharpening, and design-direction planning before implementation starts.

Browser-centric QA workflow for user flows, regressions, and bug reproduction. Use for end-to-end checking, report-only QA, or iterative test-and-fix loops around visible product behavior.

Findings-first code review workflow focused on correctness, regressions, trust boundaries, and missing tests. Use for diffs, pull requests, pre-merge review, or any request to check code quality.

Security review workflow for app code, secrets handling, MCP risks, and agentic attack surface. Use when code touches auth, user input, external tools, secrets, file access, or high-trust automation.

Release workflow that ties verification, review, documentation updates, and PR preparation together. Use when work is ready to package, summarize, and move toward merge or deployment.

Test-driven development workflow for features, bug fixes, and refactors. Use to force test-first implementation with explicit coverage expectations and clear red-green-refactor sequencing.

Verification workflow for build, lint, types, tests, and security checks. Use after meaningful code changes and before release or review handoff.

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.

End-to-end testing workflow for critical user flows using browser automation. Use when validating full-stack behavior, regression-prone journeys, or release gates for visible product functionality.

Exa-backed search workflow for web, company, and technical discovery tasks. Use when broad external search is needed and the result should be ranked and summarized efficiently.

Scoped-edit workflow that restricts edits to an approved directory boundary. Use during debugging or sensitive refactors to prevent unrelated changes from leaking into the session.

Frontend architecture guidance for component structure, state, accessibility, and UI behavior. Use when building or reviewing interfaces and interaction flows in modern web apps.

Combined safety workflow that applies destructive-command warnings and scoped edit boundaries together. Use for high-risk tasks where both command safety and edit containment matter.

Repository health workflow for build, lint, type, test, and security status. Use to assess codebase readiness, run quality gates, or summarize engineering health before major changes or release.

Root-cause-first debugging workflow. Use for bugs, regressions, stack traces, production issues, or any case where the real failure path must be understood before edits are proposed.

MCP design guidance for tools, resources, transports, validation, and trust boundaries. Use when cataloging MCP servers, building new servers, or reviewing MCP-related risk and integration choices.