Engineering
How we start a new project
Checklist for scaffolding new E-FACTS work — linked to Design Language
How we start a new project
Use this checklist before creating repos, routes, or greenfield apps.
1. Clarify the job
- Persona + outcome named (Users)
- Surface owner chosen (Surfaces)
- Success metric / kill criterion drafted (Metrics)
2. Align with product & design
- Read Product principles
- Read Design language and
docs/Design.md - Confirm IA impact (tabs? docs sidebar? marketing page?)
3. Pick the stack deliberately
| If you are building… | Start from… |
|---|---|
| Shopper UI | iOS app patterns (Mobile) |
| Public web | Next.js marketing conventions (Frontend) |
| Internal docs pages | Fumadocs MDX under content/docs/ |
| APIs | Backend Fastify + Postgres conventions (API) |
4. Wire engineering hygiene
- Env contract (
.env.example) — no secrets committed - Auth boundary documented (Auth)
- CI / deploy path named (Deploy)
- Graphify / Cognee updated when the repo is durable (Agent tooling)
5. Ship the first vertical slice
Prefer one thin path (auth → one resource → one screen) over empty scaffolding.