← Fancy UI Curriculum
Reading is open to everyone. Enrol to record progress, sit the graded test and earn the certificate — the learner is resolved from your account, never from a value the browser supplies.
Human+ UX — the capstone
The contract every interactive Fancy surface is held to, and the reason the suite exists. Passing its final test certifies you.
0/4 lessons
0%
Every surface owes two things, not one
~9 min
A Fancy surface owes two constraints:
- Authoring surface. Humans and agents can rapidly compose good-looking, working apps with it. Terse props, JSON-friendly inputs, sensible defaults, good types.
- Inhabited surface. The running app embeds agents as first-class participants. Agents read and write component state through MCP bridges and stable handles — not Playwright, not DOM scraping. The component itself is the agent's affordance.
Purely visual components — a static label, a divider, a layout shell — owe only the first. Anything stateful or interactive owes both.
The second is the one people skip, and skipping it is what produces a component that demos beautifully and cannot be driven.