Explore AI Agent Skills & Claude Prompts

Use ONLY when the user explicitly wants end-to-end guided workflow through the dev-skills toolchain. Triggers on phrases like "用 dev-auto / 帮我串起来 / 从需求到 commit / 完整跑 / end to end / 走完整流程 / 下一步该做什么 / what's next". Reads `.claude/artifacts/{designs,plans,fixes}/` and `.design-context.md` existence to detect current phase (no deep parsing) and recommends next step across dev-design-context, dev-grill-docs, dev-plan, dev-tdd, dev-fix, dev-verify, dev-code-review, dev-commit-writer, and dev-finish. Does NOT invoke other skills, write code, or produce artifacts. Optional arguments — `[slug]`; `--status [slug]`; `--next [slug]`; `--recover [slug]`.

dev-code-review

Use when reviewing uncommitted or staged git changes before commit. Trigger on: 帮我 commit, 我要 commit, commit 一下, 准备提交, pre-commit, 提交前检查, 看下这次修改, commit 前看一下, I want to commit, let's commit, review my changes. Checks conventions, functionality, wiring, comments, and dead code; emits a commit message only when READY. Does not mutate the working tree. Route to dev-commit-writer only when the user explicitly asks to skip review or wants only a commit message.

dev-commit-writer

Use only when the user explicitly asks for a commit message without review. Trigger on: 帮我写 commit message, 给个 commit message, 生成 commit message, 这次 commit message 怎么写, write a commit message, skip review, 跳过 review, 我自审过了, only message, 只要 message. Writes a message from the current git diff in repository style. Does not review code quality or mutate the working tree; ambiguous commit requests like 帮我 commit route to dev-code-review.

dev-design-context

Use as a one-time design setup for UI, product, landing-page, or brand-heavy work. Scans the project for design context, asks only the UX questions that cannot be inferred, then writes persistent design guidelines to .design-context.md. Does not implement features or review code.

dev-finish

Use when implementation and verification are complete and the user needs to finish a development branch by merging locally, creating a PR, keeping the branch, or discarding work. Applies after tests pass and code review is ready.

dev-fix

Use when the user reports a bug, broken behavior, regression, failing test, or asks to investigate/root-cause/debug. Trigger on: 修个 bug, 这个 bug, 排查一下, 复现, 这个错怎么回事, 为什么 X 不工作, debug, RCA, fix this bug, investigate, reproduce. Guides root-cause debugging: reproduce with a failing test, list hypotheses, trace backward, fix only the confirmed cause, verify red-green-red, and leave a regression test. Does not symptom-patch or write commit messages.

dev-grill-docs

Use as the main intake for fuzzy or under-specified feature work before coding. Trigger on: dev-grill-docs, grill-with-docs, grill with docs, 拷问需求, 拷问方案, 压测方案, 术语沉淀, 帮我设计, 写个方案, spec 一下, design this, scope this out. Reads existing docs/code first, asks one focused question at a time, produces the spec artifact at .claude/artifacts/designs/<feature>.md, and may also update CONTEXT.md or docs/adr/ for stable domain language and durable decisions. Does not implement code, fix bugs, or write implementation plans.

dev-plan

Use when a spec or scoped requirement exists and the user wants a concrete implementation plan before coding. Trigger on: 出个 plan, 做个实施方案, 怎么做这件事, 给我个方案, plan this, make a plan, consensus plan, ralplan. Produces a RALPLAN-DR plan with principles, decision drivers, viable options, ADR, and Planner-Architect-Critic validation. Does not gather requirements, fix bugs, review code, or write code.

dev-spec

Compatibility alias for dev-grill-docs spec-only mode. Use when the user explicitly says dev-spec, spec 一下, 设计文档, 帮我设计, design this, or scope this out and expects a feature intent artifact at .claude/artifacts/designs/<feature>.md. Do not maintain a separate workflow here: load dev-grill-docs and follow it with --spec-only, preserving dev-spec trigger compatibility for existing docs and downstream tools.

dev-tdd

Use when implementing a feature, refactor, direct hotfix, or scoped behavior change before writing production code. For bug reports that need root-cause investigation, use dev-fix instead; dev-fix already owns failing regression tests.

dev-verify

Use before claiming work is complete, fixed, ready, passing, or before handing off to commit review, PR, merge, or branch cleanup. Requires fresh verification commands and evidence before any success claim.

redesign-existing-projects

star 1

Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.