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 |
|---|---|---|
| Planning | Planning & spec | Spec-driven for products, vibe code for experiments |
| Editor + AI | Editor & AI | Cursor Nick’s Pick, Windsurf, or Antigravity |
| Framework | Next.js | React, routing, API routes, great docs |
| Design | Frontend design | design.md + AI tools, no Figma required |
| Styling | Tailwind CSS | Utility-first, fast iteration, huge ecosystem |
| Auth | Authentication | Clerk, Supabase Auth, or Neon Auth |
| Backend + data | Backend & data | Supabase or Neon Nick’s Pick for Postgres |
| Deploy | Vercel + DNS | Built for Next.js; simple Git connect |
You can replace any layer — e.g. SvelteKit, Firebase, Fly.io — using the same questions in each chapter. See Stacks & boilerplates for pre-configured combos.
Reading order
- Planning & specification
- Editor & AI
- Frontend framework
- Frontend design
- Styling
- Authentication
- Backend & data
- Stacks & boilerplates
- Deployment
- Security basics
- Practices & quality
Use the Dictionary when jargon appears. For systems-level AI (agents, cost, safety), see Explainers. For getting your product in front of people, see Distribution.