Design in Claude
<level>10</level> · Lesson 2 of 7 · 45 min Free lesson+100 XP

Make your app's rulebook and teach it to Claude

<you-will-learn>

  • The 7 parts of every app rulebook
  • Making yours from screenshots, one step at a time
  • Checking it on one page, then installing it in Claude
  • Testing it and fixing what's missing

In Lesson 1 we learned the big idea: write your app's rules down once, and Claude follows them forever. Today you make that rulebook. Grab your my-app-screens folder from the Level 0 side quest.

How I did this levelThe first rulebook I made was for the design system I'd built at work. I already had colours and components in Figma, but they lived in my head and in files nobody read. I spent one evening with Claude turning them into a skill: colours with names, a spacing scale, my ten most-used components, and a list of things we never do. The next morning I asked for a screen in a fresh chat — and for the first time, it looked like our app. Not perfect. But ours. Everything since has been adding rules.
Two ways to do this lesson: do every step yourself by chatting with Claude (free, about 45 minutes — and you'll understand your rulebook deeply), or use the Brand-to-Skill skill from the pack, which runs all the steps for you in about 15 minutes. Both give the same result. We recommend doing it by hand once.

What goes in a rulebook?

Think of it like the instructions in a LEGO box. Seven parts:

PartWhat it meansEveryday example
1. ColoursWhich colour does which job“Main buttons are dark green. Background is cream.”
2. TextFonts and sizes for titles, normal words and small notes“Titles are 24, bold. Notes are 13, grey.”
3. SpacingHow much empty room goes around things“Always 16 between cards, 20 at the screen edge.”
4. PiecesWhat buttons, cards, lists look like — in every state“Buttons are full width; grey when disabled.”
5. VoiceHow the app talks“Say ‘Add money’, not ‘Initiate transfer’.”
6. Never listThings your app never does“Never purple. Never fake text.”
7. Self-checkA checklist Claude runs before showing you anything“Did I only use our colours?”

No app yet? Start from references

Building something brand new, with no screens to screenshot? Don't invent a style from nothing — that's exactly how generic AI UI happens. Borrow on purpose instead:

  1. Pick 4–6 apps or sites you love. Good free places to look: Mobbin (real app screens), Refero, Pinterest, Dribbble.
  2. Write one thing you like about each. Be specific: “the calm cream background”, “the big bold numbers”, “the chunky black buttons”.
  3. Ask Claude to remix them into one system (below). Then continue from Step 1 with the result instead of screenshots.
I don't have a design system yet. My product is [one line] for [who]. It should feel [3 words]. Here are apps I love and what I like in each: [list]. Make a remix table: one row per design decision, which reference it comes from, and the value you propose. Take ideas, not identities — the result must look like a new product, not a copy.
With the pack: say I don't have a design system — start from references and Brand-to-Skill runs this for you.

Step 0 — Start a project (2 minutes)

In Claude, create a Project called “[Your app] design system” and upload your screenshots to it. A project keeps files and chats together, so you don't have to re-upload every time.

New word: projectA folder inside Claude that holds files and chats about one topic. Every chat inside it can see those files.

Then open a new chat inside the project and type:

I want to build a design system for my app from these screenshots, step by step. Don't build anything yet. First, describe what you see: the overall feel, colours, text, spacing and the main pieces (buttons, cards, lists). Then tell me what you can't tell from the screenshots.

What you should see: a description of your app and a list of open questions (for example “I can't see a disabled button”). That list is gold — those are the gaps generic AI fills with guesses.

Step 1 — Give every colour a job

“Green” tells Claude nothing about when to use it. “Main button colour” does.

List every colour you see in the screenshots with its hex code. Then give each one a job from this list: page background, card background, subtle background, main text, light text, text on buttons, main button, main button pressed, accent, light accent, border, success, warning, error. If a job has no colour, suggest one that fits.
New word: hex codeA colour written as a code, like #0F3D2E (a dark green). Computers use it to get exactly the right colour.
New word: tokenA colour or size with a name that says its job, like color-action-primary instead of “green”. Names help Claude pick the right one every time.

Check it: are any two colours almost the same? Merge them. Is there a colour with no job? Remove it. Fewer colours, each with one job, is the secret.

Step 2 — Text sizes

Now text. What font does the app use (or the closest free one)? Make a type scale: display, h1, h2, body, small and label — each with size, line height and weight. Base it on what you see in the screenshots.

What you should see: a small table with six rows. If your app uses a custom font you can't name, say “use Inter as a stand-in” — it's free and close to most app fonts.

Step 3 — Measure the breathing room

Most AI designs feel “almost right” because the spacing is off, not the colours.

Measure the spacing in the screenshots: the gap at the screen edge, inside cards, between items in a list, and between sections. Turn it into a spacing scale on a 4px grid (4, 8, 12, 16, 20, 24, 32, 48). Also tell me the corner roundness of buttons, cards and sheets, and whether the app uses shadows or borders.

Step 4 — Describe your 5 most-used pieces

Usually: a button, a text box, a card, a list row, and one piece special to your app (a price tag, a progress bar, a seat).

Write a recipe for each of these components: button, text input, card, list row, and [your special piece]. For each: what it's made of, its variants (like primary and secondary), every state (default, pressed, focused, disabled, loading, error), sizes, and which tokens it uses. Keep each recipe short.
New word: stateThe different ways one thing can look. A button can be normal, pressed, disabled (greyed out) or loading (spinning).
New word: componentA reusable piece of a screen, like a button or a card. Same piece, used everywhere.

Step 5 — Voice: how your app talks

From the words in the screenshots, write voice rules: tone in 3 words, how buttons are written (verb first?), how errors are written, how money, dates and numbers are formatted, and 10 words to avoid.

Step 6 — Write your Never list

This is the secret weapon against boring AI looks. Start with these and add your own:

  • Never use a colour that isn't a token
  • Never add gradients or shadows unless the app has them
  • Never write “Lorem ipsum” or fake names like “John Doe” — use realistic content
  • Never put a card inside a card
  • Never centre a page title unless the app does
  • Never use more than one main button per screen
Add a Never list to the design system. Include these: [paste the list]. Then add 5 more based on what would make a screen look generic compared to my app.

Step 7 — Look at it all on one page

Make a specimen page as an artifact: every colour with its name and hex, every text size, the spacing scale, and the five components in all their states.

Put it next to your real screenshots. Does it feel like your app? If something's off, don't fix the page — fix the rule: “The main green is too bright, use #0F3D2E.”

Specimen page showing a rulebook's colours, text and pieces
Saffron's specimen page: the whole rulebook on one page.

Step 8 — Turn it into a skill and install it

Turn everything we decided into a design-system skill folder: a SKILL.md with the rules, the Never list and a 10-point self-check, a tokens.css file, and a DESIGN.md that describes the same system in plain markdown. The skill should load whenever I ask to design a screen for [app name]. Give me the folder as a zip.
New word: DESIGN.mdAn open, plain-text format for describing a product's look to any AI tool. Your Claude skill is the engine; DESIGN.md is a copy you can hand to other tools or to teammates who don't use Claude.

Then install it:

  • Claude website or app: Settings → Capabilities (or Skills) → Upload skill → pick the zip. Make sure it's switched on.
  • Claude Code (for people who code): unzip it into ~/.claude/skills/.

Menu names change as Claude updates. If you can't find Skills, search “skills” in Claude's help centre.

Step 9 — The real test

Open a brand-new chat (not inside the project) and type one line:

Design the settings screen for [app name].

What you should see: a screen that looks like your app, with no other instructions. If it does — congratulations, that's the whole trick working.

If it goes wrongLooks generic? The skill may not have loaded — check it's switched on, and mention the app name in your message. Colours right but feels off? Usually spacing or component recipes — add more detail there. One specific mistake? Ask: “What rule would have prevented this? Add it to my design system and give me the updated skill.”

How the rulebook grows

Write every new rule as one sentence + the reason + the date:

Sheet top edge is 54px or 102px, never in between — anything else cuts the iOS nav bar (2026-11-18)

The reason matters more than the rule. When Claude meets a case nobody wrote down, the reason is what it thinks from. And the date tells you which rules are old enough to question.

Your rulebook is never finished, and that's good. Every time you correct Claude, ask yourself: “will this happen again?” If yes, turn it into a rule. After a few weeks your rulebook will know your app better than any written style guide — because every mistake made it better.

With the pack: type Set up my design system for <my app> and drop in your screenshots. Brand-to-Skill runs Steps 1–9, asks you a few easy questions in one go, builds the skill, the tokens file and the specimen page, and tests it on a real screen.
Checkpoint — you're Level 10 if you can tick these
  • My rulebook has colours with jobs, text sizes, spacing, 5 components, voice and a Never list
  • I've seen it all on one specimen page
  • It's installed as a skill and switched on
  • In a new chat, “design the settings screen” looks like my app

Side quest

Ask for three different screens in three new chats: a list, a form and a profile page. For each, note one thing that's wrong and turn it into a rule. Three rules added = your rulebook is already better than yesterday.