synthesis-of-formlisted
Install: claude install-skill imikailoby/claude-skills
# Synthesis of Form — structural UI/UX method
Design is achieving **fit** between **form** (the interface) and **context** (everything the interface must answer to). Fit cannot be observed directly — only **misfits** can. So the method works negatively: hunt misfits, map how they interact, fix them piecemeal.
Run the steps in order whether architecting new UI or critiquing existing UI; when architecting, step 2's misfits are anticipated rather than observed.
## 1. Name the ensemble
Write down both halves before judging anything — the design object is never the form alone, always the ensemble:
- **Form**: screens, components, information architecture, interaction patterns, visual system, microcopy.
- **Context**: user goals and tasks, usage situations (device, environment, interruptions, time pressure), user characteristics (expertise, impairments, domain language), business and technical constraints.
Done when: someone reading the two lists could tell what would count as a failure.
## 2. Enumerate misfits
A misfit is a concrete point of stress in the ensemble — never "bad design" in the abstract. Every misfit names a form element AND the context condition it fails under: "the save action (form) is undiscoverable under time pressure on mobile (context)".
Sweep each category:
| Misfit | Stress |
|---|---|
| Conceptual | labels or model clash with users' mental model |
| Affordance | interactive reads as static, or static as interactive |
| Feedback | state changes inv