Glyph kit

Every kind

45 figures,
6 that move.

Each is drawn here by the kit itself, from its example data. All of it is sample data, and it says so on the figure.

Research data

Turn interviews, surveys and usability tests into evidence a team can read in a PR or a ticket. Every figure keeps who said it and where it came from.

Likert answers

A survey question answered on a five-point scale, compared across questions.

Watch for: Show the counts or percentages; never hide neutral answers, they change the story.

Themes by participant

Synthesis after interviews: which themes came from how many people.

Watch for: A theme from one loud participant looks small here, which is the point. Keep participant codes, never names.

Affinity counts

Counting notes per cluster after an affinity session.

Watch for: State what was counted (notes, people, sessions) in the title.

Quote card

Evidence for a finding, quoted exactly.

Watch for: Quote verbatim, cite the session and time, and never attach a real name without consent.

Task results

Usability test timings and completion.

Watch for: With fewer than about eight people, report the range and the completions, not a confident median.

Journey feeling

How a journey felt, stage by stage.

Watch for: The score is a judgement from research, say whose and from what.

Experiments and metrics

Funnels, cohorts, test results and the everyday charts. Numbers are always printed next to the bars, so a reader or a model reads them instead of estimating lengths.

Funnel

Steps people drop out of.

Watch for: Use the same time window for every step.

Retention cohorts

Retention by start month or week.

Watch for: Newer cohorts have fewer periods; blank is not zero.

Test result

A test result with confidence intervals.

Watch for: Overlapping intervals mean no clear difference yet; don't round that into a win.

Metric panel

A few metrics at a glance with their trend and change.

Watch for: Up isn't always good: time and tickets should go down. Say which way is better.

Bar chart

Ranked quantities.

Watch for: Sort first; one scale per document; value as text on every row.

Forecast

Measured values with a projection in the same bar.

Watch for: Say how the projection was made in the legend line.

Meter

Usage against a cap or quota.

Watch for: Over 100%, the bar stays full and the word over says the rest.

Sparkline

A trend inside a sentence or a table cell.

Watch for: Print the first and last values; a sparkline has no axis.

Heatmap

Density over a grid, such as activity by weekday.

Watch for: Five levels is the limit people can tell apart.

Calendar strip

Yes or no per day.

Watch for: Put date labels over the exact columns they name.

Comparison

Two versions of the same measures, side by side.

Watch for: Every row needs its own unit in the text; ten cells is enough.

UX flows

Agree on paths, states and journeys before anyone designs a screen. Text flows are quick to change in review and easy for an agent to turn into routes and state.

Flow with decisions

A flow with decisions and failure paths.

Watch for: Every decision's no-branch needs a destination, or it's a dead end nobody designed.

State machine

Anything with loading, saving, error or retry states.

Watch for: Read the footer: it lists ends and unreachable states.

Journey map

Stages of an experience with what people do, think and feel.

Watch for: Thoughts are quotes or close paraphrases from research, not invented.

Linear flow

A short linear sequence.

Watch for: Four or five boxes per row at most.

Tree or sitemap

Sitemaps, IA, file layouts, spec folders.

Watch for: Past three levels deep it stops being readable; collapse the rest.

Planning

Roadmaps, priorities, ownership and decisions in a form that lives next to the work and diffs when plans change.

Now, next, later

Now, next, later, or any set of columns.

Watch for: Keep items short enough to fit two lines.

Impact and effort

Choosing what to do first.

Watch for: Scores are estimates; write who scored them.

Swimlane

Who does what, in what order, across roles.

Watch for: One action per row; returns go left once.

Timeline

Release plans, animation tracks, anything over time.

Watch for: One scale for all rows; print start and end as text.

Status key

A legend for status across documents.

Watch for: Keep the same mapping in every document of a project.

Decision log

Recording what was decided and why.

Watch for: Write the why as evidence, not opinion.

Wireframes

Screens built from a small set of primitives. The same primitive names map to real components in the design-system map, which is what lets a text wireframe become a prototype and then production code without reinterpretation.

Screen wireframe

A layout proposal: content, order and controls before visuals.

Watch for: One screen per sketch; notes go outside the frame; use only the primitives so the map can translate them.

Responsive pair

The same screen at two widths.

Watch for: Show what moves or disappears, not just a narrower copy.

Design system

Document the design system as data: scales, contrast, component states, layers and tokens. Contrast is computed, not eyeballed.

Spacing scale

Documenting spacing tokens.

Watch for: State the unit per cell under the chart.

Type scale

Documenting type sizes and line heights.

Watch for: Sizes in one unit; bars compare size, not weight.

Contrast check

Checking colour pairs against WCAG 2 thresholds.

Watch for: AA needs 4.5:1 for body text and 3:1 for large text and UI parts.

Component states

Which component states exist, are in progress or missing.

Watch for: Blank means the state doesn't apply; missing is ░.

Layer stack

z-index and surface order.

Watch for: Name what each layer is for, not just its number.

Token table

Listing tokens with their values and uses.

Watch for: Inside Markdown, a Markdown table is easier to edit.

Table

Tables in places without Markdown: terminals, code comments.

Watch for: In Markdown, use a Markdown table.

Handoff and QA

Measurements and checklists for handing work to engineering and checking what came back.

Spacing redline

Spacing and widths for handoff.

Watch for: Widths are proportional but labels carry the real numbers.

QA checklist

Design QA before release.

Watch for: Blocked items need a reason in words.

Comparison

Two versions of the same measures, side by side.

Watch for: Every row needs its own unit in the text; ten cells is enough.

Motion

Write motion down as a decision before anyone animates it: why it moves, what starts it, how long, which curve, and what reduced motion shows instead. The HTML form plays it.

Motion intent

Deciding a single motion before building it.

Watch for: No intent, no animation: if 'why' is empty, cut it. Reduced motion is designed, not 'none'.

Transition spec

One transition, property by property.

Watch for: Animate transform and opacity; anything else needs a measured reason.

Stagger

Several elements entering in sequence.

Watch for: Cap the total: past about 400ms the last item feels late.

Frame strip

Seeing an easing curve frame by frame.

Watch for: Rows are equal slices of time, so bunched marks mean slow movement.

Motion timing

Comparing durations and easing, today against proposed.

Watch for: Keep the 500ms scale fixed across a report; a + is usually the finding.

Easing tokens

Documenting easing tokens.

Watch for: Three or four curves cover most products.

Moving diagrams

A process over time. Each plays on screen and keeps a still that makes the same point, for reduced motion, print and docs.