using-superspec
Use at the start of any conversation - establishes how to find and use SuperSpec skills. Combines development discipline with spec-driven documentation.
发现 工具与集成 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Use at the start of any conversation - establishes how to find and use SuperSpec skills. Combines development discipline with spec-driven documentation.
Use when implementation is complete, all tests pass, and you need to integrate the work. Guides completion by presenting structured options for merge, PR, or cleanup.
Use when implementing any feature or bugfix, before writing implementation code. Each Scenario in Specs becomes a test case following RED → GREEN → REFACTOR cycle.
Use after verification passes to archive completed changes. Applies delta specs to main specs and moves change to archive.
Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification, not performative agreement or blind implementation.
Use when you have a written implementation plan to execute in a separate session with review checkpoints. Alternative to subagent-driven development for batch execution.
Use after completing tasks to review code for quality and spec compliance. Two-stage review: Spec Compliance first, then Code Quality.
Use after implementation is complete to verify that code matches specifications. Ensures every Requirement is implemented and every Scenario has a corresponding test.
Fast-track from idea to implementation-ready plan in one session. Combines brainstorm (4 phases) + validate + plan into a single flow. Use for small-to-medium features that don't need separate review points.
Use after specs are validated to create TDD implementation plan. Each Scenario in Specs becomes a test case in the plan. Combines bite-sized TDD tasks with spec references.
Execute Gemini CLI for AI-powered code analysis and generation. Use when you need to leverage Google's Gemini models for complex reasoning tasks.
Use before any feature work. Progressive design flow with four phases: Explore → Propose → Design → Spec Outputs: proposal.md, design.md, specs/*.md
Execute Codex CLI for code analysis, refactoring, and automated code changes. Use when you need to delegate complex code tasks to Codex AI with file references (@syntax) and structured output.
Phase execution protocol to prevent context drift during long development sessions. MUST be read at the start of each phase and referenced in the last TODO of each phase. This ensures AI maintains context acros...
External AI code review using Codex or Gemini. Reads project.yaml to determine which provider to use for frontend vs backend tasks. Includes hallucination detection to avoid blindly applying AI suggestions.
Use to validate spec documents for correctness, completeness, and consistency. Ensures specs follow SuperSpec format and are ready for implementation.
Use when about to claim work is complete, fixed, or passing. REQUIRES running verification commands and confirming output before making any success claims. Evidence before assertions, always.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. Dispatch one agent per independent problem domain for parallel execution.
Use when starting feature work that needs isolation from current workspace. Creates isolated git worktrees with smart directory selection and safety verification.
Guide for UI styling with semantic design system classes. Never use gray-* colors or arbitrary Tailwind utilities.
Guide for validating external data with Zod. Use when fetching from APIs, processing webhooks, or handling user input.
Evaluate external PR suggestions (Gemini, CodeRabbit) against project conventions. Use when asked to review or agree with external code review comments.
Enforce TypeScript type organization rules. Use when creating types, interfaces, or DTOs. All types MUST go in /types directory - never inline in components.
Enforce the internal API proxy layer pattern. Use when adding API endpoints, fetching data from backend, implementing HMAC signing, or working with lib/api/* or app/api/*.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。