Scaffold Project Documentation
You are generating standard project documentation files for this repository.
Available Documents
The following documents can be generated:
| Key | File | Description |
|---|---|---|
readme |
README.md |
Project overview, setup, usage, and contribution info |
license |
LICENSE |
Open source license file |
contributing |
CONTRIBUTING.md |
Contribution guidelines and development workflow |
changelog |
CHANGELOG.md |
Version history following Keep a Changelog format |
adr |
docs/adr/README.md |
ADR index and initial template (Rule 10.2) |
gitignore |
.gitignore |
Git ignore patterns for Node.js/TypeScript projects |
security |
SECURITY.md |
Security vulnerability reporting policy |
code-of-conduct |
CODE_OF_CONDUCT.md |
Contributor Covenant code of conduct |
Instructions
Determine which docs to create — If
$ARGUMENTSis provided, parse it as a comma-separated list of keys from the table above. Otherwise, ask the user which documents they want using a multi-select question with all options listed above.Check for existing files — For each selected document, check if the file already exists. If it does, ask the user whether to overwrite or skip it.
Read project context — Examine the following to tailor the generated docs:
package.json(project name, description, version, license, scripts)CLAUDE.md(project overview).claude/docs/TypeScript Coding Standard for Mission-Critical Systems.md(if present, reference it in CONTRIBUTING.md)- Existing
README.mdor other docs (to avoid contradictions)
Generate each document — Create each file with appropriate content:
- README.md: Include project name, badges placeholder, description, features, prerequisites, installation, usage, development (build/test/lint scripts from package.json), project structure, contributing link, license link.
- LICENSE: Ask the user which license (MIT, Apache-2.0, ISC, BSD-3-Clause). Default to MIT if not specified.
- CONTRIBUTING.md: Development setup, coding standards reference (link to the coding standard doc if it exists), PR process, commit message conventions, testing requirements (Rule 9.1: >=95% branch coverage).
- CHANGELOG.md: Follow Keep a Changelog format. Start with
## [Unreleased]section. - ADR index: Create
docs/adr/README.mdwith an empty table. Create thedocs/adr/directory if needed. - .gitignore: Node.js + TypeScript patterns (node_modules, dist, coverage, .env, *.js.map, etc.).
- SECURITY.md: Vulnerability reporting instructions, supported versions table, disclosure policy.
- CODE_OF_CONDUCT.md: Contributor Covenant v2.1.
Summary — List all files created and any that were skipped.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.