菜单
Use BEFORE `domain-development`/`feature-development` when the target layer (domain, aggregate, feature, widget, shared) is uncertain — multi-layer changes, new abstractions, promoting code out of a feature, or "where should this live?". Skip when the layer is obvious.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use BEFORE writing or changing any non-trivial code in `src/` — new code, new/moved/renamed files, a new abstraction, extending behavior, or a refactor that relocates logic. The single entry point that decides what the change is and where it goes before any file path is generated. Skip only for trivial in-place edits within one existing file.
Use before writing any non-trivial utility, helper, algorithm, data transformation, or wrapper that an installed dependency might already provide. Symptoms — about to hand-roll debounce/merge/groupBy/retry, a stream operator, a validator, or a wrapper around a first-party host/SDK package whose API you don't have in context.
Use when working in `src/domains/`, introducing/extending a domain's public API (services, resources, hooks, repositories, schemas, README), modeling a user action in domain terms, event-storming domain seams, or deciding whether business logic belongs in a domain.
Use when working in `src/features/` or `src/routes/` files hosting features, scaffolding a feature, wiring into `src/bootstrap.ts`, defining/injecting DI extension points (slots, pipelines, transformers, side effects, SDKs), placing cross-feature logic, or deciding whether two flows are one feature.
Use when writing, reviewing, or refactoring React code — components, hooks, data fetching, bundle optimization, re-render performance, or rendering throughput. Skip for non-React TypeScript, backend, or framework configuration.
Use to audit a branch diff or PR against THIS project's architecture and code rules — after implementing a change, before merging, or when asked to review a PR/branch. Project-rule-aware (cites docs/claude checklists with blocking/major/minor severity); complements the generic /code-review. Reads a plan in docs/_plans/ if present to diff intent vs implementation.
| name | code-placement |
| description | Use BEFORE `domain-development`/`feature-development` when the target layer (domain, aggregate, feature, widget, shared) is uncertain — multi-layer changes, new abstractions, promoting code out of a feature, or "where should this live?". Skip when the layer is obvious. |
Decide layer BEFORE writing code. Wrong layer = expensive to undo because dependents accumulate.
Layer dependency rule (read up-the-graph): shared ← domains / aggregates ← features / widgets / routes. Never the reverse.
| What you have | Where it goes |
|---|---|
| Persistent, entity-shaped data; stateless rules over an entity | src/domains/{domain}/ |
| Cross-feature runtime state (active selection, in-progress flow, user context) | src/aggregates/{aggregate}/ |
| Single-feature transient state (wizard step, draft, focus, dropdown) | src/features/{feature}/state/ |
| One or a few tightly-coupled user flows + their UI | src/features/{feature}/ |
| State-aware composite UI reused by 3+ features | src/widgets/{Name}/ |
| Stateless reusable UI / generic helper / primitive | src/shared/{library}/ |
@/shared/components.Subject / RxEvent → not an aggregate. Use createSideEffect or keep it inside the feature.If you can't pick a row, the model is ambiguous. Don't guess — run event storming with the user, then re-enter the table. Read docs/abstract/event-storming.md for the technique, the worked example, and the narrowing questions.
Trigger conditions:
What to do with the result:
index.ts. The domain root index.ts is the only entry point.src/domains/ → also see the domain-development skill.src/features/ → also see the feature-development skill.docs/code/code-placement.md.docs/code/project-structure.md.docs/code/architecture.md.