/ skills /style-guide
Skill · Claude Code

style-guide

Agree on your site's design rules once, then keep them

Use it when The same kind of inconsistency keeps turning up across pages, like three heading sizes or two card styles, and you want one site-wide rule instead of fixing it page by page.

Try it: paste this into Claude Code
Use the style-guide skill to audit my whole site for inconsistent headings, spacing, colors and card styles, and propose rules.
24 featuresReal rendered examples, never descriptionsNothing changes until you approve it

1What it audits

01

Starts From What's Decided

Reads your existing rules first and never re-asks

If your project already has a written style guide, or rules saved from an earlier run, those count as decided. Run it again anytime and it only proposes what is new or still inconsistent, so the guide grows over time.

02

The Whole Site at Once

Type, spacing, color and components across every page

It scans all your pages for headings, body and small-print sizes, spacing on phone and desktop, color use, repeated components like cards and headers, disclaimers and dark mode. Anything already scheduled on your to-do list is left alone.

03

Ratify What You Already Do

Patterns you've settled on become official rules

When the site already does something one way in practice, it is shown once with its exact code, so you can confirm it as the official rule rather than leave it as habit.

04

Settle the Real Splits

A recommended option and alternatives for open questions

Where pages genuinely disagree with no clear winner, you get a recommended option plus one or two alternatives to choose from, each one rendered.

2What you see

05

Seen, Not Described

Every option rendered at its real size, side by side

Each item shows the actual compared styles at their real size, color and weight, with representative text from your site. You choose between two things you can see, never between two class names.

06

The Recipe Beside It

The exact code for each style, ready to reuse

Next to each example sits the exact markup or classes that produce it. Once a rule is accepted, the recipe is what everyone copies.

07

Jump to a Category

Filter tabs with a count for each category

A big audit gets clickable tabs, one per category with its item count, so you can work through color without scrolling past every typography item. Only categories with items this round appear.

08

Color-Coded Categories

Each category has its own colored chip

Every item carries a chip in its category's color, matching its filter tab. Scanning a long page by eye gets much faster.

09

A Key to the Colors

One legend explains the decision colors

A small key near the top maps each decision color to its meaning, so the progress bar and button states make sense without rereading every button row.

10

Light and Dark Preview

Flip every example between your light and dark looks

If your site has both themes, one switch shows every example in either one, separately from the review page's own theme. A contrast problem that only appears in dark mode is visible before you approve.

11

An Honest Opinion

Each item comes with a reason and a recommendation

Every item explains why it is proposed and carries a Recommended or Not Recommended badge, so you know where Claude stands before you decide.

3How you decide

12

Four Clear Choices

Deny, revise, fix everywhere now, or record for later

Each item has Deny, Request Revision, Accept – Apply Everywhere Now and Accept – Record for Later. You decide both whether the rule stands and when existing pages catch up.

13

Works as Designed

Say no and still record why the difference is on purpose

A Works as Designed checkbox on Deny records the current state as the rule, with your comment as the reason. Two things that look inconsistent but are meant to differ get documented instead of flagged again next time.

14

A Note on Anything

An optional comment box on every decision

All four choices take an optional comment. On an Accept it adjusts the rule and the fix, so you never need a separate approve-with-changes button.

15

One Paste Back

A progress bar and Copy My Decisions stay in view

A bar pinned to the bottom shows how many items you've reviewed and a count per decision. One button copies a plain summary that you paste back into chat.

4After you decide

16

Fix It Everywhere Now

Accepted rules can be applied to every page at once

Choose Apply Everywhere Now and every page that does it differently is updated to match, in the same pass, with your comment folded in.

17

Or Record It for Later

The rule is saved now and the cleanup goes on your to-do list

Choose Record for Later and the rule is written down immediately, while updating the existing pages becomes a to-do entry naming which pages and what the rule is. It doesn't get lost.

18

A Living Style Guide

Accepted rules collect in one guide page you keep

Every accepted rule lands in a style guide page in your project, sorted by category, each with its example, its code and a one-line rule. It is republished to the same link every time.

19

Future Sessions Follow It

Your project instructions point new work at the guide

It checks that your project's instructions for Claude point at the style guide, and if they don't, proposes adding the pointer and waits for your go-ahead, since that file is yours. Later work starts from your rules instead of reinventing them.

20

Optional: A Hidden Address

Opt-in only: served on your site after you approve

If you want it, the guide can also be served at an unlinked address on your own site, like /styleguide, always showing the saved version. This is optional and opt-in, and it is never set up without your explicit approval.

21

Tested Before You See It

Every button is clicked before the page reaches you

Before each publish, the review page is loaded and clicked through automatically, including picking an option, to confirm the buttons work and nothing scrolls sideways.

5Rounds

22

Just What's Still Open

The next round brings back only undecided items

A follow-up round shows every item without a final decision, with last round's proposal carried forward and labeled. It goes up at the same link.

23

Settled Items, Dimmed

Related decided items stay visible for context

When a settled item helps explain a new one, it stays on the page, dimmed, so you see the connection without being asked to decide it again.

24

Where the Page Goes

A private link, a local file, or your Wi-Fi

Your project picks where review pages go: a private claude.ai link, an HTML file that opens in your browser, or that file served on your home Wi-Fi so a phone can open it. Nothing is ever uploaded or tunneled in the Wi-Fi mode, and the server stops when the review ends.