AI is best as a constraint enforcer. Use it to draft a one‑screen spec, then cut anything that doesn’t serve the single path.
One‑pager contents (must fit one screen)
- 6‑step user journey (one happy path)
- Minimal data model (entities + key fields only)
- Required UI only (screen + success state)
- 2 API stubs (POST /action, GET /status)
- Fake/stub plan (what you’ll mock or WoZ)
- 3 tests (happy, bad input, external failure mocked)
- Landing blurb (headline → value → CTA)
- Not‑Doing list
Example API stubs (Fastify)
// POST /action
app.post('/action', async (req, reply) => { /* validate input; enqueue work; return id */ });
// GET /status?id=...
app.get('/status', async (req, reply) => { /* return {{ id, state, result }} */ });
Not‑Doing list you’ll thank yourself for
- OAuth, teams, roles
- Fancy state machines
- “Nice to have” settings
Tip: If your one‑pager doesn’t fit a single screenshot, it’s not a one‑pager.
Grab the exact prompt + examples → https://shipwithai.substack.com/p/pasta-al-dente-ship-a-one-feature?utm_source=devto&utm_medium=social&utm_campaign=issue_pasta_al_dente_week
Top comments (0)