ds-init

/ds-init

New projects start with no CI, no test setup, no linting, and inconsistent structure. This skill scaffolds all of it from day one.

Project Scaffolding — Generate production-ready project structure for any stack.

Completion Evidence — applies to every phase: Report done/OK only with the machine-checkable evidence the gates name — the exact command run and its observed output (or file:line diff). Missing evidence → report INCOMPLETE plus what is missing. Self-assessment is never evidence. (This band repeats at file end by design — both copies are normative.)

Triggers

User runs /ds-init, or asks to scaffold/bootstrap/initialize a new or greenfield project.

Triggers — INVOKE / DON'T INVOKE

INVOKE	DON'T INVOKE
"scaffold a new {framework} project"	"audit existing project for health" (→ ds-blueprint)
"create CI / Docker / test boilerplate from zero"	"deploy the app" (→ ds-deploy)
"initialize project structure for {type}"	"add a feature to existing app" (→ implement directly)
"bootstrap this repo's tooling configs"	"set up my machine's AI toolset" (→ ds-rig)
"bootstrap with sensible defaults"	"research which framework to pick" (→ ds-research)

Contract

Dimensions: none (carrier)

• Generates project structure, a local quality gate, test setup, Docker stubs, editor config, env templates
• Detects intent (web / api / mobile / cli / library / monorepo) from input or codebase signals
• Generates only files relevant to detected type — no unnecessary boilerplate
• Respects existing files — overwrites only with explicit user confirmation
• Standalone. Uses blueprint when available to select scaffold template; asks user when absent.
• Minimal liability + minimum deps + maximum automation: well-known config patterns, no custom security code, minimal starting deps (rationale documented), lint/format/type/test wired from day one via a local quality gate. Prefer stdlib and established minimal libraries.
• Local gate first: wires a local quality gate by default (advisory handoff to /ds-quality; absent → a generated scripts/quality.sh-style chain from ../core/toolchains.md) instead of CI; CI workflow files generate only under --full. A privacy-policy stub + data-inventory file generate only when pii=yes; otherwise skipped with a one-line note.
• Full accounting enforced: every finding and planned check ends in an explicit disposition (fixed / skipped + reason / only you can do); summary totals balance.
• Pre-existing / out-of-scope errors detected during work are NOT skipped — fixed inline or escalated with concrete blocker.
• Exempt from state protocol: idempotent scaffolding — re-running on the same project naturally resumes because existing files are skipped. No ds/audit/init.json.