Specialization kata · UX-002

Draw low-fidelity screens and wire the flow

Turn the sitemap into greyscale screens at phone size, wired into a clickable prototype that reaches every state, errors included.

Draft. This recipe is a draft. Its checks may not have been run, and it can change.

Status
Draft
Kata ID
UX-002
Maintainer
UX pathway maintainer
Last verified
Not available. Built and checked by the Dojo maintainers; no independent review yet.
Found a problem?
Report it

The outcome

Greyscale 390 px screens for every Pocket Invoice state, wired so a person can click from sign-up to a sent invoice and through every error.

For: Learners who have a sitemap and want to test it before choosing colours or type.

Done when

  • There is one board per state, at 390 px wide, with no colour except greys
  • Every transition in the sitemap is a working interaction in View mode
  • Errors that no button causes are marked as prototype-only links, so the prototype can still reach them
  • A partner finishes the happy path without being told where to click

You make: Wireframe set, Prototype. Outcome: Connect wireframes.

Showcase and provenance

The Dojo’s worked example, made by the maintainers rather than by a learner: Pocket Invoice as an editable Penpot file, a token file and a working, accessible page.

See the showcase

Made by
Developer Dojo maintainers
Source
Generated from the Pocket Invoice flow and tokens with Penpot’s official library
Licence
MIT
Date

Brief, inputs and constraints

Inputs

  • Your sitemap from UX-001. Source: Your own Penpot file. Terms: Your work.
  • Page 02 of pocket-invoice.penpot. Source: The UX pathway page. Terms: Dojo content, MIT licence.

Constraints

  • Fictional data
  • No personal data
  • No paid tools

Capabilities practised

  • Design interaction
  • Map flows

Stack, permissions and cost

Stack components with version, permissions and cost
PartComponentVersionPermissionsCost
ToolPenpot (self-hosted or penpot.app)2.18 (the example file was checked on a self-hosted 2.18.7)Edit one practice project of your ownPenpot Professional plan: $0, up to 8 members and 10 GB, no file limits (penpot.app/pricing, checked 2026-11-20). Self-hosting is free under MPL-2.0; you pay for your own server.
HarnessAny chat assistant in a browserNot available. Not fixed; any assistant can draft the text, and its version changes the wording, not the checksReads only what you paste into it; it never touches the design fileNot available. Depends on your assistant and plan; not measured
InstructionsThe prompts on this pageDraft, 2026-11-20NoneNone
DataPocket Invoice, an invented invoicing appFlow spec of 2026-11-20: 11 states, 19 transitionsFictional; no real company, person or customerNone

Stack recipes

  • Penpot and browser
  • Assistant and browser

Why this stack

Penpot is open source, runs in a browser, can be self-hosted and has a free plan with no file limits, so every learner can open the same editable file. The assistant only drafts text you check; the design work and the checks stay with you.

Alternatives

  • Figma. Widely used. The free Starter plan allows unlimited drafts but is limited elsewhere (for example 20 MCP tool calls a month); Professional seats cost $3 to $16 a month and there is no self-hosting (figma.com/pricing, checked 2026-11-20). The example file is Penpot-only and has not been tried in Figma. Not tested for this recipe.
  • Penpot MCP server with an agent. Lets an agent edit the open page directly, but uses a personal key with no permission scopes. Not run for this pathway: no native write by an agent was verified. Not tested for this recipe.

Agents and review gates

  1. Drafting assistant

    Writes the words for each screen (headings, labels, hints, error messages) from the sitemap.

    Review gate: You compare every line with the flow and the done-when list before it goes into Penpot.

  2. Reviewer

    Clicks through View mode and lists every transition that does not work or lands on the wrong board.

    Depends on: Drafting assistant

    Review gate: A finding counts only when the reviewer can point to the board, layer or line it is about.

