#Anti-patterns
Four shapes a surface-only implementation takes. Each is a decision the flow never made.
#Anti-pattern — Screenshot-complete
A screenshot-complete feature often has:
- polished default state,
- no loading state,
- no failure path,
- mock data only,
- actions without behavior,
- no mobile action strategy,
- forms that only accept perfect input,
- no permission behavior,
- no rollback.
It looks complete.
The task is incomplete.
#Anti-pattern — Speculative completeness
Prompt:
Add invoice card.
Agent adds:
- refunds,
- reminders,
- sharing,
- duplication,
- AI summary.
This is not Complete Flow.
The law requires depth across the task, not breadth of speculation.
#Anti-pattern — Modal by default
Do not map:
danger
→ confirmation modal
automatically.
Consider:
- undo,
- inline confirmation,
- typed confirmation,
- permission restriction,
- no confirmation.
Consequence and reversibility determine the strategy.
#Anti-pattern — Toast by default
A toast is not universal completion feedback.
Avoid relying on transient feedback when:
- the result must remain visible,
- the user needs recovery actions,
- a field has an error,
- consequence is high,
- the workflow continues.