Build an app
Shipping an app is layers of decisions. None are universal: teams swap frameworks, hosts, and databases. This section gives you:
- What problem each layer solves
- Common options — what each is best for
- A default spine this wiki uses for examples — not a law
Default spine (NK Wiki examples)
| Layer | Default pick | Why it’s a sane starting point |
|---|---|---|
| Editor + AI | Editor & AI | Cursor, Windsurf, or Antigravity — see pros/cons |
| Framework | Next.js | React, routing, API routes, great docs |
| Styling | Tailwind CSS | Utility-first, fast iteration, huge ecosystem |
| Backend + data | Supabase | Postgres, auth, storage without running your own DB |
| Deploy | Vercel + DNS | Built for Next.js; simple Git connect |
You can replace any layer — e.g. SvelteKit, PlanetScale, Fly.io — using the same questions in each chapter.
Reading order
- Planning & specification
- Editor & AI
- Frontend framework
- Styling
- Backend & data
- Deployment
- Security basics
- Practices & quality
Use the Dictionary when jargon appears. For systems-level AI (agents, cost, safety), see Explainers.
Last updated on