Stack rules
Twelve standards files for the stack this kit assumes. They load only when the
work actually touches the relevant area, which is the point: importing all of
them on every session costs roughly 12,500 tokens, and a Python service that
will never render a button should not pay for the Tailwind rules.
The six genuinely universal standards (git, security, writing, naming,
typescript, review-discipline) are not here. Those are @-imported by
CLAUDE.md and always in context, at about 3,700 tokens.
Which file to read
Read the specific file before writing code in its area. Do not read all twelve.
| Working on |
Read |
| React components, shadcn/ui, loading/empty states |
references/components.md |
| API routes, Zod validation, error shapes |
references/api.md |
| Supabase schema, RLS, migrations, queries |
references/database.md |
| Vercel deploys, env vars, pre-deploy checks |
references/deployment.md |
| Color, typography, spacing, the visual system |
references/design.md |
| Images, fonts, bundle size, Core Web Vitals |
references/performance.md |
| React Query, URL state, Zustand, form state |
references/state.md |
| Semantic HTML, focus, ARIA, WCAG contrast |
references/accessibility.md |
| Scroll animations, parallax, reveal effects |
references/scroll-effects.md |
| Unit, integration, and E2E tests |
references/testing.md |
| Hick's, Fitts's, Miller's, layout decisions |
references/ux-laws.md |
| Pre-ship audit across all six lenses |
references/audit.md |
How to apply them
These are standards, not suggestions. When a file says "never build a custom
button, use shadcn/ui," that is the expected output, not one option among
several. If a rule genuinely does not fit the project, say so and explain why
rather than quietly ignoring it.
When a task spans areas, read each relevant file. Building a settings page that
saves to Supabase means components.md, state.md, and database.md, plus
accessibility.md before it ships.
1---2name: stack-rules3description: Enforces this kit's standards for Next.js, React, Supabase, and Vercel work. Use when writing or reviewing UI components, API routes, database schemas or queries, deployment config, styling and design, scroll animations, accessibility, performance, state management, tests, or when running a pre-ship audit. Covers shadcn/ui component patterns, Zod-validated App Router routes, RLS policies, Core Web Vitals budgets, WCAG contrast, and the UX laws checklist.4---56# Stack rules78Twelve standards files for the stack this kit assumes. They load only when the9work actually touches the relevant area, which is the point: importing all of10them on every session costs roughly 12,500 tokens, and a Python service that11will never render a button should not pay for the Tailwind rules.1213The six genuinely universal standards (git, security, writing, naming,14typescript, review-discipline) are not here. Those are `@`-imported by15`CLAUDE.md` and always in context, at about 3,700 tokens.1617## Which file to read1819Read the specific file before writing code in its area. Do not read all twelve.2021| Working on | Read |22| ------------------------------------------------- | ------------------------------ |23| React components, shadcn/ui, loading/empty states | `references/components.md` |24| API routes, Zod validation, error shapes | `references/api.md` |25| Supabase schema, RLS, migrations, queries | `references/database.md` |26| Vercel deploys, env vars, pre-deploy checks | `references/deployment.md` |27| Color, typography, spacing, the visual system | `references/design.md` |28| Images, fonts, bundle size, Core Web Vitals | `references/performance.md` |29| React Query, URL state, Zustand, form state | `references/state.md` |30| Semantic HTML, focus, ARIA, WCAG contrast | `references/accessibility.md` |31| Scroll animations, parallax, reveal effects | `references/scroll-effects.md` |32| Unit, integration, and E2E tests | `references/testing.md` |33| Hick's, Fitts's, Miller's, layout decisions | `references/ux-laws.md` |34| Pre-ship audit across all six lenses | `references/audit.md` |3536## How to apply them3738These are standards, not suggestions. When a file says "never build a custom39button, use shadcn/ui," that is the expected output, not one option among40several. If a rule genuinely does not fit the project, say so and explain why41rather than quietly ignoring it.4243When a task spans areas, read each relevant file. Building a settings page that44saves to Supabase means `components.md`, `state.md`, and `database.md`, plus45`accessibility.md` before it ships.
calebnewtonusc