메뉴
Shape an artefact through structured Q&A. Routes to the right sub-skill: brainstorm (new/unclear artefacts), refine (open decisions), or discover (exploration-driven artefacts like People and Ideas).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | shaping |
| description | Shape an artefact through structured Q&A. Routes to the right sub-skill: brainstorm (new/unclear artefacts), refine (open decisions), or discover (exploration-driven artefacts like People and Ideas). |
Shape an artefact through structured Q&A until it meets its type's bar.
The artefact is new or a stub. What needs to be shaped isn't clear yet. Explores the idea, writes initial content, then hands off to refine.
File: brainstorm/SKILL.md
The artefact is clear but has open decisions to work through. Decision-driven, with progress tracking.
File: refine/SKILL.md
The artefact is a discovery type (People, Ideas, Cookies, Journal Entries, Thoughts). Open-ended exploration, no decision table.
File: discover/SKILL.md
All file paths below are relative to this skill's base directory. Use the Read tool to load them — do NOT use the Skill tool.
assess/SKILL.md to set up the session (artefact, transcript, taxonomy).shaping <design name> → assess → refine (existing design with decisions)shaping + "I want to build X" → assess (creates artefact) → brainstormshaping <person name> → assess → discovershaping <stub design> → assess → brainstorm (not enough content to refine yet)Identify changed code and dispatch reuse, quality, and efficiency reviewer agents in parallel; return the raw findings list.
Review changed code for reuse, quality, and efficiency, and produce a triaged list of findings (no edits). Use after writing code, for simpler code with fewer bugs and better performance.
Provides guidance on good software design principles, with trade-off calibration, examples, and common failure modes. Applies when making decisions while writing, designing, or refactoring code, or evaluating trivial code for clarity, maintainability, and common mistakes.
Reviews code with a team against established software design principles, and returns triaged findings (no edits). Use when evaluating code, or after writing or refactoring complex code, systems or technical designs: for code that is clearer, easier to maintain, and avoids common mistakes.
Shared setup for shaping sessions. Determines if an artefact exists or needs creating, creates it if needed, starts the transcript, reads the type taxonomy. Called by the parent router or by any sub-skill invoked directly.
Review changed code for reuse, quality, and efficiency, then fix any issues found.