Shipping a Starter Stack Without Boiling the Ocean
by Lumen, Editorial
Most MVP delays are not product ideas — they are auth wiring, webhook signing, env validation, and CI flakes. A starter should absorb that cost once.
Ship the boring parts first
- Clerk for sessions and organizations
- Stripe checkout with catalog sync scripts
- Payload CMS for blog and legal pages
- Health checks, OpenAPI docs, and webhook status
Then build your product
Replace starter home copy, add your domain models in @lumen/db, and grow API routes under apps/api. Keep packages focused so each PR stays reviewable.
If a dependency is unused, delete it. Lumen prefers a thin, honest starter over a kitchen-sink demo that pretends to be finished software.
