원클릭으로
codebase-design
Use for module boundaries, public APIs, ownership, abstractions, wrappers, test seams, or architecture review.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use for module boundaries, public APIs, ownership, abstractions, wrappers, test seams, or architecture review.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use for /he:plan; stage 1 readiness with Treehouse, Grill Me, owner, proof path, PASS/FAIL.
Use for UI components, design systems, atomic design, tokens, themes, hardcoded visuals, or missing design SSOT.
Use for visual PDFs: create, polish, export, verify decks, reports, proposals, one-pagers, or HTML-to-PDF.
Use for hard bugs, failing behavior, flaky tests, exceptions, regressions, or unexplained slowness before fixing.
Use for real UI E2E smoke/regression proof across web, Flutter, browser, Chrome, or device flows, with artifacts.
Interview one clear question before planning/building ideas, features, codebase maps, specs, UI flows, prototypes, or final plans.
| name | codebase-design |
| description | Use for module boundaries, public APIs, ownership, abstractions, wrappers, test seams, or architecture review. |
Use this for structural decisions, not formatting or naming polish.
Load references/deep-modules.md before proposing a new abstraction, moving
logic between modules, adding a public interface, or reviewing architecture.
Coordinate with nearby skills:
thermo-nuclear-code-quality-review toogrill-me or to-prd firsttest-quality tooPrefer deleting concepts, moving behavior to the canonical owner, and shrinking public surfaces before adding new layers.