메뉴
Use when the user says: "mockup this UI", "show me what it looks like", "HTML mockup", "UI preview", or "generate a mockup". Generate self-contained HTML mockup files. Reads design/context.md if present for consistent styling.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | mine-mockup |
| description | Use when the user says: "mockup this UI", "show me what it looks like", "HTML mockup", "UI preview", or "generate a mockup". Generate self-contained HTML mockup files. Reads design/context.md if present for consistent styling. |
| user-invocable | true |
Dispatches a subagent to generate self-contained HTML mockups. The main agent resolves design context, then hands off generation entirely.
$ARGUMENTS — a description of what to mockup. If empty, ask the user what they want to mockup.
Look for design/specs/*/design.md:
Look for design context (checked in order, first match wins): design/context.md, .impeccable.md, design/direction.md. If found, note its path. If none found, proceed without — the worker uses its default aesthetic.
Launch one subagent (model: sonnet, subagent_type: general-purpose):
Generate an HTML mockup.
What to build: <user's description from $ARGUMENTS> Design context file: <path to design/context.md or equivalent, or "none"> Design doc: <path to design.md if found, or "none">
Read
${CLAUDE_CONFIG_DIR:-~/.claude}/skills/mine-mockup/worker.mdfor the complete workflow. Follow every step. Do NOT use the Skill tool — the instructions are in worker.md, not a skill.
The subagent returns the file path of the generated HTML.
Present the file path to the user. If no design/context.md exists, suggest: "Want more control over styling? Run /i-teach-impeccable to set up design tokens."
Use when the user says: "clean code check", "style review", "LLM smell check", "code hygiene", "nitpick this", "style check", "find style sins", "nitpicker review", "anal retentive review", "exhaustive style review", "no-filter style report". Dispatches three parallel stylistic checkers — llm-checker (training-bias patterns), lazy-checker (deferred debt), and nitpicker (style hygiene) — and consolidates findings into a report organized by checker with a Summary section for orchestration consumption.
Use when the user says: "review my changes", "run the reviewers", "code and integration review", "readability review", "maintainability review", "sniff test this", "WTF check", "code smells", "is this code any good", "fresh eyes on this branch", "review this directory", "check this module", "review this skill", "review these instructions". Dispatches three parallel reviewers — code, integration, and a readability pass for code; consistency, instruction quality, and writing quality for instruction files — and consolidates findings into one prioritized report.
Use when the user says: "spec this out", "help me define what I want to build", "interview me about this idea", "design this change", "write a design doc", or needs to define WHAT and HOW to build something. Proportional discovery interview + codebase investigation → design.md.
Use when the user says: "draft a plan", "create work packages", "generate WPs", "review this plan", or "check the plan". Turns a design doc into task files and validates them against a traceability-focused checklist.
Use when the user says: 'close gaps in this design', 'fill gaps in the spec', 'lightweight design review', 'gap-close this doc', 'completeness review', or wants to verify a doc has all required content before implementation.
Use when the user says: "ship it" or "commit push and PR". Commits, pushes, and creates a PR in one step.
