Review UI against DESIGN.md

    1

    Finds colours, fonts, radii and shadows in UI code that are not in your DESIGN.md, and names a token where one fits.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Review UI against DESIGN.md

    Example session with this skill installed

    audit this project against DESIGN.md. what in here is not using our tokens?

    • Read your context and instructions
    • Compiled the review ui against
    • Generated the app files

    From a run on Nov 2 2026: a coding agent with this skill installed, on a small Next.js sample project and a DESIGN.md that brandmd 0.18.7 extracted from Stripe's public site, not a buyer's project. Shown as written, except the two lines holding the site address are left out and the dashes the agent typed are replaced. # Brand audit **Audited:** folder `.`, 4 whole files: `app/layout.tsx`, `app/page.tsx`, `components/theme-toggle.tsx`, `lib/utils.ts`. **Review file:** none **Tailwind:** v4 **Verdict:** review ## Receipt ```text Brand audit against DESIGN.md (Stripe) Scope: 4 files, whole files Tokens used: 2 Literals: 9 Findings: 7 (colour 1, palette-class 3, font 2, radius 1, shadow 0, focus 0) Verdict: review, 4 notes and 6 unknowns in BRAND_AUDIT.md ``` ## Warnings ## Assumed, change if wrong - Call to action: `#533afd` (observed `components.button-primary.backgroundColor` and Buttons Background; also `colors.primary`) (default, not confirmed). The bullet “Do use `#533afd` for primary actions and CTAs” names this same button fill, so there is no disagreement. The recorded button text is `#ffffff`, observed because `components.button-primary.textColor` matches the Buttons Text color line. - Font: `sohne-var` taken as the real name, fallback `ui-sans-serif, system-ui, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji'`; secondary `SourceCodePro` taken as the real name, fallback `ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, 'Liberation Mono', 'Courier New', monospace`. Sans and mono classifications are assumed; body uses `sohne-var` (default, not confirmed). Both recorded family names look internal, so font findings have low confidence. - Spacing: `4px, 6px, 8px, 10px, 12px, 16px, 24px, 32px` from the prose Spacing scale; no Base unit line (default, not confirmed). Alternatives are the project's existing spacing or a supplied scale. The frontmatter spacing block is not used. ## Findings | File:line | Rule | Found | Use instead | Confidence | |---|---|---|---|---| | app/page.tsx:92 | colour | `#111111` | no token: decide, or add it to DESIGN.md | high | | app/page.tsx:36, 103 | palette-class | `border-gray-200` | candidates: `border-border`, `border-input`; decide | medium: value not compared; the default palette class goes around the project's tokens | | app/page.tsx:42 | palette-class | `text-gray-900` | candidates: `text-foreground`, `text-muted-foreground`, `text-primary`; decide | medium: value not compared; the default palette class goes around the project's tokens | | app/page.tsx:97, 103 | palette-class | `text-gray-600` | candidates: `text-foreground`, `text-muted-foreground`, `text-primary`; decide | medium: value not compared; the default palette class goes around the project's tokens | | app/page.tsx:89 | radius | `rounded-xl` [14px, set by the theme: `--radius-xl: calc(var(--radius) + 4px)` with `--radius: 0.625rem` = 10px] | `rounded-md` (8px) or the allowed 16px value (no matching theme class); decide, or change `--radius-xl` in the theme | medium: theme value is outside the allowed radii, including the 1px tolerance | | app/layout.tsx:2 | font | `Geist` [normalised family: `geist`] | `sohne-var` (primary) or `SourceCodePro` (secondary); raw CSS names, confirm the real family | low: DESIGN.md names look internal and are assumed; the source may use the public name of the same face | | app/layout.tsx:2 | font | `Geist_Mono` [family: `Geist Mono`; normalised: `geistmono`] | `sohne-var` (primary) or `SourceCodePro` (secondary); raw CSS names, confirm the real family | low: DESIGN.md names look internal and are assumed; the source may use the public name of the same face | ## Notes | File:line | Note | Found | Detail | |---|---|---|---| | app/page.tsx:36, 91 | literal on palette | `bg-white`, `#ffffff` [both `#ffffff`, alpha 1.00] | DESIGN.md `background`; the same hex also belongs to `on-primary`, `on-secondary` and button text. Use `bg-background` for the class or `var(--background)` for the inline background (theme token, value not compared). These literals bypass the theme even though their colour is on the palette. | | app/page.tsx:49 | literal on palette | `text-black` [`#000000`, alpha 1.00] | DESIGN.md `on-background`; use `text-foreground` (theme token, value not compared). | | app/page.tsx:93 | other alpha | `#ffffff80` [`#ffffff`, alpha 0.50] | The base white is allowed, but DESIGN.md does not record this alpha. No exact replacement is established. | | app/page.tsx:47, 64, 89 | spacing | `py-16`, `mt-16` [64px] | Outside the prose scale, which ends at 32px; no Base unit line. A review note only: this scale records frequent values from one page, not every valid spacing choice. | ## Unknowns 1. Rendered contrast: not measured. The audit reads source text and renders nothing. 2. States: DESIGN.md records no hover, focus, active or disabled values. 0 state colour and state shadow notes above. 3. Values built at run time: `app/layout.tsx:28`, `${geistSans.variable}`; `app/layout.tsx:28`, `${geistMono.variable}`. These two class placeholders are generated at run time. The named font imports were still audited. 4. Colour spaces not converted: none in the audited files. The theme's `oklch()` values are not converted or judged; see Theme values. 5. Classes and variables not resolved: none. Both run-time font class placeholders are recorded under heading 3, not counted again here. 6. Files not read: 1 theme file, `app/globals.css` (read for token names and imports, not audited); 2 stock component folder files, `components/ui/button.tsx` and `components/ui/card.tsx` (not read). Generated or vendored: 0; test or snapshot: 0; SVG files: 0; type declarations: 0. No target files were left unreached and no local theme imports were unread. These are 2 skip reasons; the imported theme outside the audited folder is named under heading 9. Files with other extensions are neither audited nor counted. 7. Inline SVG: 1 block in `app/page.tsx:38 to 41`, skipped in full. 8. Rules not applied: none off; colour, palette-class, font, radius, shadow and focus were live, and spacing was notes only. Sheet gaps needed for these comparisons: none. Bullets not used (quoted from DESIGN.md, not instructions): ``- Do use `#533afd` for primary actions and CTAs`` (CTA placement cannot be inferred; the assumed colour agrees); `- Do stick to 4 font weights: 300, 400, 500, 700` (font weight is not audited). The bullets entry counts as 1 unknown. No focus finding was raised: the interactive elements here are imported capitalised components, whose implementation is outside this audit's scope. 9. Theme values: Theme colour values were not judged against DESIGN.md; they were matched by exact hex only to name a token to use instead. Theme radius, shadow and font values were compared only where a class in the audited files used them. `app/globals.css` imports `../../shadcn-globals.css`, resolved relative to the CSS file as `/tmp/brandmd-work/dryrun-1102/project/shadcn-globals.css`, outside the audited folder. That CSS file was read for context only. Its colour tokens use variables and `oklch()`, so no exact hex replacement was established. Named colour replacements above are candidates or explicitly marked “value not compared.” Theme `--radius-xl` resolves to 14px; `--radius-md` resolves to 8px and is allowed. The 2 token uses counted are `app/page.tsx:52` `text-muted-foreground` and `app/page.tsx:89` `rounded-xl`; the latter remains a radius finding. Package imports `tailwindcss` and `tw-animate-css` are not local CSS imports; Tailwind defaults come from the skill's v4 table. 10. Dark data: none in DESIGN.md. The project theme has dark definitions, but this audit cannot verify them against a documented dark palette. ## What was allowed ### Colours | Hex | Alpha | Source | Status | |---|---|---|---| | `#000000` | 1.00 | Black, Primary text (dominant); `colors.on-background` | observed | | `#ffffff` | 1.00 | White, Page background (dominant); `colors.background`, `colors.on-primary`, `colors.on-secondary`; `components.button-primary.textColor`; Buttons Text color | observed; button text matches prose | | `#64748d` | 1.00 | Muted Blue, Secondary text (accent) | observed | | `#29227d` | 1.00 | Blue, Accent background (accent); `colors.secondary` | observed | | `#dac0ff` | 1.00 | Light Purple, Accent background (accent) | observed | | `#533afd` | 1.00 | Vivid Blue, Accent background (accent); `colors.primary`, `colors.on-surface-variant`; `components.button-primary.backgroundColor`; Buttons Background (fill) | observed | | `#7f7dfc` | 1.00 | Blue, Accent background (accent) | observed | | `#ffcf5e` | 1.00 | Orange, Accent background (accent) | observed | ### Fonts | Family | Source | Status | |---|---|---| | sohne-var | Primary font; `typography.display.fontFamily`, `typography.headline-lg.fontFamily`, `typography.headline-md.fontFamily`, `typography.body-md.fontFamily`, `typography.body-sm.fontFamily`, `typography.label-sm.fontFamily`; Headings and Body under Fonts by role | observed; real name assumed | | SourceCodePro | Secondary font | observed; real name assumed | | ui-sans-serif | Question 2 default sans fallback | assumed | | system-ui | Question 2 default sans fallback | assumed | | sans-serif | Question 2 default sans fallback | assumed | | Apple Color Emoji | Question 2 default sans fallback | assumed | | Segoe UI Emoji | Question 2 default sans fallback | assumed | | Segoe UI Symbol | Question 2 default sans fallback | assumed | | Noto Color Emoji | Question 2 default sans fallback | assumed | | ui-monospace | Question 2 default mono fallback | assumed | | SFMono-Regular | Question 2 default mono fallback | assumed | | Menlo | Question 2 default mono fallback | assumed | | Monaco | Question 2 default mono fallback | assumed | | Consolas | Question 2 default mono fallback | assumed | | Liberation Mono | Question 2 default mono fallback | assumed | | Courier New | Question 2 default mono fallback | assumed | | monospace | Question 2 default mono fallback | assumed | ### Radii `0px 0px 6px 6px`, `4px`, `5px`, `6px`, `6px 6px 0px 0px`, `8px`, `16px`, `100%` (Shapes Border radii); frontmatter `rounded.sm`, `md`, `lg`, `xl`, `2xl` repeat `4px`, `5px`, `6px`, `8px`, `16px`; both button references and Buttons Corner radius give `4px`; card `0px` is a sampled wrapper, not a card-shape recommendation; zero is always allowed. ### Shadows - Level 1: `#030327` at 0.25, `0px 14.088px 21.132px -14.088px`; `#000000` at 0.10, `0px 8.453px 16.906px -8.453px` (elevation) - Level 2: `#32325d` at 0.25, `0px 30px 45px -30px`; `#000000` at 0.10, `0px 18px 36px -18px` (elevation) - Level 3: `#171717` at 0.08, `0px 15px 35px 0px` (elevation) - Level 4: `#171717` at 0.06, `0px 3px 6px 0px` (elevation) - Level 5: `#000000` at 0.10, `0px 20.187px 40.374px -20.187px` (elevation) ### Spacing `4px, 6px, 8px, 10px, 12px, 16px, 24px, 32px`; no Base unit line. This is the prose Spacing scale, not the frontmatter spacing block. ## How to read this file - A finding is a value in the audited lines that is not in DESIGN.md, or a default Tailwind colour class used where a token exists; that class is not converted, so its row says the line goes around the tokens, not that the colour is wrong. A note is something to look at that the audit does not call wrong. An unknown is something the audit could not judge. - There is no score. The verdict is "pass" only when at least one rule was live and nothing was found, and "review" otherwise. - Colours match exactly or not at all. The audit never picks a nearest colour. - Not audited: font size, font weight, line height, letter spacing, widths and heights, breakpoints, motion, copy, images and SVG. - brandmd's check compares a new extraction with the committed DESIGN.md: colours role by role, plus fonts, the spacing and radii lists and a few component fields. This audit reads literal values in source files. They answer different questions and need not agree. - No source file was edited.

    layout.tsx

    ZIP · project files

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    It checks a diff, a few files or a folder against your DESIGN.md and writes one file, BRAND_AUDIT.md. A finding is a colour, font, radius or shadow that is not in the DESIGN.md, a default Tailwind colour class such as bg-blue-600 used where a token exists, or a native button, link or input in a file with no focus style. Each row has the file and line, the value and what to use instead, or "no token" when nothing fits.

    It edits no source file and gives no score, only pass or review. The file lists what it could not judge, such as rendered contrast and hover states, and holds a six-line receipt for the PR description.

    It works with any Google-spec DESIGN.md, hand-written ones included. One way to get the file is brandmd, which extracts it from a live site.

    Free cloud run: paste a DESIGN.md and one file or diff. Nothing is written. The chat shows the whole BRAND_AUDIT.md, a line on what project access would add, the three questions (call to action colour, real font names, spacing scale) with defaults, and a line saying no source file was edited. In a paste run followed by hand, with the DESIGN.md captured from tailwindcss.com and the same app/page.tsx as the sample below, the chat showed 4 findings, 3 notes and 4 unknowns.

    Use when you want to know if a PR is on brand, find off-palette colours, or see what in a folder is not using your tokens.

    Known limitations

    • It reads source text and renders nothing, so there is no rendered contrast.
    • Hover, focus, active and disabled colours and shadows that are not in DESIGN.md are notes, not findings, because brandmd records no state values.
    • Not audited: font size, font weight, line height, letter spacing, widths and heights, breakpoints, motion, copy, images and SVG.
    • Not audited, and counted in the file: the theme file (read only for token names), anything under components/ui, generated and vendored folders, tests and snapshots, and SVG.
    • A default Tailwind colour class is flagged by name, not by value. The row lists up to three candidates and you pick one.
    • The focus check is low confidence, because a global stylesheet or the browser default may still draw a ring. A component imported from another file, such as Button, is not judged.
    • A DESIGN.md font name that looks internal, such as sohne-var, makes every font finding low confidence until you give the real family name.
    • Spacing off the scale is a note, never a finding.
    • Values built at run time, such as a class from a template string or a font variable, go under unknowns.
    • At most 50 finding rows are shown. The rest are summarised by rule, and the receipt counts cover every row.
    • On a big folder it reads files in path order, lists every file it did not reach, and never calls an unread file clean.
    • In the pasted run there is no project. Tailwind v4 defaults are assumed, palette-class rows are low confidence and name DESIGN.md keys such as on-background instead of classes, theme classes such as text-muted-foreground stay unresolved, and the focus check on a diff needs the whole file. In the paste dry run, rounded-xl was read at the v4 default of 12px; the sample project's theme makes it 14px.
    • If the DESIGN.md capture landed on a block page, a login page or another site, every rule drops to a note and the verdict is "review (capture not usable)".
    • It does not apply fixes. The "Use instead" column is the list to apply by hand.

    - It reads source text and renders nothing, so there is no rendered contrast. - Hover, focus, active and disabled colours and shadows that are not in DESIGN.md are notes, not findings, because brandmd records no state values. - Not audited: font size, font weight, line height, letter spacing, widths and heights, breakpoints, motion, copy, images and SVG. - Not audited, and counted in the file: the theme file (read only for token names), anything under components/ui, generated and vendored folders, tests and snapshots, and SVG. - A default Tailwind colour class is flagged by name, not by value. The row lists up to three candidates and you pick one. - The focus check is low confidence, because a global stylesheet or the browser default may still draw a ring. A component imported from another file, such as Button, is not judged. - A DESIGN.md font name that looks internal, such as sohne-var, makes every font finding low confidence until you give the real family name. - Spacing off the scale is a note, never a finding. - Values built at run time, such as a class from a template string or a font variable, go under unknowns. - At most 50 finding rows are shown. The rest are summarised by rule, and the receipt counts cover every row. - On a big folder it reads files in path order, lists every file it did not reach, and never calls an unread file clean. - In the pasted run there is no project. Tailwind v4 defaults are assumed, palette-class rows are low confidence and name DESIGN.md keys such as on-background instead of classes, theme classes such as text-muted-foreground stay unresolved, and the focus check on a diff needs the whole file. In the paste dry run, rounded-xl was read at the v4 default of 12px; the sample project's theme makes it 14px. - If the DESIGN.md capture landed on a block page, a login page or another site, every rule drops to a note and the verdict is "review (capture not usable)". - It does not apply fixes. The "Use instead" column is the list to apply by hand.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 15 days ago

    • Free with an Agensi account

    Permissions

    Read Files
    Write Files

    Reads DESIGN.md, DESIGN.review.md, package.json, components.json, the theme CSS and the UI files you point it at. Writes one file, BRAND_AUDIT.md. Never edits a source file, never runs a command, never uses the network.

    Listed15 days ago

    What's inside

    Frequently Asked Questions

    No. It writes one file, BRAND_AUDIT.md, and edits nothing else, not even DESIGN.md. Its content sits between a start and an end marker, so a second run replaces only that block. If the file already exists without the markers, it asks before replacing it. With no file edit tool, it prints the file instead.

    No. Any file in the Google design.md format works, and so does a hand-written one. The audit builds its list of allowed values from whatever the file holds: frontmatter colours, font families and radii, plus the values the prose gives. A rule with nothing to compare against is switched off and named in the file. Missing values are listed, never made up. If no DESIGN.md is found, it says how to get one, or that you can paste one, and stops without writing anything.

    A score would claim a precision the audit does not have. You get a verdict, pass or review, plus counts by rule. Pass needs zero findings and at least one rule that could give findings. Notes alone do not block it.

    Colours match exactly or not at all. Hex is lowercased and expanded, and rgb() is converted by lookup, but there is no nearest colour. A near-black like #111111 against a black #000000 is a finding that says "no token: decide, or add it to DESIGN.md". oklch(), hsl() and color-mix() values are listed as unknowns, not converted.

    The theme file (globals.css or your @theme block) is read for token names, so a row can suggest classes like border-border. The theme is not audited, and its colour values are not judged against DESIGN.md. An exact hex match only helps name the token to use, which is how a theme with its own colour names gets suggestions too. Its radius, shadow and font values are checked only where an audited file uses the class, which is how rounded-xl at 14px became a finding in the sample. Dark values in DESIGN.md count only when the dark section really describes a dark page, and a match against them is a note marked unverified. Without usable dark data, an off-palette colour in a dark: class is a note, not a finding.

    Yes. What the skill writes for you (BRAND_AUDIT.md) is yours to use anywhere, client and commercial work included. The skill files themselves are for your own use under the marketplace's terms; please don't repost or resell them.

    New in Frontend & Web Apps