lets-vibe
v0.5.1
Published
CLI tool that scaffolds a professional documentation structure for new projects.
Readme
lets-vibe
A CLI tool that scaffolds a clear, professional documentation structure for new software projects.
Installation
# Run directly with npx (recommended)
npx lets-vibe <project-name>
# Or install globally
npm install -g lets-vibe
lets-vibe <project-name>Features
- Generates a
v-docs/directory with ready-to-edit markdown templates. - Cross-platform: macOS, Linux, Windows.
- Helpful flags:
--dry-run,--overwrite,--yes,--cursor,--no-templates.
Getting the Most Out of lets-vibe
Start early – run the CLI at project inception so the Idea & Architecture docs guide discussions from day one.
Use flags together – generate a project and pre-create Cursor context in one go:
npx lets-vibe my-app --cursorDry-run before committing – preview changes when adding docs to an existing repo:
lets-vibe . --dry-runIterate on templates, don't ignore them – replace every
{{placeholder}}in the generated markdown; unfinished TODOs are a signal to revisit requirements.Link docs in pull requests – when a PR implements an architecture decision, reference the ADR section in
02_architecture.mdso reviewers have context.Track work in packages – use the work-packages folder with WP001, WP002 naming to track discrete deliverables.
CI tip – add a workflow step that fails if
grep -R "{{.*}}" v-docs | wc -lreturns non-zero, ensuring placeholders get filled.
License
MIT © Conor Breen
# Generate docs **with** templates (default)
npx lets-vibe my-app
# Skip copying templates
npx lets-vibe my-app --no-templates