Skip to content
cccskills
FreePublished on GitHub

infra-implement

Use for the infrastructure implementation phase after the backend follows the model — turning documents/infra-design decisions into infra/ (local container stack, production IaC), wiring cradle.json infra.up / infra.containers, adding IaC validate and image build steps to CI, and, once E2E passes, applying production once in a sandbox and recording it in the deployment table. Not for designing infrastructure (infra-design).

The English summary is being prepared. Showing the original description.

Works withTerraform
See how to install

Files included (1)

  • SKILL.md3.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

インフラ実装

設計(documents/infra-design/)を infra/ に写す。出番は 2 回: local スタックは E2E の前提、本番の apply は E2E 合格の後。 順序の確認から始める: cradle status でバックエンドが着手済か。着手済でなければ着手しない。

手順

  1. 設計を読む: documents/infra-design/ の 02_local / 03_production / 04_operations。INFRA-D をそのまま実装に写す。設計に無いものを足さない(足したくなったら infra-design スキルに戻す)。

  2. local: コンテナ(DB・backend・frontend・モック発行者)を infra/local/ に置く。cradle.json の infra.up に立てる 1 コマンド、infra.containers にコンテナ名を書く。立てて cradle doctor --local が fresh になったら、README の投入表の local を 済(日付) にする。

  3. CI: 骨格の cradle.yml に段を足す。infra/ があるときだけ動く形にする。

    infra:
      runs-on: ubuntu-latest
      steps:
        - uses: actions/checkout@v4
        - uses: hashicorp/setup-terraform@v3
          if: hashFiles('infra/prod/**') != ''
        - run: terraform -chdir=infra/prod fmt -check && terraform -chdir=infra/prod init -backend=false && terraform -chdir=infra/prod validate
          if: hashFiles('infra/prod/**') != ''
        # plan は state と資格情報が要る。持てる環境でだけ足す
        - run: docker build -t <registry>/<app>-backend:${{ github.sha }} backend
          if: hashFiles('infra/**') != ''
    

    IaC が Terraform でなければ、その道具の fmt / validate に読み替える。イメージのタグはコミット SHA。

  4. prod: E2E 合格後、サンドボックスで一度 apply する。cradle status のインフラ設計に prod に関わる未決 INFRA-Q が残っていれば apply しない。投入表の prod を 済(日付) にし、記録に詰まった箇所を 1 行。

  5. 設計への戻し: 実装で前提が変わったら README の「実装後の見直し」に事実だけを書き、設計を直す。

決めごと

  • IaC のモジュール・compose は Cradle が配らない。書き方は設計(INFRA-D)と infra 規約が決める。
  • fail-open の既定・削除保護・アラームの通知先は infra 規約のとおり。実装で緩めない。
  • 機械で確かめられるのは cradle doctor --local(local の鮮度)だけ。残りは設計と突き合わせて読む。

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

asuka1975/cradle5Updated Oct 1, 2026

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.

asuka1975/cradle5Updated Oct 1, 2026

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.

asuka1975/cradle5Updated Oct 1, 2026

cradle

Free

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.

asuka1975/cradle5Updated Oct 1, 2026

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.

asuka1975/cradle5Updated Oct 1, 2026

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.

asuka1975/cradle5Updated Oct 1, 2026

See all skills by asuka1975

Report a problem with this skill