CNA Templates
August 6, 2026 · View on GitHub
This repository contains official templates and extensions for create-awesome-node-app.
Quick start
Browse templates and extensions on the official site, then scaffold locally:
# Interactive mode
npx create-awesome-node-app
# With template and extensions
npx create-awesome-node-app --template react-vite-boilerplate --addons material-ui zustand
Available templates
| Template | Type | Use Case |
|---|---|---|
| React Vite | react | Frontend apps |
| Next.js | nextjs | Full-stack apps |
| NestJS | nestjs-backend | Backend APIs |
| Remix / React Router v7 | remix | Full-stack apps |
| Astro | astro | Content sites |
| Hono | hono | Lightweight APIs |
| Turborepo | monorepo | Monorepos |
| WebdriverIO | webdriverio | E2E testing |
| WebExtension | webextension-react | Browser extensions |
Documentation
| File | Contents |
|---|---|
| docs/ARCHITECTURE.md | System overview, type system, generation flow |
| docs/AUTHORING.md | File conventions, EJS variables, package/ system |
| docs/AUTHORING.es.md | Spanish version of the authoring conventions |
| docs/TESTING.md | Local testing and CI workflow |
| docs/MAINTENANCE_RUNBOOK.md | Operational procedures for maintaining templates, extensions, CI, dependencies, security, and releases |
| CONTRIBUTING.md | How to add templates and extensions |
CI trust layers
Green Actions mean templates and realistic selections work — not that every extension can be merged into one mega-app. See #309 and docs/TESTING.md.
| Workflow | Trigger | Scope |
|---|---|---|
| L0 Integrity | PR, main, weekly | Registry paths, doc links, assets, profiles |
| L1 Templates | PR, main, weekly | Every template alone |
| L2 Extensions | PR (changed), weekly (all) | One extension × canonical template |
| L3 Profiles | PR (affected), weekly (all) | Curated one-per-category stacks |
- PR required bar: L0 + L1 (always). L2/L3 run for touched paths.
- Weekly: full L1 + L2 + L3.
- Never: stack all compatible extensions in one job.
See the Actions tab for latest runs.
For AI assistants: copy-paste to start a maintenance session
If you are an AI agent beginning work on this repository, paste the following prompt exactly (after reading any prior conversation context the user provides):
You are maintaining the Create-Node-App ecosystem: the `create-node-app` CLI monorepo and the `cna-templates` template/extension bank.
Follow the maintenance runbook at `docs/MAINTENANCE_RUNBOOK.md` and its companion guides (`docs/MAINTENANCE_TEMPLATES.md`, `docs/MAINTENANCE_DEPENDENCIES.md`, `docs/MAINTENANCE_SECURITY.md`, `docs/MAINTENANCE_CI.md`, `docs/MAINTENANCE_RELEASE.md`).
Always:
1. Run the pre-flight checklist in `docs/MAINTENANCE_RUNBOOK.md` Section 3 before changing code.
2. Start every significant task with a GitHub issue. If the solution is not obvious, use the issue to analyze options before writing code.
3. Scope work to one fix per PR with a `Closes #<issue>` link when applicable.
4. Open PRs as **ready for review** (not drafts) and wait for automated AI reviewers such as CodeRabbit to finish before merging.
5. Write commits, PRs, issues, and docs in English.
6. Validate locally with `file://` URLs before pushing (see `docs/MAINTENANCE_TEMPLATES.md` Section 9).
7. Run the relevant full CI workflow manually after risky merges and watch it to completion.
8. Update `knowledge/processes/create-node-app-maintenance.md` in the workspace if you discover a new pattern or decision.
Current known constraints:
- CI uses layered L0–L3 workflows (`ci-*.yml`); do not reintroduce all-extensions stacking.
- Always resolve `file://` paths from `templates.json` `url` directories, never from public slugs.
- `create-node-app` releases use npm Trusted Publishing via OIDC; do not use a manual `NPM_TOKEN`.
If the user only says "continue" or asks "what should I do next", summarize the current CI/issues state and propose the next action.
Support
- 🌐 Official site
- 📚 Templates
- 🧩 Extensions
- 📦 NPM Package
- 🐛 Report Issues
- 💬 Discussions
👥 Contributors
Made with contributors-img.