Knowledge
Things that cost real time because a tool behaved differently than its documentation said. Written by /harvest, tagged by stack, and installed to match what a project is built on.
What's in it
Listed from the repo at build time.
knowledge/
5 files, 26 gotchas
| File | Stack | Gotchas | Verified |
|---|---|---|---|
Verifying UI in the Claude Code Browser pane browser-verification.md | claude-code-desktop | 5 | 2026-09-14 Claude Code 2.1.266, Browser pane Chrome 152.0.7977.76, Playwright 1.63 + cached chromium_headless_shell-1228 |
Bun gotchas bun.md | bun | 2 | 2026-09-13 bun 1.4.2 |
ESLint 9 flat-config gotchas eslint.md | eslint-9 | 3 | 2026-09-13 eslint 9.39.5, @typescript-eslint/parser 8.70.0 |
Next.js App Router gotchas nextjs-app-router.md | nextjs-16 | 1 | 2026-09-13 next 16.3.5 |
shadcn registry gotchas shadcn-registry.md | nextjs-16tailwind-4shadcn-4 | 15 | 2026-09-14 shadcn 4.21.0 |
The format
Frontmatter says who the file is for and how stale it is. Then one bullet per gotcha, bold claim first. This is shadcn-registry.md, as committed.
---scope: stackstack: [nextjs-16, tailwind-4, shadcn-4]verified_version: shadcn 4.21.0verified_on: 2026-09-14---- **`init --base` takes `base`, not `base-ui`.** `shadcn init -d --base base` (values: `radix | base | aria`). Some docs and skills say `base-ui`; 4.21 rejects it.Keep it true
verified_on tells a reader whether to trust the file or check it again. Update it whenever a bullet is confirmed against the installed tool, and never write an example from memory.What earns a place
A note earns its place only when the documentation is silent or wrong.
Anything that restates the docs makes the rest of the file less likely to be read. The test is whether it cost someone an hour: a gotcha solved and not written down gets solved again in the next project.