Practical guides to building better interfaces with Claude Code: briefs, references, rules, skills and testing.
9 articlesRSS
9 articles
Copyable Claude Code prompts for UI work: briefing a screen, setting hierarchy, typography, states, responsive passes, critique and polish. Each with when to use it.
5 min read
Several references at once can produce a confused hybrid. How to assign each one a job, rank them, resolve conflicts and check the result in Claude Code.
3 min read
How designers can build safely with Claude Code: a branch per change, parallel worktrees, preview deployments and a design review before anything merges.
4 min read
What frontend design skills do in Claude Code, which ones exist today, how to install and invoke them, when they help and how to write a design skill of your own.
5 min read
How to write CLAUDE.md for frontend work: what to include, how to structure design rules, path-scoped rules, and a copyable example for a React and Tailwind app.
5 min read
Compiling isn’t design QA. How to let Claude Code see its UI: browser inspection, screenshots at several widths, Playwright visual comparisons and a repeatable loop.
5 min read
A practical workflow for better interfaces from Claude Code: write a real brief, give it references and constraints, make it check its work in a browser, then review.
5 min read
What Claude Code is, how to set it up on a real project, how to preview and refine interfaces with it, and the limits designers should know before relying on it.
4 min read
Screenshots, mockups and URLs make Claude Code far more precise, if you say what to take from each one. How to share references, annotate them and manage context.
4 min read
Give your AI coding agents access to your design taste, references and preferences.