Loading...
Loading...
Found 110 Skills
GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow (constitution, specify, clarify, plan, tasks, analyze, implement). Use when working with spec-kit CLI, .specify/ directories, or creating specifications with constitution-driven development. Triggered by "spec-kit", "speckit", "constitution", "specify", references to .specify/ directory, or spec-kit commands.
Spec-driven development orchestration with context engineering for solo developers. Prevents context rot through fresh subagent contexts and atomic task execution. Use when: starting projects, planning features, executing development phases, or when user says "gsd", "plan", "new project", "execute phase". Triggers: /gsd init, /gsd plan, /gsd execute, /gsd status, /gsd verify
Enforces spec-before-code workflow for AI-driven development. Automatically selects Spec-Kit or OpenSpec mode, triages complexity (quick/standard/thorough), recovers session context, and applies quality gates (G0-G4) with automated review loops at every stage. Use this skill whenever the user says "/super-spec", "spec first", "规范先行", or starts any feature, bugfix, or refactor — especially in projects with .spec-mode, .specify/, or openspec/ directories. Even if the user doesn't explicitly ask for spec-driven workflow, activate this skill for any non-trivial code change to prevent skipping the design phase. Orchestrates: Spec-Kit/OpenSpec (OPSX) + planning-with-files + ui-ux-pro-max (v2.0, 67 styles, 161 palettes, 13 stacks) + Superpowers (TDD, code review, verification, debugging, spec/plan review loops, subagent model selection).
(NS) Ad-hoc coding worker — bug fixes, small refactors, scripts, migrations — without full SDD. Entry priority 5: use for "just implement this", "quick fix", or concrete coding without execution-handoff (also C2 under ns-code-autonomous). Do NOT use for GitLab ISSUE_URL (ns-execution-gitlab-issue), multi-day/version scope (ns-spec-driven), diagnosis-only (ns-code-investigator), or when execution-handoff.md exists. Do NOT generate requirements/tasks/handoff.
Refactoring workflow — test coverage gate, DRY + SOLID analysis, SRP decomposition, pattern discovery, spec-driven user review, and execution planning
(NS) Create and maintain Cypress E2E tests in an independent tests-e2e/ Node package at repo root (bootstrap when missing). DRY device-aware command architecture (shared/pages/device). Use when writing or refactoring Cypress specs, custom commands, scaffolding E2E on greenfield projects, or implementing E2E tasks — not when planning E2E task markdown (ns-spec-driven references/e2e-test-task-generator.md). Read harness e2e rules when present. Mandatory discovery before writing specs.
(NS) Security/compat/a11y hygiene + Vercel Web Interface Guidelines review (headers, CSP, deps, accessibility). Use when hardening security, fixing CSP/CORS/headers, reviewing UI / checking a11y / auditing UX, or applying Web Interface Guidelines — even without saying "best practices"; also at ns-proto-creator close-out. Do NOT use for MR/SOLID review (ns-reviewer), visual redesign (ns-frontend-design), or feature implementation (ns-coder / ns-spec-driven).
Generate SDD requirements from RFCs/specs and quantitatively verify implementation conformance. spec draft → spec align → spec verify → automated validation loop with codex/claude. Operate spec-to-impl drift gates as CI checks.
Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and task lists. Triggers: "kiro", ".kiro/specs/", "feature spec", "需求文档", "设计文档", "实现计划".
Transform reverse-engineering documentation into GitHub Spec Kit format. Initializes .specify/ directory, creates constitution.md, generates specifications from reverse-engineered docs, and sets up for /speckit slash commands. This is Step 3 of 6 in the reverse engineering process.
Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and implementation task lists. Use when creating feature specs, requirements documents, design documents, or implementation plans. Triggered by "kiro" or references to .kiro/specs/ directory.
Workflow orchestrator for Spec Driven Development. Coordinates skills and tracks progress. speckit workflow, spec driven development, speckit commands.