Menu
Post-cargo-generate setup for a new project. Walks through first-run configuration, domain replacement, and tooling bootstrap.
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
| name | template-init |
| description | Post-cargo-generate setup for a new project. Walks through first-run configuration, domain replacement, and tooling bootstrap. |
| disable-model-invocation | false |
Run /template-init immediately after cargo generate completes in a new project.
Ask the user which surfaces were selected during generation (CLI / API / MCP / web). Note any surfaces that were excluded — those directories won't exist and references to them should be skipped.
The generated project contains a demo example domain. Ask the user for their first real domain name (snake_case).
Then:
crates/core/src/example.rs → crates/core/src/{domain}.rscrates/core/src/example/ → crates/core/src/{domain}/crates/app/src/cli/example.rs → crates/app/src/cli/{domain}.rs (if CLI surface)crates/app/src/api/services/example.rs → crates/app/src/api/services/{domain}.rs (if API surface)mod example / use example references in lib.rs, main.rs, and surface filescrates/app/src/mcp/ (if MCP surface)If the user doesn't have a domain name yet, skip this step and remind them to use /add-domain later.
Replace the template placeholder content with:
just bootstrap # installs cargo-nextest, lefthook, taplo, etc.
just install-hooks # wires lefthook git hooks
Invoke the sync-stack-llms subagent to analyze the actual Cargo.toml and package.json dependencies and generate any missing llms.txt reference files.
just lint # should pass on the fresh scaffold
just test # should pass
If either fails, surface the errors before proceeding.
git add -A
git commit -m "chore: initialize project from rust-bin template"
/add-domain for subsequent domainsScaffold a new domain module following the spec layout. Creates all required files with correct structure and wires CLI, API, and MCP surfaces.
Authoritative procedure for publishing an MCP server to the official MCP registry at registry.modelcontextprotocol.io — package metadata, server.json schema, authentication, validation, publish, and verification. Preloaded by mcp-publisher.
Stage all current changes, optionally bump project versions, update changelog, commit with an appropriate message, push the current or new feature branch, and then save session documentation. Use when the user asks to quick push, commit and push everything, ship current changes, or run a full git add/commit/push workflow with session capture.
Save the current agent session to an in-repo markdown file with observed metadata, git state, session context, verification evidence, errors, open questions, and next steps. Use when the user asks to save session notes, persist conversation context, create a session log, document the current work, or when another workflow such as quick-push needs post-push session documentation.
Run xtask enforcement gates before declaring work complete. Use before finishing any Rust code change.