Design the prompt-interface for one of three feature briefs we provide (see the kit, or pick your own with a one-paragraph user-and-domain statement at the top of your narrative). The user is explicitly non-expert — assume they have never used a chat-style LLM tool.
Required deliverables
- Static prototype (Figma, Framer, or live HTML) showing: empty state with three contextual prompt chips, scaffolded input, streaming/in-progress state, output with inline citations or a paired uncertainty signal, refusal-as-redirect for one out-of-scope action, and an undo/regenerate/edit-and-retry surface.
- Interaction flow (≤ 6 frames) for the primary path, plus one agentic-UX frame showing how a long-running task surfaces progress and offers cancel.
- Annotations on every frame explaining the design decision and at least one rejected alternative.
- 60-second walkthrough video.
- ≤ 600-word narrative articulating: who the user is, the trust principle the design rests on, the riskiest design call you made and why, and one calibration moment in the onboarding.
Out of scope
- Production code. Static prototype is fine.
- A full design system. One feature surface is enough.
- Brand exploration. Use a neutral system; the rubric does not score brand.
What we look for
- Refusal-as-redirect rather than flat ''I can''t help with that''.
- Honest uncertainty — inline citations or qualitative bands, not unsupported confidence percentages.
- Visible agentic surface for any long-running task — named steps + cancel.
- Capability legibility — the user can tell which tools/skills are running without reading a manual.
How it's graded
One rubric — Design Foundations — applied at full weight. Four criteria: interface clarity (25%), uncertainty handling (25%), feedback and recovery (25%), design narrative (25%). Each criterion is scored 0–5 with a written rationale by the grader.