Cline rules

1# Project Rules
2 
3## Stack
4- Use Node.js 20.9.0 or newer.
5- This is a Next.js portfolio site with page routes under `pages/`.
6- Shared UI lives under `components/`.
7- Design-system primitives live under `components/design-system/`.
8- Static assets live under `static/`.
9 
10## Workflow
11- Before editing, inspect repo state with `git status --short` and `git diff --stat`.
12- If the diff is large, identify the largest changed files before editing.
13- Prefer small, low-churn edits over broad rewrites.
14- Avoid modifying `package-lock.json` unless dependency work requires it.
15- Follow Conventional Commits for commit messages.
16 
17## Generated Files
18- Do not edit, stage, commit, or include generated output unless explicitly asked.
19- Treat `out/**`, `.next/**`, `_next/**`, `_error/**`, `dist/**`, `build/**`,
20  `coverage/**`, `.turbo/**`, `.vercel/**`, `*.map`, `*.min.js`, and `*.min.css`
21  as generated.
22- Root static-export HTML files are generated. Treat `pages/` and `components/` as
23  source of truth.
24- If a build modifies generated files, leave them unstaged and report the change.
25 
26## Verification
27- For source code changes, run `npm test` and `npm run build`.
28- `npm run build` performs the static export and refreshes `out/`, including
29  `out/.nojekyll`.
30- Keep `npm run build` cross-platform; do not add OS-specific shell snippets.
31