scaffold

Scaffold

Prepare a project for development. Creates directories, configs, and installs dependencies — never source or test files.

Boundaries

This skill MAY: create directories, config files, install dependencies, set up tooling. This skill MAY NOT: create source files (*.ts, *.js, *.py, etc.), create test files, write implementation code, write test code.

NEVER create source or test files. Structure and configuration only.

Common Rationalizations

Shortcut	Why It Fails	The Cost
"Create a starter file — just a skeleton"	Skeletons become the implementation. Test writers then test the skeleton, not real behavior	Weak tests that pass with stubs
"Skip dependency install — implementer can do it"	Missing deps cause confusing errors downstream	Wasted time debugging missing imports
"Use default configs — they'll customize later"	Default configs often conflict with project conventions	Config drift → inconsistent behavior

---

Step 1: Read Architecture Doc

If $ARCH_PATH is set (pipeline mode):

1. Read the architecture doc at $ARCH_PATH
2. Extract: dependencies, file structure, external services
3. Announce: "Reading architecture: [filename]."

If no env var (standalone mode):

1. Use AskUserQuestion (header: "Project", question: "What project are you setting up? Provide an architecture doc path, or describe what you're building.")
2. If they provide a path, read it
3. If they describe it, gather: language/framework, dependencies, project type

Exit: Know what directories, dependencies, and configs are needed.

---

Step 2: Assess Project State

Determine if this is greenfield or brownfield:

# Check for existing project indicators
ls package.json pyproject.toml Cargo.toml go.mod 2>/dev/null
ls -d src/ lib/ app/ 2>/dev/null

• Greenfield: No project manifest or source directories exist
• Brownfield: Project exists — verify paths, note discrepancies with architecture doc