Skip to main content

template-reference

Use this skill when the user asks about "template hierarchy", "template levels", "project template conventions", "what files go in a template", "Level 0 vs Level 1", "template structure", "what belongs in the parent template", or needs reference documentation for the project template system and its 4-level hierarchy.

Source facts

Repository
Agents-Store/codex-plugins
Last source activity
October 4, 2026 at 20:44
Detected SKILL.md language
English
Stars
0
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
5 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
template-reference
description
Use this skill when the user asks about "template hierarchy", "template levels", "project template conventions", "what files go in a template", "Level 0 vs Level 1", "template structure", "what belongs in the parent template", or needs reference documentation for the project template system and its 4-level hierarchy.
# 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](references/hierarchy.md) — Detailed level descriptions with examples - [file-inventory.md](references/file-inventory.md) — Complete file-by-file inventory per template level - [conventions.md](references/conventions.md) — Naming conventions, stack.json schema, CLAUDE.md structure, .mcp.json and settings
View on GitHub