ワンクリックで
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.