Build your repo
Your stack
1Database
ORM
Vercel AI SDK with a streaming chat route, structured output and tool calling.
4 rules · 2 skills · 6 docs
Users, bans, impersonation and an audit log at /admin. Needs sign in.
2 rules · 2 skills · 8 docs
Analytics
Error tracking
Support chat
- PostHog works best with error tracking.
Mode
The plan loop without the gate. Best when you work alone.
Agent tools
Next.js 16 on Vercel. The only stack for now.
my-app/, 175 files, Next.js 16 on Vercel
What your agent gets
52 items. 12 written for your 1 battery.
Guard hooks6
- block-destructiveBefore BashBase
Blocks irreversible shell commands: recursive force deletes, DROP and TRUNCATE sent to a database, force pushes, git reset --hard, git clean, dd, and truncating redirects onto tracked files.
- enforce-typecheckBefore BashBase
Rewrites a bare tsc, however it is launched, into the project's typecheck script before it runs.
- env-leak-detectorBefore Bash, Read, GrepBase
Blocks tool calls that would print, transmit or commit a secret: literal credential shapes, reads of local .env files by any command or by the Read and Grep tools, echo of secret variables, environment dumps, and live values from your .env files.
- auto-lintAfter Edit, Write, MultiEditBase
Runs Biome on the file that was just edited, applies safe fixes, and reports anything it could not fix.
- enforce-doc-metaAfter Edit, Write, MultiEditBase
Checks that files written under docs/solutions/ and docs/plans/ carry the frontmatter those directories depend on, and reports exactly what is missing.
2 more hooks run in team mode.
Rules11
- Events are declared in the catalogue, named object_verb, past tensePostHog
When editing
src/lib/analytics/**+2 more - Identify before the first event that matters, reset on sign-outPostHog
When editing
src/lib/analytics/**+2 more - Server events for anything a client can lie about, and never PII in propertiesPostHog
When editing
src/lib/analytics/**+2 more - Default: tokens only, and both modes every timeDefault design
When editing
src/components/**+1 more - Code style and file conventionsBase
Always loaded
Skills10
- /add-eventPostHog
Add a product event end to end: catalogue entry, the question it answers, the capture call on the correct side of the network, and a check that it arrives.
- /ask-productPostHog
Answer a question about user behaviour from this repo's event catalogue and the PostHog project, with the caveats that make the number usable.
- /new-componentDefault design
Add a component to the Default kit: prefer pasting from shadcn/ui, fix the two bridge classes, keep it token-only and verify it in both light and dark.
- /deploy-to-vercelBase
Ship my-app to Vercel: local gates, environment variables per scope, preview verification, promotion and rollback.
- /helpBase
Explain the agentic system in this repo (rules, skills, agents, hooks, solution docs and the CE loop) and where to go for help beyond it.
Subagents6
- product-analystPostHog
Read-only product analyst. Answers questions about user behaviour from the event catalogue and the PostHog project, and says plainly when the instrumentation cannot answer them.
- designerDefault design
Owns the Default design system and its shadcn bridge. The only agent allowed to introduce a new visual pattern or a new token. Refuses to ship a raw colour or a single-mode change.
- documentarianBase
Keeps README, CLAUDE.md, DESIGN.md, docs/onboard.md and docs/solutions/ true to the code. Writes solution docs from work that just landed.
- pr-reviewerBase
Reviews a diff against this repo's rules before it becomes a PR. Convention-aware, blocking on correctness and security, advisory on taste.
- security-auditorBase
Audits the repo or a diff for leaked secrets, broken auth boundaries, injection, unsafe dependencies and unsafe deploy configuration.
Solution docs18
- Ad blockers eat a third of your analytics: proxy ingestion through your own domainPostHog
- Event names that still make sense in twelve monthsPostHog
- Feature flags without the flickerPostHog
- The identify race that empties your signup funnelPostHog
- Server events versus client events, and when each one liesPostHog
MCP servers1
- posthog
- settings.json
- onboard.md
- proxy.ts
- .env.example
- .gitignore
- .mcp.json
- CLAUDE.md
- DESIGN.md
- README.md
- agentic.config.json
- biome.jsonc
- components.json
- next.config.ts
- package.json
- playwright.config.ts
- postcss.config.mjs
- tsconfig.json
- vitest.config.ts
CLAUDE.md
Structure preview. Repo-wide rule bodies are written into the real file in full.
# my-app Generated by [Agentic Boilerplate](https://github.com/agentic-studio/agentic-boilerplate) from [Agentic Studio](https://theagentic.studio). Same `agentic.config.json`, same repo: regenerate and diff any time. - **Stack:** Next.js on Vercel (`nextjs-vercel`)- **Batteries:** PostHog (`posthog`)- **Design:** Default (`default`). See [DESIGN.md](DESIGN.md).- **Package manager:** bun- **Mode:** solo- **Agent targets:** claude ## Read this first On a fresh clone, read [docs/onboard.md](docs/onboard.md) before running orediting anything. It lists every environment variable, where to get it, andthe order to set the services up. ```shbun installcp .env.example .env.localbun run verifybun run dev``` ## How this repo is set up for agents - `.claude/rules/`: 11 rules. 3 load every session, 8 load when you read a file they cover.- `.claude/agents/`: 6 subagents, listed below.- `.claude/skills/`: 10 skills, listed below.- `.claude/hooks/`: 6 guard hooks, wired in `.claude/settings.json` for Claude Code.- `.mcp.json`: 1 MCP server (`posthog`). Setup is in [docs/onboard.md](docs/onboard.md).- `docs/solutions/`: 18 solved problems. Read the relevant one before re-solving anything.- `docs/plans/`: one plan per unit of work. Run `bun run verify:hooks` to prove the guards still block what they claim to block.Do not edit `.claude/settings.json` by hand: the `system-manager` agent owns it. ## Workflow The Compound Engineering plugin adds the loop: `/ce-brainstorm`, `/ce-plan`, `/ce-work`, `/ce-code-review`, `/ce-compound`.`.claude/settings.json` enables it once you trust this folder. If the commands are missing, run `/plugin install compound-engineering@compound-engineering-plugin`. ## Rules Loaded every session: - [Code style and file conventions](.claude/rules/code-style.md)- [Git and change hygiene](.claude/rules/git.md)- [Security rules](.claude/rules/security.md) Loaded when you read a file they cover: | Rule | Applies to ||---|---|| [Deployment rules](.claude/rules/deployment.md) | `next.config.ts`, `vercel.json`, `package.json`, `src/proxy.ts`, `src/app/**/route.ts`, `.env.example` || [Events are declared in the catalogue, named object_verb, past tense](.claude/rules/event-naming.md) | `src/lib/analytics/**`, `src/app/**`, `src/components/**` || [Identify before the first event that matters, reset on sign-out](.claude/rules/identify-timing.md) | `src/lib/analytics/**`, `src/app/**`, `src/components/**` || [Landing page, legal pages and llms.txt](.claude/rules/landing-and-legal.md) | `src/lib/site.ts`, `src/lib/llms.ts`, `src/app/page.tsx`, `src/app/(legal)/**`, `src/app/llms.txt/**`, `src/components/marketing/**`, `src/components/site/**` || [Server events for anything a client can lie about, and never PII in properties](.claude/rules/server-truth-and-pii.md) | `src/lib/analytics/**`, `src/app/**`, `src/components/**` || [Testing rules](.claude/rules/testing.md) | `tests/**`, `src/**/*.test.ts`, `src/**/*.test.tsx` || [Default: tokens only, and both modes every time](.claude/rules/tokens-only.md) | `src/components/**`, `src/app/**` || [Build UI from the component kit](.claude/rules/ui-kit.md) | `src/components/**`, `src/app/**` | ## Skills | Skill | Use it for ||---|---|| `/add-event` | Add a product event end to end: catalogue entry, the question it answers, the capture call on the correct side of the network, and a check that it arrives. || `/ask-product` | Answer a question about user behaviour from this repo's event catalogue and the PostHog project, with the caveats that make the number usable. || `/deploy-to-vercel` | Ship my-app to Vercel: local gates, environment variables per scope, preview verification, promotion and rollback. || `/help` | Explain the agentic system in this repo (rules, skills, agents, hooks, solution docs and the CE loop) and where to go for help beyond it. || `/landing-copy` | Rewrite the landing page, the metadata and the legal details for the real product from a short brief, by editing src/lib/site.ts only. || `/new-component` | Add a component to the Default kit: prefer pasting from shadcn/ui, fix the two bridge classes, keep it token-only and verify it in both light and dark. || `/qa-feature` | Exercise a feature end to end (happy path, unhappy paths, auth boundaries, refresh and mobile) before anyone calls it done. || `/security-audit` | Run the standing security pass through the security-auditor agent (secrets, auth boundaries, injection, dependencies and deploy config) and turn findings into fixes. || `/verify` | Prove the repo is actually configured: every required env var present, every configured service reachable, and the guard hooks still blocking what they claim to block. || `/write-spec` | Turn a loose request into a written spec (problem, scope, behaviour, acceptance criteria) that /ce-plan can consume without guessing. | ## Subagents | Agent | Use it for ||---|---|| `designer` | Owns the Default design system and its shadcn bridge. The only agent allowed to introduce a new visual pattern or a new token. Refuses to ship a raw colour or a single-mode change. || `documentarian` | Keeps README, CLAUDE.md, DESIGN.md, docs/onboard.md and docs/solutions/ true to the code. Writes solution docs from work that just landed. || `pr-reviewer` | Reviews a diff against this repo's rules before it becomes a PR. Convention-aware, blocking on correctness and security, advisory on taste. || `product-analyst` | Read-only product analyst. Answers questions about user behaviour from the event catalogue and the PostHog project, and says plainly when the instrumentation cannot answer them. || `security-auditor` | Audits the repo or a diff for leaked secrets, broken auth boundaries, injection, unsafe dependencies and unsafe deploy configuration. || `system-manager` | Maintains the .claude agentic layer itself: rules, skills, agents, hooks, settings. Adds a rule when a correction repeats. | ## Credit Generated by [Agentic Boilerplate](https://github.com/agentic-studio/agentic-boilerplate) from [Agentic Studio](https://theagentic.studio). - [AI Mechanic](https://theagentic.studio/ai-mechanic): Fix a vibe-coded repo, then install this system into it.- [Claude Engineering System](https://theagentic.studio/claude-engineering-system): The same agentic layer, installed into your existing codebase.- [AI Product Sprint](https://theagentic.studio/ai-product-sprint): We build the MVP on top of a repo like this one.
Default. shadcn done carefully. Neutral greys, near-black actions, one blue for links, Geist throughout.
Your agents read this design’s DESIGN.md before they touch a colour.
