Free lesson · Skill · 6 min
The feature card
Part of Vibe Coding Foundations
The one idea
A feature card is one buildable chunk — not the whole app. Each card has:
- Name — one feature in plain English
- Acceptance criteria — how you judge done (checklist)
- Constraints — what must not change or be added
- Tests — three manual steps a non-coder can run
Example: "Mark action done" — criteria: checkbox persists after refresh; only owner can mark; empty list shows helpful message. Tests: add action, mark done, refresh page.
Why one feature per card
Agents and chats do better with one job. You review one diff. You know exactly what broke if something fails.
Your win today
Write one feature card for the smallest shippable slice of your app.