Gsx Vrf Approved
Release a GSD `checkpoint:human-verify` gate: resolve the Plan number (e.g. Phase 4.4) or Task number (e.g. Task 4.4.3; inferred from context / STATE.md if blank), validate it is an un-released checkpoint:human-verify gate, then reply the `<resume-signal>` it requires (usually 'approved') to unblock GSD. Locate→validate→reply only; no edits, no SUMMARY, no commit. Invoke when the user finished a…
Devops Best Practices
容器化与部署的工程规范。涵盖 Dockerfile 多阶段与非 root、K8s/Kustomize/Helm 的探针与安全上下文、凭据不入库、docker compose 的 profile 与健康检查、CI 流水线的事件作用域与 tag 策略、process-compose 的进程生命周期。在编写或审查 Dockerfile、docker-compose.yml、process-compose.yml、CI 流水线配置、K8s 清单、Helm chart、部署脚本时使用——尤其是新增服务、调整探针、处理镜像 tag 与环境差异、或往仓库里加任何含凭据的配置时。
Doc Writing Best Practices
中文技术文档的写作规范。涵盖中西文混排的空格与标点、标题层级与代码块标注、表格与列表的取舍、以及"写清为什么"和"示例可直接抄用"的内容要求。在编写或修改 README、设计文档、运维手册、变更说明、注释块等任何面向人阅读的中文技术文档时使用——尤其是产出 Markdown 文件、写提交说明、或整理已有文档时。
Product Spec
管理产品功能规范——功能清单、交互逻辑、以及 Flyway 式版本化的新增与变更记录，产出可直接喂给 Claude Design、v0、Figma Make、Lovable 等 AI 设计工具的规范文件。规范落 .product/spec/<产品线>/，V 链（V1__baseline、V2__xxx）记录演进，合成的 CURRENT.md 是喂设计工具的唯一入口。在用户说「建产品功能规范」「写功能规格」「记录这次产品变更」「生成给设计工具的规范」「同步 CURRENT.md」「product-spec」时使用，也用于新产品线初始化规范、或规范与实现漂移需要核对时。
Gsx Add Todo
Capture an idea, task, or issue surfaced mid-session as a structured todo — thin alias that hands off to /gsd:capture (default add-todo mode). Invoke when the user says 'add a todo', 'capture this as a todo', 'gsx-add-todo', 'remember to fix X later', 'log this for later work', or drops a task-shaped aside that isn't worth interrupting current work for.
Gsx Vrf Autorun
Auto-run every `<how-to-verify>` step of a GSD `checkpoint:human-verify` task (PLAN.md): background tasks for cold-start, Playwright MCP for web E2E (≤10 retries/step), curl for APIs, self-seed+test; skip un-judgeable steps; summary in conversation. Verify-only — never fix/release/write files. Arg = task # (4.4.1) or Plan # (4.4 / Plan 4); inferred from context/STATE.md if blank. Invoke: 'auto-ve…
Gsx Plan Phase
Docs-grounded front-door to /gsd:plan-phase that splits its native Research→Plan into two explicitly-gated calls: FIRST a Context7-grounded research pass (/gsd:plan-phase --research-phase N, which spawns gsd-phase-researcher and writes RESEARCH.md) with a MANDATORY Context7 gate — every library/SDK capability, API limit, version difference, framework configuration, DB dialect, or CLI usage the ph…
Gsx Uat Planfix
Docs-grounded batch-fix of a GSD Phase's acceptance Gaps via /gsd:plan-phase N --gaps then /gsd:execute-phase N --gaps-only, with a MANDATORY Context7 gate that always runs before planning — every Gap whose root cause turns on external technology behavior (library/SDK capability, API limit, version difference, framework configuration, DB dialect, CLI usage) is checked against current docs and the…
Spec Triage
为**已有代码的存量项目**整顿编码规范：勘察代码库取证、只就推断不了的事访谈、再把每条约定按加载成本分诊到 CLAUDE.md / 通用 skill / .claude-rules / 项目文档四层，并检测既有规范与代码库的漂移。在用户说「给这个项目建规范」「整顿 CLAUDE.md 和 rules」「规范和代码对不上了」「检查规范漂移」「spec-triage」时使用，也用于规范文件膨胀到该拆分时。空仓或刚跑完脚手架的新项目改用 spec-setup。
Gsx Uat Autorun
Auto-run every test case under `## Tests` of a GSD Phase's HUMAN-UAT.md / UAT.md and write results back live — background tasks for cold-start smoke, Playwright MCP for web E2E, curl for APIs, self-seed and test; set each result (pass/issue/skipped/blocked) + note, skip undecidable ones with a reason, update Summary, write Gaps into `## Gaps`. Test only, never fix. Arg is the Phase number (inferr…
Gsx Uat Quickfix
Fix acceptance Gaps from both *-VERIFICATION.md (auto-verify; frontmatter status: gaps_found + gaps: list / ### Gaps Summary) and *-UAT.md / *-HUMAN-UAT.md ## Gaps (verify-work) one by one via /gsd:quick: resolve Phase number (inferred from context / STATE.md if blank), Gap name (e.g. GAP-1 / VERIFY-1; all open Gaps if blank) and an optional --discuss flag (run every Gap's /gsd:quick as /gsd:quic…
Gsx Replan Phase
Thin front-door to /gsd:plan-phase N --reviews — replans a GSD Phase by folding cross-AI review feedback (REVIEWS.md, produced by /gsd:review or /gsx-plan-review) back into PLAN.md. Use after a plan has been peer-reviewed and you want the critique incorporated — 'replan with the review feedback', 'fold Codex's comments into the plan', 'redo Phase 3's plan addressing the reviews', 'incorporate REV…
Gsx Uat Phase
Run conversational UAT on a built Phase — thin alias that hands off to /gsd:verify-work. Invoke when the user says 'UAT', 'verify', 'verify Phase', 'run UAT', 'gsx-uat-phase', 'accept this Phase', 'acceptance test'.
To Md
>-
Frontend Ui Best Practices
React + shadcn/ui 后台管理系统的界面与交互规范。涵盖表单校验时机与错误呈现、弹窗抽屉的状态重置与破坏性操作确认、列表分页与表格对齐、日期数字格式、图标与提示的一致性、模块 README 文档要求。在编写、审查或重构前端页面时使用——尤其是做表单、列表页、弹窗抽屉、删除等破坏性操作、或调整界面文案与格式时。
To Requirements
将用户口述、聊天记录或提供的原始需求与上下文方案，澄清并整理成项目根目录的 REQUIREMENTS.md。固定按「项目定位与核心能力、产品交付矩阵、产品功能调研、技术实现参考」四段结构输出；区分需求、约束与参考方案，对未提及、含糊或冲突的信息逐项向用户确认，确认完整后再保存文件。在用户说「把需求整理成 REQUIREMENTS.md」「记录原始需求」「把口述需求落盘」「补全需求文档」「to-requirements」时使用，也用于按同一结构更新已有 REQUIREMENTS.md。
Gsx Code Review
Review + auto-fix on a GSD Phase's changed source — equals /gsd:code-review {N} --fix --all. Arg is the Phase number (inferred from context / STATE.md last completed phase if blank). Invoke when the user says 'code review Phase X', 'review and auto-fix Phase X', 'run code-review --fix', 'gsx-code-review'. Reviews the changed source itself (bug/security/quality) — unlike gsx-uat-planfix / gsx-uat-…
Gsx Add Backlog
Park an idea that isn't ready for active planning into the ROADMAP.md backlog (999.x numbering) — thin alias that hands off to /gsd:capture --backlog. Invoke when the user says 'add this to the backlog', 'park this idea', 'gsx-add-backlog', 'not now but later', or wants to note something out-of-sequence without committing to a phase.
Gsx Vrf Review
Summarize what a GSD checkpoint:human-verify round changed across frontend / backend / database, and surface frontend-only patches that should have landed in backend/DB (field validation, enum/code zh↔en mapping, defaults, uniqueness, masking, permission visibility), interviewing the user per risk. Diagnostic only — no edits, no executor, no commits, no file writes. Invoke explicitly at a round's…
Gsx Debug
Diagnose-first debugging front-door: run /gsd:debug --diagnose to get a root-cause report (diagnose only, no fix), then — whenever the root cause touches library behavior, version differences, framework configuration, or CLI usage — MANDATORY-consult Context7 for current docs before proposing anything, produce one or more concrete fix plans with trade-offs, and finally interview the user twice: w…
Spec Setup
为新项目从零建立编码规范：先访谈定项目形态（Web fullstack / 后端服务 / 小程序 / Android / iOS / CLI·SDK / 桌面应用，支持一仓多形态），再从既有 *-best-practices skill 继承技术栈与规范、缺口走推荐、主框架经 Context7 定版本，最后只固化已裁决的少量约束并显式留白与记录复查触发点。在用户说「新项目建规范」「初始化 CLAUDE.md 和 rules」「刚建的仓库要定规范」「选型定了帮我固化下来」「spec-setup」时使用。存量项目（已有实质业务代码）改用 spec-triage。
Gsx Uat Newtest
Append one new Test to the `## Tests` section of a GSD Phase's HUMAN-UAT.md / UAT.md (produced by /gsd:verify-work): parse the user's Test description, fill missing fields (title / expected / result) in one AskUserQuestion pass; auto-continue Test numbering from max N (never reused), follow the file's existing single- or multi-line `expected:` style, and bump frontmatter `updated:` + `## Summary`…
Design To Code
将高保真设计/原型（HTML + React JSX，通常来自 Claude Design、Artifacts、Figma 导出或其他设计工具）还原为生产级 React 前端代码，技术栈为 Vite + React + TypeScript + Tailwind CSS + shadcn/ui，包管理器使用 pnpm。当用户提到"还原原型"、"把设计变成代码"、"把原型转成 React"、"把 Claude Design 的设计变成代码"、"实现这个设计稿"、"高保真还原"、"design to code"、"prototype to React"、"convert mockup/design to React"、"restore prototype"，或任何把高保真设计/原型/mockup 转成可投产前端代码的需求时，主动使用此 skill。即使用户没有明确说"还原"，只要场景是"我有…
Spring Boot Best Practices
Spring Boot 3 + Java 21 + MyBatis Plus 项目的编码规范与架构纪律。涵盖分层依赖、国密 SM2/SM3/SM4、MyBatis Plus 实体与主键策略、多方言数据库迁移、R/RList/RPage 响应包装、DTO 职责边界、命名约定、模块 README 文档要求。在编写、审查或重构 Spring Boot 后端代码时使用——尤其是新增 Controller/Service/Mapper、定义 Entity 或 DTO、写数据库迁移、处理加解密与签名、或设计 API 契约时。
Gsx Quick
Front-door for one small problem that runs /gsd:quick --discuss — a lightweight discussion phase before planning (surfaces assumptions, clarifies gray areas, captures decisions) instead of quick's default fast path. Use whenever the user wants a single scoped problem fixed with GSD guarantees and wants it thought through rather than blind-fixed: 'gsx-quick', 'fix this properly', 'discuss this sma…
Gsx Fast
Multi-round-iterate-then-final-squash fast workflow for one trivial change (lighter than gsx-quick: /gsd:fast runs inline — no subagents, no PLAN/SUMMARY, no .planning/quick/{id}/ dir): call /gsd:fast to do the one-liner inline, ask via AskUserQuestion whether to keep tweaking; if yes call /gsd:fast again (no resume — each round is independent inline) until satisfied; finally squash all commits i…
Gsx Discuss Phase
Docs-grounded front-door to /gsd:discuss-phase: run the phase-context discussion that produces CONTEXT.md, but with a MANDATORY Context7 gate — whenever a gray area being discussed turns on a technology choice, a library/SDK capability, an API limit, a version difference, framework configuration, a DB dialect, or CLI usage, consult Context7 for current docs BEFORE posing the question or recording…
Gsx Uat Newgap
Append one new Gap to the `## Gaps` section of a GSD Phase's HUMAN-UAT.md / UAT.md (produced by /gsd:verify-work): parse the user's Gap description, fill missing fields (severity / linked Test number / artifacts) in one AskUserQuestion pass; auto-continue numbering from max GAP-N (following the file's existing Markdown-heading or YAML-list style), and bump frontmatter `updated:` + Summary `open_g…
Gsx Ui Spec
Wrap /gsd:ui-phase to generate a UI design contract (UI-SPEC.md) for a frontend phase, anchored screen-by-screen to the high-fidelity prototype. Use whenever the user wants to start, plan, or spec the UI/frontend work of a GSD phase — 'UI spec for phase 3', 'generate the UI design contract for phase X', 'frontend spec for Phase X', 'ui-phase 3', 'design the UI for phase X', or just a phase number…
Gsx Plan Review
Thin front-door to /gsd:review --phase N --codex — gets an independent cross-AI peer review of a GSD Phase's PLAN.md from the external Codex CLI, producing REVIEWS.md. Use after a phase is planned (PLAN.md exists) and you want a second pair of eyes before executing — 'review the plan with Codex', 'peer-review Phase 3's plan', 'cross-AI review', 'get Codex to critique this phase plan', 'plan-revie…