Use to start a new product on Cradle or to add the Cradle skeleton to an existing repository — writes cradle.json, the project-facts instruction (.apm/instructions/project.instructions.md), documents/{ddd,ai-notes,infra-design,codebase} templates, CI, and a compiling Lean executable-spec scaffold with a minimal example domain, mockup and CLI.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
node <skills>/cradle-init/scripts/init.mjs --project <Root> [--domain "<一言>"] [--dir <path>] [--backend <package>] [--only <prefix>] [--dry-run] [--force]
<skills> は cradle-core 規則のとおり（Claude Code .claude/skills / Codex .agents/skills）。<Root> は Lean のルート名前空間（大文字始まり。例: MonoWa）。lake の exe 名はその小文字。
--domain "<一言>" はプロダクトの一言（ドメインの事実なので documents/ddd/event-timeline.md の冒頭 プロダクト: 行に書く。探索役の最初の問いの出発点になる）。
敷くもの: cradle.json、.apm/instructions/project.instructions.md（このプロジェクト固有の事実。Claude Code では apm install が .claude/rules/project.md に、Codex では apm compile --single-agents が AGENTS.md に写す）、.gitignore（追記）、
.github/workflows/cradle.yml（lake build と cradle の検査を CI で回す）、documents/ddd/（5 ファイル）、documents/ai-notes/README.md、documents/infra-design/（README + 01〜04）、documents/codebase/openapi.yaml、
lean/（動く最小ドメイン「メモ」付き。lake build → CLI → モックアップ → golden がその場で通る）。既存ファイルは据え置く。
ターゲット別の設定例は置き場があるものだけ: Claude Code の許可リストの例（settings.local.json.example。.claude/ に置く）、.codex/config.toml（AGENTS.md の上限を上げる）。
--backend com.example.notes を付けると backend/ktlint-rules/（設計上の作法を検査する独自ルール 8 本）・.editorconfig・gradle.properties も敷く（backend フェーズの入口で）。
--only <prefix> --force は、そのパスで始まる骨格由来のファイルだけを敷き直す（例: Cradle を更新したあと --only lean/Main.lean --force と --only lean/mockup/server.mjs --force。Main.lean と server.mjs は骨格の持ち物で作り込まない。作り込んだ index.html は上書きしない。まだ汎用のままなら --only lean/mockup --force で UI ごと。lean/<Root>/Runtime/ はプロジェクトの持ち物なので敷き直さず、新しいファイルだけ --only で足す — 順序は docs の導入手順）。
documents/ddd/event-timeline.md の冒頭 プロダクト: 行（--domain が書く。置き場のまま（（一言で））なら ddd.mjs start --domain "<一言>" が書く）。.apm/instructions/project.instructions.md の残りの固有の事実は apm install で rules に写す（Codex は apm compile --single-agents で AGENTS.md に。apm compile は rules を書かない）。cd lean && lake build → cradle status（Lean が「ビルド済」になる）。lean/README.md のドメインの節を書く。cradle status が「骨格のサンプル」と示す）、形式化の最初のセッションで丸ごと置き換える（層の形は残す）。Prelude・Domain/{Annotations,ValueObject,Error,Entity/Note}・Application/{ActorContext,RepositoryState,ReadModel,View,Projection,UseCase/{PostNote,CloseNote,Notes}}・
Runtime/{Ids,Command,Observation,Environment,Machine,Reachable,Views,Json,Scenarios}・Laws/Properties・Main.lean（Cradle 標準プロトコル。5 cmd と external）・mockup/。
どのファイルもそのまま規約の実例で、references/lean-conventions.md（lean-domain-model スキル）が指す。
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when adding or changing REST endpoints or the OpenAPI contract — deriving endpoints from the Lean commands and views, writing documents/codebase/openapi.yaml first, then regenerating the backend controller interfaces and the frontend client.
The English summary is being prepared. Showing the original description.
Use after a backend build succeeds or whenever authentication, authorization, actor/identity handling, external service calls (IdP, JWKS, DB, clock), logging, observability, configuration or error contracts are in play — delegates to the backend-design-reviewer agent for a design-quality review of the current branch.
The English summary is being prepared. Showing the original description.
Use when it is time to make the backend follow the Lean model — regenerate Kotlin from Lean, implement the generated interfaces (UseCase, QueryService, Repository, Entity), wire every generated contract test, make the build green, then run the design and SQL reviews. Backend comes after the human confirmed the screens.
The English summary is being prepared. Showing the original description.
Use when you need the current position in the Lean spec-driven pipeline, or any deterministic check of a Cradle project — status, golden regression, Lean layer walls, regeneration impact, unslop lint, ddd cleanup. Runs the scripts under scripts/ and reports their output verbatim.
The English summary is being prepared. Showing the original description.
Use when the product owner asks where the project stands, what to do next, or which phase of the Lean spec-driven pipeline is current — runs cradle status and proposes exactly one next step.
The English summary is being prepared. Showing the original description.
Use to run or continue domain exploration with the product owner as domain expert — event storming interviews, hotspots (HS), ubiquitous language, UX review of the domain, checking or resolving open MQ/UX items, or a status summary of documents/ddd. Also use when the user starts explaining their business, purpose or workflow. Never edit documents/ddd directly; go through this skill.
The English summary is being prepared. Showing the original description.