Project Template Hierarchy Reference
Quick reference for the 4-level project template system. For detailed docs, see the references/ files linked below.
Levels Overview
| Level |
Pattern |
Parent |
Purpose |
| 0 |
project-template |
none |
Universal base — structure, rules, commands, conventions |
| 1 |
project-{stack} |
project-template |
Stack-specific — stack.json filled, plugins declared, stack docs |
| 1.5 |
demo-{stack} |
project-{stack} |
Working demo app — sample data, seed scripts, showcases |
| 2 |
{client}-{project} |
project-{stack} |
Client project — real IDs/URLs, .env and settings.local.json values behind the ${VAR} references in .mcp.json |
Each level inherits everything from its parent and adds level-specific content.
What Lives Where
- Level 0 owns: Process skills (brainstorming, TDD, debugging, planning, verification), core workflow skills (commit, pr, plan-feature, code-review-project, retro, sync), generic rules (safety, search-before-building, conventions), docs templates, project-config template
- Level 1 owns: Stack-specific skills (e.g.,
new-page for Next.js), stack-specific .env.example vars, stack-specific CLAUDE.md gotchas, stack plugin references, stack-specific docs (architecture, code-style)
- Level 1.5 owns: Sample data, seed scripts, working pages, demo deployment configs
- Level 2 owns: Client resource IDs, real credentials (.env), domain-specific skills, custom business logic
Key Files
Every template has: stack.json, AGENTS.md (shared rules), CLAUDE.md (imports @AGENTS.md), README.md, .env.example, .mcp.json (committed, ${VAR} references only), .gitignore, docs/ (architecture, code-style, api-conventions), .claude/ (skills, agents, rules, settings.json with enabledPlugins and extraKnownMarketplaces).
Detailed References
- hierarchy.md — Detailed level descriptions with examples
- file-inventory.md — Complete file-by-file inventory per template level
- conventions.md — Naming conventions, stack.json schema, CLAUDE.md structure, .mcp.json and settings
1---2name: template-reference-23description: >4 Use this skill when the user asks about "template hierarchy", "template levels",5 "project template conventions", "what files go in a template", "Level 0 vs Level 1",6 "template structure", "what belongs in the parent template", or needs reference7 documentation for the project template system and its 4-level hierarchy.8disable-model-invocation: true9metadata:10 source: https://skillmd.com/skills/agents-store/template-reference-211---1213# Project Template Hierarchy Reference1415Quick reference for the 4-level project template system. For detailed docs, see the `references/` files linked below.1617## Levels Overview1819| Level | Pattern | Parent | Purpose |20|-------|---------|--------|---------|21| 0 | `project-template` | none | Universal base — structure, rules, commands, conventions |22| 1 | `project-{stack}` | `project-template` | Stack-specific — stack.json filled, plugins declared, stack docs |23| 1.5 | `demo-{stack}` | `project-{stack}` | Working demo app — sample data, seed scripts, showcases |24| 2 | `{client}-{project}` | `project-{stack}` | Client project — real IDs/URLs, .env and settings.local.json values behind the `${VAR}` references in .mcp.json |2526Each level inherits everything from its parent and adds level-specific content.2728## What Lives Where2930- **Level 0 owns:** Process skills (brainstorming, TDD, debugging, planning, verification), core workflow skills (commit, pr, plan-feature, code-review-project, retro, sync), generic rules (safety, search-before-building, conventions), docs templates, project-config template31- **Level 1 owns:** Stack-specific skills (e.g., `new-page` for Next.js), stack-specific .env.example vars, stack-specific CLAUDE.md gotchas, stack plugin references, stack-specific docs (architecture, code-style)32- **Level 1.5 owns:** Sample data, seed scripts, working pages, demo deployment configs33- **Level 2 owns:** Client resource IDs, real credentials (.env), domain-specific skills, custom business logic3435## Key Files3637Every template has: `stack.json`, `AGENTS.md` (shared rules), `CLAUDE.md` (imports `@AGENTS.md`), `README.md`, `.env.example`, `.mcp.json` (committed, `${VAR}` references only), `.gitignore`, `docs/` (architecture, code-style, api-conventions), `.claude/` (skills, agents, rules, `settings.json` with `enabledPlugins` and `extraKnownMarketplaces`).3839## Detailed References4041- [hierarchy.md](references/hierarchy.md) — Detailed level descriptions with examples42- [file-inventory.md](references/file-inventory.md) — Complete file-by-file inventory per template level43- [conventions.md](references/conventions.md) — Naming conventions, stack.json schema, CLAUDE.md structure, .mcp.json and settings