メニュー
Use when canonical image source files (images/<harness>/Dockerfile or darkish-prelude.sh) have been edited; the local image tag must be rebuilt before any subharness dispatched into that harness will pick up the change
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use at session start in any darken-managed workspace (any repo containing `.scion/grove-id`) to prime as the host-mode orchestrator for the §7 pipeline. Loads the non-negotiables block, the routing classifier, the background-dispatch monitoring protocol, the bounded-transcript evidence rule, the 14-role roster, the escalation classifier, and the four loop primitives for playbook-driven coordination (darken dispatch / inbox / accept / state). Invoke whenever the operator types a task and the workspace is darken-managed.
Use in any darken-managed workspace (any repo containing `.scion/grove-id`) when you would normally dispatch a subagent via the Agent tool but you are operating as the host-mode orchestrator. Translates the muscle memory into subharness dispatch, maps task shapes to roles, frames the task in caveman-standard with a status-publishing recipe and a fixed milestone vocabulary, and reads worker output back via the bounded-transcript protocol.
Constitution-driven specification flow mounted by planner-t4. Activates when an agent must drive the full ratification pipeline: constitution review, spec.md authoring, plan.md production, and tasks/ decomposition. Use when operating under the specify CLI, when a feature requires formal ratification before implementation, or when producing structured spec artifacts for downstream worker harnesses.
Multi-skill bundle mounted by planner-t3. Activates when a design session must scaffold an architecture that satisfies both Hipp zero-config reliability principles and Ousterhout deep-module complexity reduction. Triggers on requests to design libraries, data layers, or system modules where simplicity, embeddability, and minimal cognitive load must all be balanced together.
Use when designing libraries, modules, or data layers that must be simple, reliable, and self-contained. Use when choosing between embedded vs server-based solutions. Use when reviewing code for unnecessary complexity, dependencies, or configuration. Triggers on requests involving zero-config design, embedded systems, long-term maintainability, or first-principles thinking.
Use when designing modules, classes, APIs, or system architecture. Use when reviewing or refactoring code for complexity. Use when choosing between implementation approaches. Triggers on requests involving abstraction design, interface simplicity, information hiding, or reducing cognitive load.
| name | substrate-image-discipline |
| description | Use when canonical image source files (images/<harness>/Dockerfile or darkish-prelude.sh) have been edited; the local image tag must be rebuilt before any subharness dispatched into that harness will pick up the change |
The local Docker image tags (local/darkish-claude:latest, local/darkish-codex:latest, local/darkish-gemini:latest, local/darkish-pi:latest) are NOT automatically rebuilt by goreleaser at release time. They are local artifacts of make -C images <harness>. If the canonical source under images/<harness>/ changes and the operator forgets to rebuild, every subsequent subharness dispatch into that harness uses the STALE image — even after a brew upgrade of darken itself.
Core rule: after editing any file under images/<harness>/, rebuild that harness's image before dispatching the affected role.
images/<harness>/darkish-prelude.shimages/<harness>/Dockerfileimages/Makefile or anything under images/<harness>/bin/git checkout of a branch that has substrate-source changes you have not yet builtmake -C images claude # darkish-claude:latest
make -C images codex # darkish-codex:latest
make -C images gemini # darkish-gemini:latest
make -C images pi # darkish-pi:latest
Each target is independent. Build only the ones whose source changed.
Before dispatching a role, sanity-check the image has the expected fix baked in. Pattern: pull a known string out of the prelude inside the image:
docker run --rm --entrypoint cat local/darkish-codex:latest \
/usr/local/bin/darkish-prelude.sh | grep -c "<expected-marker>"
If the count is wrong, rebuild.
local/darkish-codex:latest. The codex prelude on feat/v0.1.17 had the pre-clone pre-pop fix from B4, but the local image was last built on main (which lacked it). Container errored at Git clone failed: git init failed:. Required scion stop, branch checkout, make -C images codex, re-spawn.darken setup reports "OK darken images built" if any tag exists at all (regardless of how stale).| Edited | Rebuild | Verify |
|---|---|---|
images/claude/darkish-prelude.sh | make -C images claude | docker run --rm --entrypoint cat local/darkish-claude:latest /usr/local/bin/darkish-prelude.sh | grep <marker> |
images/codex/Dockerfile | make -C images codex | image exists with recent CreatedAt |
| Worktree out of sync (e.g. on main, code lives on feat branch) | git checkout feat/<branch> first | run rebuild from that branch |
make -C images all may not exist; build per-harnessdarken doctor to detect stale images — it currently checks existence, not freshness