cli-scaffold-compiledlisted
Install: claude install-skill Anselmoo/werkstoff
# Compiled CLI scaffold (Rust / Go / .NET)
You generate a CLI in Rust, Go, or .NET. All rules come from the
**`cli-architecture`** doctrine — load it first and follow it; this skill does
not restate it.
## Precondition — invoked via scaffold-cli
This skill assumes `scaffold-cli` has already resolved the language and
dispatched here with `paradigm: compiled` (Rust, Go, or .NET). If invoked
directly and no resolved language was handed off, do not resolve it
yourself — stop and tell the user to invoke `scaffold-cli` instead. If you
must confirm ambiguity, you may re-run
`python3 "${CLAUDE_PLUGIN_ROOT}/scripts/lang_router.py" "<language-as-given>"`,
but only continue if its JSON `paradigm` is `compiled`; on `AMBIGUOUS:`,
`UNSUPPORTED:`, or any other `paradigm`, refuse and name `scaffold-cli` as the
correct entry point — mirroring `scaffold-cli`'s own AMBIGUOUS/UNSUPPORTED
handling rather than scaffolding anyway.
## Step 1 — Load doctrine
Load the `cli-architecture` skill. Do not generate anything before it is loaded.
## Step 2 — Read the per-language reference
Read the reference for the resolved language (each maps 1:1 onto the five pillars):
- Rust → `${CLAUDE_PLUGIN_ROOT}/skills/cli-scaffold-compiled/references/rust.md`
- Go → `${CLAUDE_PLUGIN_ROOT}/skills/cli-scaffold-compiled/references/go.md`
- .NET → `${CLAUDE_PLUGIN_ROOT}/skills/cli-scaffold-compiled/references/dotnet.md`
## Step 3 — Resolve the write target (in code)
```bash
python3 "${CLAUDE_PLUGIN_ROOT}/script