Menu
Scaffold stage for the rust-cli skill family: create a new Rust CLI Skill project from the package templates and prepare it for validation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Umbrella guide for the rust-cli skill family: route Rust CLI Skill work through intake, description, scaffolding, feature extension, validation, and publish/release while preserving the constitution, package layout contract, and packaging boundaries.
Description stage for the rust-cli skill family: define or refresh the generated skill description contract before downstream stages change scaffold, feature, validation, or packaging surfaces.
Extension stage for the rust-cli skill family: add the supported stream or repl feature to an existing scaffolded project while preserving the shared runtime contract.
Triage stage for the rust-cli skill family: classify the request as description, scaffold, extend, validate, or publish, confirm required inputs, load the shared rules, and hand off to the correct next phase.
Publish stage for the rust-cli skill family: close the workflow with repository-owned packaging and release actions, including report-only summaries, dry runs, exact-mirror rehearsals, destination configuration checks, and the supported GitHub Actions publication path.
Validation stage for the rust-cli skill family: run the documented compliance checks for an existing project and report whether it is constitution-compliant, usable with warnings, or blocked by errors.
| name | rust-cli-scaffold |
| description | Scaffold stage for the rust-cli skill family: create a new Rust CLI Skill project from the package templates and prepare it for validation. |
Use this stage when the work is to create a brand-new Rust CLI Skill project from this package and the description stage has already approved the generated skill's description contract.
Create a constitution-compliant project scaffold that is immediately ready for validation and reuses the approved description contract across generated surfaces.
Read instructions/new.md as the exact source of truth for token expansion,
file layout, required commands, and verification checks.
skill_nameauthorversionrust_editiondescription../../instructions/new.md:
validate the name, require it when missing, and refuse to overwrite an
existing target directory.cargo build, cargo clippy -- -D warnings, cargo fmt --check, and
cargo test.This stage is complete only when the new project exists, the template expansion is clean, and the required checks pass.
Continue with ../rust-cli-validate/SKILL.md
unless the user explicitly asked to stop after scaffolding.