Setup and smoke test

  1. Open Penpot in a browser: sign up at penpot.app, or use your own self-hosted instance.
  2. Download pocket-invoice.penpot from the UX pathway page and import it (Projects, then Import .penpot).
  3. Open each of the four pages once in the workspace before you use View mode, so Penpot lays out the text.

Sign-in and access: Your own Penpot account. The chat assistant needs no access to Penpot.

Smoke test

Do
Open page 02 in View mode and click Create workspace without filling the form.
Expect
The prototype moves to the sign-up error state.
Result
Passed /examples/ux-pathway/penpot-import-check.json (checks import, pages, text-layout-02 and text-layout-04)

Prompts

Copy a prompt into the assistant you use. Replace anything that does not fit your situation, and never paste private or personal data you are not allowed to share.

Write the screen words

Gets plain headings, labels and error messages for each state.

You can also select and copy the text.

Practice exercise

Prototyping (Penpot user guide). From Prototyping (Penpot).

Terms: Read on the publisher’s site under its terms.

Execution and handoffs

  1. Drafting assistant: Write the words for every screen with the prompt. Hand-off: You check the words against the sitemap.
  2. Learner: Draw one greyscale 390 px board per state and add an interaction for every transition: navigate, open overlay for the dialog, close overlay for Keep editing. Hand-off: The prototype goes to a partner in View mode.
  3. Reviewer: Click through every path and list what does not work. Hand-off: You fix each finding.

Tests, failures and corrections

Checks with expected and recorded results
CheckExpectedResultEvidence
Click through page 02 of the example in Penpot View mode, along every transitionEvery one of the 19 transitions lands on the right board, with no page errorPassed on /examples/ux-pathway/penpot-import-check.json (interactions-02, flow-02 and prototype-walk-02; screenshots in /examples/ux-pathway/screens/)
A partner clicks through your own prototype without helpThey finish the happy path and one error pathNot runNot run, so there is no evidence. This is not a pass.

Failures and corrections

No failures have been recorded.

Adapt it

  • The screens are for a 1280 px desktop as well as a phone. Draw desktop boards for the screens with the most content and check that the reading order stays the same.
  • The dialog becomes a separate page. Replace the overlay with a navigate interaction and add a way back, then check the walk again.

Unseen Randori

See the UX Randori recipe.

Constraints

  • Greyscale only
  • Every transition wired

How it is judged: A partner clicks through without help.

More Randori challenges

Belt evidence

Belt stages are proposed practice stages, not issued credentials. Evidence below is what a reviewer would look for; it is not a record that anyone has shown it.

Evidence a reviewer looks for

  • A click-through in Penpot View mode reaches every transition in the sitemap (Self-check)
  • A partner who has not seen the sitemap completes the happy path and one error path in View mode (Peer review)

Belt criteria

  • Practice: Clicks through page 02 of the example file and reaches every state
  • Adapt: Adds the screen for a new state and wires it both ways
  • Demonstrate: Builds low-fidelity screens for the Randori flow that a partner can click through without help

See the belt stages · Prepare a practice review

Connections

Used by
No other kata names this one as a foundation yet.
Professional review
Not required for practice. Real work in a regulated field still follows that field’s rules.

Sources

  • Penpot

    Prototyping (opens the publisher's site in a new tab)

    • Free
    • Docs
    • Beginner

    Penpot explains how to connect boards into interactive user flows and preview them. Use any assistant to propose a flow, build it in your own file, then test the navigation and review the result. The guide is public; editor access and any optional integration depend on your setup and permissions.

Maintenance and caveats

Review cadence: Every six months, or when Penpot changes its file format or token import

  • This recipe is a draft: the example was built and checked by the Dojo maintainers, and no learner has run it yet.
  • Penpot plans, versions and features change; check penpot.app/pricing and help.penpot.app before you rely on a limit.
  • The example file was checked on a self-hosted Penpot 2.18.7. Penpot cloud (penpot.app) was not checked.

All kata recipes · Back to katas