01UI state checklist: Empty, loading, error and recovery
Use a UI state checklist for empty, loading, success, error and recovery. Copy the worksheet, record missing states and keep each observation with its source.
Read articleQuiet field notes about capture, design memory, and making references useful to the agents beside you.
01Use a UI state checklist for empty, loading, success, error and recovery. Copy the worksheet, record missing states and keep each observation with its source.
Read article
02Document responsive design behaviour with a copyable worksheet. Record viewport conditions, layout changes and unknown breakpoints for a clearer handoff.
Read article
03Document UI motion references with a copyable handoff worksheet for triggers, timing evidence, interruptions and a reduced-motion alternative.
Read article
04Annotate design references with a target, observation, interpretation and proposal. Copy the worksheet and follow a worked filter-panel example.
Read article
05Run a task-based UX competitive analysis with a copyable worksheet. Compare the same task, preserve evidence and turn observations into a testable hypothesis.
Read article
06Learn what a visual reference library contains, how it differs from a moodboard, and how to build one you can retrieve from later.
Read article
07A lightweight system for organizing design inspiration by future decisions, with fewer tags, useful notes, and a review habit.
Read article
08A practical Chrome workflow for saving website inspiration with its source, rationale, capture state, and a retrievable label.
Read article
09Compare moodboards and visual reference libraries by purpose, lifespan, structure, and the design decisions each one supports.
Read article
10Understand what a link, screenshot, preview, and durable capture preserve—and choose the lightest format that supports your design decision.
Read article
11Convert a pile of visual references into a focused design brief with sourced principles, constraints, decisions, and explicit unknowns.
Read article
12Give coding agents focused visual evidence, explicit constraints, source-linked decisions, and a runnable acceptance check instead of a vague style prompt.
Read article
13A source-aware method for turning repeated visual decisions into candidate design tokens without pretending screenshots contain exact systems.
Read article
14Preserve where a design reference came from, what was captured, and how your notes derive from it so evidence remains useful and auditable.
Read article
15Understand what local-first means for a visual reference library, including control, offline access, sync, deletion, backups, and private-source boundaries.
Read article
16Build a web design moodboard that connects references to type, imagery and layout decisions. Use a worked example and a practical approval worksheet.
Read article
17Create a brand moodboard with a clear positioning link, meaningful visual choices and an approval record. Includes a worked example and review worksheet.
Read article
18Build a logo design moodboard around visual mechanisms, context and useful constraints. Includes a worked research example and a sketch handoff checklist.
Read article
19Create a photography moodboard that explains light, crop and subject direction. Use a feasibility worksheet to turn references into shots and fallback plans.
Read article
20A moodboard defines visual direction; a storyboard explains a sequence. Compare their roles with a product-film example and a practical decision diagram.
Read article
21Choose a style tile or moodboard by what needs approval. Compare their scope, build a bookstore direction, and separate visual agreement from layout sign-off.
Read article
22Choose website fonts with a same-copy audition: test reading, language coverage, weights, licensing and fallback behavior before committing to a family.
Read article
23Try five website font pairing recipes, then test optical size, role contrast, real copy and fallback behavior instead of trusting a pairing chart alone.
Read article
24Build website typography hierarchy with clear text roles, a starting scale, semantic headings and mobile spacing checks. Fix flat type without adding fonts.
Read article
25Create a website color palette by assigning roles and checking actual foreground-background pairs. Use a worked neutral palette and avoid the five-swatch trap.
Read article
26Run a design critique with a clear question, a 30-minute agenda, useful feedback prompts and a decision record. Keep taste, evidence and approval separate.
Read article
27Keep a design decision log with context, alternatives, evidence and a clear reopen condition. Copy the record structure and follow a completed checkout example.
Read article
28Use a design handoff checklist that ties flows, states, assets and responsive rules to an owner and a check. Includes an upload example and developer playback.
Read article
29Fix website visual hierarchy with a clear page priority, an emphasis budget and scan, keyboard and mobile checks. Includes a service-page example.
Read article
30Design a hero section that explains the offer, earns trust and gives a clear next step. Use three copy examples plus image, mobile and loading checks.
Read article