template-init

Automate post-scaffold setup with placeholder substitutions and tooling bootstrap.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jmagar/rust-bin --skill template-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-init
Source: https://github.com/jmagar/rust-bin/tree/main/.claude/skills/template-init
Command: npx skills add https://github.com/jmagar/rust-bin --skill template-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the initial project setup after cargo generate by applying placeholder substitutions and bootstrapping tooling.

Core Features & Use Cases

  • Domain renaming: replaces placeholders with the real domain across crates and surfaces.
  • Tooling bootstrap: installs and wires common developer tools (linting, testing, git hooks).
  • First-run verification: validates scaffold integrity and creates an initial commit to lock in changes.

Quick Start

After running cargo generate for a new project, run /template-init to apply the first-run configuration and bootstrap tooling.

Frequently Asked Questions about template-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate project setup after running cargo generate for a new Rust crate?

Automated project setup after cargo generate applies placeholder substitutions, bootstraps tooling, and creates a verification commit to deliver a ready-to-work Rust crate with linting, testing, and git hooks wired.

What does domain renaming do during Rust project scaffolding?

Domain renaming during Rust project scaffolding replaces placeholders across crates and app surfaces with the real domain name, ensuring consistent naming throughout the workspace before tooling bootstrap begins.

How do I bootstrap developer tooling for a new Rust-bin template?

Tooling bootstrap for a new Rust-bin template installs and wires common developer tools including linting, testing, and git hooks, enforcing a deterministic workflow that validates scaffold integrity before the first commit.

Can I use this scaffolding workflow for non-Rust projects?

This scaffolding workflow targets Rust crates and app surfaces specifically, applying domain renaming and tooling bootstrap tailored to Rust-bin templates rather than generic non-Rust project structures.

What's the best way to lock in initial project changes after scaffolding a Rust crate?

Lock in initial project changes after scaffolding by running a first-run verification that validates scaffold integrity and creates an initial commit, ensuring the Rust crate starts from a known, deterministic state.

Why does template-init enforce a deterministic workflow for Rust project setup?

Template-init enforces a deterministic workflow through defined steps to guarantee scaffold integrity, applying placeholder substitutions and tooling bootstrap consistently so every new Rust-bin project reaches the same ready-to-work state.