Practices & quality
What this layer solves
Practices turn a prototype into something you can change without fear: small PRs, automated checks, and a bit of observability.
Options / habits
| Practice | Best for | Tradeoffs |
|---|---|---|
| TypeScript | Catch whole classes of bugs | Slightly slower onboarding |
| Lint + format (ESLint, Prettier) | Consistent style | Occasional rule fights |
| Tests (Vitest/Jest, Playwright) | Regression safety | Time to write meaningful tests |
| CI on PR | Block broken merges | GitHub Actions minutes |
| Structured logging | Debug production issues | Upfront setup |
NK Wiki default: TypeScript on, ESLint from create-next-app, add one E2E happy-path test when core flow stabilizes.
Outline: minimal quality bar
- Branch + PR even when solo — narrative for future you.
- Preview URL from Vercel on every PR — click through on mobile.
- Error monitoring (e.g. Sentry) when you have users — optional early, valuable soon.
- README in repo: how to run locally, required env vars, deploy steps.
Official links
- Vitest — unit tests
- Playwright — browser E2E
Related
- How you know it’s working — metrics mindset for AI + app features
Last reviewed: April 2026.
Last updated on