Setup Project Files
UTILITY SKILL. INVOKES: repo inventory, docs, package scripts. FOR SINGLE OPERATIONS: source scaffolding.
USE FOR:
- "setup the project files"
- "initialize this app"
- "scaffold the repo"
- "create the initial structure"
- "make this early repo follow sound architecture"
DO NOT USE FOR:
- Docs-only setup; use
initialize-project-docs.
- Electron shell creation; use
initialize-electron-app.
- Branch planning, PR publishing, CI repair, or reviews.
- Feature work after project structure already exists.
Workflow
- Inventory with
rg --files; read README, AGENTS, docs, manifests, config, lockfiles, source, and tests.
- Infer purpose, runtime, surfaces, and risks. Ask one question only when structure hinges on the answer.
- Choose structure using Architecture Principles and Project Archetypes. Prefer project vocabulary over generic buckets.
- Create the smallest useful structure: entrypoint or composition root, config, pure domain modules, edge adapters, and focused tests.
- Keep docs consistent; use
initialize-project-docs only when onboarding docs are also missing.
- Validate available commands, new scripts, and
git diff --check; reread for placeholders, imports, and path drift.
Guardrails
- No templates, empty folders, unrelated scripts, or aspirational docs.
- Preserve user files and existing conventions.
- Put side effects at edges and pure decisions in core/domain/shared modules.
- Centralize config parsing and validation.
Examples:
- In scope: "scaffold this CLI repo after reading the README."
- Out of scope: "create README and AGENTS only."
Troubleshooting:
If no validation commands exist, run smoke checks and report the gap.
Final Response
Summarize the inferred shape, files changed, validation performed, and assumptions.
1---2name: setup-project-files3description: Create or refresh source files for young software projects. Use for "setup project files", "initialize this app", "scaffold the repo", "create initial structure", or aligning a young codebase with README, docs, manifests, and AGENTS instructions.4---56# Setup Project Files78**UTILITY SKILL. INVOKES:** repo inventory, docs, package scripts. **FOR SINGLE OPERATIONS:** source scaffolding.910## USE FOR:1112- "setup the project files"13- "initialize this app"14- "scaffold the repo"15- "create the initial structure"16- "make this early repo follow sound architecture"1718## DO NOT USE FOR:1920- Docs-only setup; use `initialize-project-docs`.21- Electron shell creation; use `initialize-electron-app`.22- Branch planning, PR publishing, CI repair, or reviews.23- Feature work after project structure already exists.2425## Workflow26271. Inventory with `rg --files`; read README, AGENTS, docs, manifests, config, lockfiles, source, and tests.282. Infer purpose, runtime, surfaces, and risks. Ask one question only when structure hinges on the answer.293. Choose structure using [Architecture Principles](references/architecture-principles.md) and [Project Archetypes](references/project-archetypes.md). Prefer project vocabulary over generic buckets.304. Create the smallest useful structure: entrypoint or composition root, config, pure domain modules, edge adapters, and focused tests.315. Keep docs consistent; use `initialize-project-docs` only when onboarding docs are also missing.326. Validate available commands, new scripts, and `git diff --check`; reread for placeholders, imports, and path drift.3334## Guardrails3536- No templates, empty folders, unrelated scripts, or aspirational docs.37- Preserve user files and existing conventions.38- Put side effects at edges and pure decisions in core/domain/shared modules.39- Centralize config parsing and validation.4041## Examples:4243- In scope: "scaffold this CLI repo after reading the README."44- Out of scope: "create README and AGENTS only."4546## Troubleshooting:4748If no validation commands exist, run smoke checks and report the gap.4950## Final Response5152Summarize the inferred shape, files changed, validation performed, and assumptions.
willakins