UI image to code methodology. Use when the user provides a UI screenshot, design mock, app screen, dashboard image, mobile screen, web page image, or says "UIๅพ็ๆไปฃ็ ", "็ๅพๅ้กต้ข", "ๆ นๆฎ่ฎพ่ฎกๅพๅฎ็ฐ", "screenshot to code", "image to code", or asks Codex to implement a frontend from an image. Requires a UI image plus a design size when available, forces clarification for every uncertainty, then reconstructs the UI in the target project or a runnable standalone app with browser screenshot verification and visual diff evidence.
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, functional correctness, security/reliability/performance hotspots, 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.
Primary intake for fuzzy feature/product requirements before coding; prefer this over dev-spec for requirement alignment. Use when the user says or implies: ้ๆฑ่ฟไธๆธ ๆฅ, ๅ ๅซๅไปฃ็ , ๅ ๅธฎๆๆขณ็/ๆถๆ/ๅฏน้ฝ/ๆไธไธ้ๆฑ, ๅ ้ฎๆ้ฎ้ข, ๆ็กฎ่ๅด/่พน็/้ชๆถๆ ๅ, ๅ PRD/spec/่ฎพ่ฎกๆๆกฃ, ๅธฎๆ่ฎพ่ฎก, ๅไธชๆนๆก, ่ฟไธช้ๆฑๆไนๅ, design this, scope this out. Also trigger on dev-grill-docs, grill-with-docs, ๆท้ฎ้ๆฑ, ๆท้ฎๆนๆก, ๅๆตๆนๆก, ๆฏ่ฏญๆฒๆท. Reads existing docs/code first, asks one focused question at a time, produces .claude/artifacts/designs/<feature>.md, and may update CONTEXT.md or docs/adr/ for durable terms/decisions. Does not implement code, fix bugs, or write implementation plans.
Use only after a spec or clearly scoped requirement exists and the user wants a concrete implementation plan before coding. Trigger on explicit implementation-planning requests such as ๅบไบ่ฟไธช spec ๅบ plan, ้ๆฑๅทฒ็ปๆธ ๆฅไบ็ปๅฎๆฝๆนๆก, ๆๆฏๅฎๆฝๆนๆก, ๅบไธช plan, ๅไธชๅฎๆฝๆนๆก, plan this, make a plan, consensus plan, ralplan. If the user says ๅไธชๆนๆก, ็ปๆไธชๆนๆก, ๆไนๅ่ฟไปถไบ, ๅธฎๆ่ฎพ่ฎก, or the requirement is still fuzzy, route to dev-grill-docs first. 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.
Compatibility alias for dev-grill-docs spec-only mode. Assists dev-grill-docs by running its spec-only path. Use only when the user explicitly says dev-spec, asks to preserve an old dev-spec workflow, or explicitly wants spec-only output without CONTEXT.md / ADR updates. For natural requirement-alignment requests such as ๅ ๅธฎๆๆขณ็้ๆฑ, ๅธฎๆ่ฎพ่ฎก, ๅไธชๆนๆก, spec ไธไธ, ่ฎพ่ฎกๆๆกฃ, design this, or scope this out, prefer dev-grill-docs. Do not maintain a separate workflow here: load dev-grill-docs and follow it with --spec-only.
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]`.
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.
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.