Project Templates
How templates turn good practices into reproducible project starts for agents.
The Project Starter Stack turns accumulated learning into reproducible starts. A new project should not begin from zero; it should begin from a base that already includes stack decisions, rules, skills, and documentation.
Next.js Template
The main reviewed template targets modern frontend work:
| Technology | Use |
|---|---|
| Next.js 15 | App Router and modern structure. |
| React 19 | UI and components. |
| TypeScript | Strict typing. |
| Tailwind CSS v4 | Styling. |
| shadcn/ui + Radix | Accessible components. |
| Zustand | Client state. |
| Vitest + Testing Library | Tests. |
| Supabase | Optional backend when needed. |
Included Skills
The template includes skills to guide the agent:
next-best-practices;react-best-practices;shadcn-ui;vitest-testing;frontend-design;project-conventions;supabase-postgres-best-practices.
Required Documentation
Each generated project should include:
| File | Purpose |
|---|---|
docs/README.md | Project introduction, routes, and stack. |
docs/code-reference.md | Living reference for interfaces, functions, and flows. |
docs/architecture.md | Technical decisions and structure. |
AGENTS.md | Rules for agents working in the repository. |
Expected Flow
Loading diagram…
Learning
Templates are packaged operational memory. Whenever the system learns a good practice, it can become a rule, skill, script, or base file so future projects start in a better state.