Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Design System Generator

    1

    Describe a product, its audience and its personality, and get a complete design system in one document: brand, colour with checked contrast, type, components, CSS tokens, style guide

    $5

    /mo

    Subscription · cancel anytime

    Secure checkout via Stripe

    • Always the latest version
    • Delivered live to your agent via MCP
    • Cancel anytime, access ends at period end
    Security scanned
    Design System Generator

    Design System Generator

    Example session with this skill installed

    Create a design system for Ledgerly, a personal budgeting app for people in their twenties who find money stressful. Calm and friendly, but it has to feel trustworthy. Web and mobile.

    • Read your context and instructions
    • Compiled the design system generator

    Here is the Ledgerly design system as one document, covering web and mobile. I calculated every contrast ratio from the hex values using the WCAG 2.1 relative-luminance formula, so the numbers are real, not estimates. Every value in the component rules has a matching token in Phase 4.


    Design System: Personal Budgeting App (Ledgerly, web and mobile)

    Phase 1: Brand Identity

    Brand name directions

    #DirectionRationale
    1Ledgerly (recommended, used throughout this document)"Ledger" signals accuracy and a record you can trust, and the "-ly" ending softens it into something friendly rather than accountant-like.
    2SteadilyIt names how the user should feel (progress without lurches), which suits an audience that is stressed by money more than confused by it.
    3Breathing RoomIt names the outcome, a gap between income and spending, in emotional words, though it reads more like a slogan than a product name.

    Directions 2 and 3 have not been checked for trademarks or domains. They are here in case Ledgerly hits a conflict.

    Personality keywords

    Calm · Friendly · Trustworthy · Clear · Patient · Grounded · Honest

    Emotional tone at first glance

    Relief. In the first second a user should see a quiet, warm screen with one big number they understand and nothing flashing at them. It should feel like opening a well-kept notebook, not a bank alert. Trust comes from precision (aligned figures, exact cents, clear dates). Calm comes from space, soft color and words that never scold.

    Competitive positioning

    Most budgeting apps either look like a bank statement (dense, grey, full of red) or act like a game (streaks, confetti, guilt when you break them). Ledgerly sits between the two. It has the precision of a statement and the warmth of a friend who is good with money: it shows the real numbers, explains them in plain words, and never shames you for them.


    Phase 2: Visual Language

    Color palette

    Contrast is measured against WCAG 2.1 AA:

    4.5:1 for body text, and

    3:1 for large text (≥ 24px regular or ≥ 18.66px bold) and for UI components and focus indicators (1.4.11). "Paper" is the app background #FAF8F4 and "Surface" is the card background #FFFFFF.

    Light theme (default)
    NameHexUsage ruleContrast note
    Ink#1E2A32All body text, headings and amounts13.82:1 on Paper, 14.66:1 on Surface. Passes 4.5:1 body
    Ink Muted#56636CSecondary text, helper text, timestamps, inactive nav labels5.83:1 on Paper, 6.18:1 on Surface, 5.29:1 on Primary Soft. Passes 4.5:1 body
    Paper#FAF8F4App background on web and mobile. Warm off-white, never pure white behind content1.06:1 against Surface, so cards need the Divider border or a shadow to separate (decorative, no text requirement)
    Surface#FFFFFFCards, inputs, modals, nav barsBackground color. Ink on it 14.66:1
    Surface Sunken#F1EEE8Neutral badges, table stripes, skeleton loadersInk 12.66:1, Ink Muted 5.34:1, Primary 6.37:1 on it. All pass 4.5:1
    Primary (Deep Teal)#1F5F5BPrimary buttons, links, active nav, the wordmark6.96:1 on Paper, 7.38:1 on Surface. White text on it 7.38:1. Passes 4.5:1 body both ways
    Primary Hover#174A47Hover state of primary actions (web)White text 9.97:1. Passes 4.5:1
    Primary Pressed#123B38Pressed/active state (web and mobile)White text 12.29:1. Passes 4.5:1
    Primary Soft#E3F0EESelected nav item pill, selected chips, info panelsPrimary text on it 6.31:1, Ink 12.54:1. Passes 4.5:1
    Sage#A9C7BCIllustration fills, progress-track fills, charts only1.71:1 on Paper, so never text and never the only boundary of a control. Ink on Sage 8.09:1 if a label must sit on it
    Border#7D8A84Input borders, checkbox and radio outlines3.39:1 on Paper, 3.60:1 on Surface. Passes 3:1 UI component (1.4.11)
    Divider#DDE2DFCard outlines, list separators. Decorative only1.31:1 on Surface. Fails 3:1, so it is only allowed where it is not the sole indicator of a control
    On Track (Success)#2E7550"On track" badges, positive progress, money in5.24:1 on Paper, 5.56:1 on Surface. Passes 4.5:1 body
    On Track Soft#E4F1E9Background for On Track badges and bannersOn Track text on it 4.78:1. Passes 4.5:1
    Heads-up (Caution)#8A5A00"Heads-up" badges: bill due soon, budget at 80%5.59:1 on Paper, 5.93:1 on Surface. Passes 4.5:1 body
    Heads-up Soft#FBEFD5Background for Heads-up badges and bannersHeads-up text on it 5.20:1. Passes 4.5:1
    Over (Clay)#A84530Overspend, failed sync, destructive actions. A warm clay instead of alarm red, on purpose5.56:1 on Paper, 5.90:1 on Surface, white on it 5.90:1. Passes 4.5:1 body
    Over Soft#F8E6E1Background for Over badges and bannersClay text on it 4.89:1. Passes 4.5:1
    Info#2F5D8ANeutral tips and "did you know" notes6.48:1 on Paper. Passes 4.5:1 body
    Focus#2D6FB8Focus ring on every interactive element4.86:1 on Paper, 5.15:1 on Surface. Passes 3:1 focus indicator. It is only 1.43:1 against Primary, so the ring always sits outside a 2px offset gap, never directly on a teal fill
    Disabled Background#E6E9E7Disabled buttons and inputsBackground for disabled text
    Disabled Text#6B767CText on disabled controls3.81:1 on Disabled Background. Disabled controls are exempt under 1.4.3, but kept legible on purpose
    Dark theme (mobile follows the OS setting, web follows prefers-color-scheme)
    NameHexUsage ruleContrast note
    Dark Paper#12191DDark app backgroundBackground
    Dark Surface#1B2429Cards, sheets, nav barsBackground
    Dark Ink#EDEFEABody text15.34:1 on Dark Paper, 13.63:1 on Dark Surface. Passes 4.5:1
    Dark Ink Muted#A3AEB4Secondary text7.84:1 on Dark Paper, 6.97:1 on Dark Surface. Passes 4.5:1
    Dark Primary#6FC2B6Buttons, links, active nav8.51:1 on Dark Paper, 7.56:1 on Dark Surface. Dark Paper text on a Dark Primary button 8.51:1. Passes 4.5:1
    Dark Primary Soft#24343ASelected nav pillDark Primary on it 6.19:1, Dark Ink 11.14:1. Passes 4.5:1
    Dark Border#6E7B81Input borders3.62:1 on Dark Surface, 4.07:1 on Dark Paper. Passes 3:1 UI
    Dark On Track#7CCB9CPositive states8.17:1 on Dark Surface. Passes 4.5:1
    Dark Heads-up#E8B860Caution states8.61:1 on Dark Surface. Passes 4.5:1
    Dark Over#E9917COverspend and destructive6.62:1 on Dark Surface. Passes 4.5:1
    Dark Focus#7FB3EEFocus ring8.11:1 on Dark Paper, 7.20:1 on Dark Surface. Passes 3:1

    The light-theme On Track #2E7550 drops to 2.84:1 on Dark Surface, so it must never be reused in dark mode. Always switch to the dark token.

    Typography system

    Display and headings: Plus Jakarta Sans (SemiBold 600, Bold 700). Its rounded geometric shapes read friendly without feeling childish.

    Body, UI and every number: Inter (Regular 400, Medium 500, SemiBold 600), with font-variant-numeric: tabular-nums on all amounts so the digits line up in columns. Aligned figures are the quietest trust signal in a finance app.

    • Fallback stack: system-ui, -apple-system, "Segoe UI", Roboto, sans-serif.

    Amount formatting: use the true minus sign (U+2212, "−$42.00"), never red parentheses. Always show cents for balances and drop them only on whole-dollar chart axes.

    LevelDesktop (≥ 1024px)Mobile (< 600px)Line heightWeight / familyUse
    Display (balance)40px / 2.5rem34px / 2.125rem1.1700 Jakarta, tabularThe one big number per screen ("Left to spend")
    H132px / 2rem28px / 1.75rem1.2700 JakartaScreen titles
    H224px / 1.5rem22px / 1.375rem1.25600 JakartaSection titles ("This month")
    H320px / 1.25rem18px / 1.125rem1.3600 JakartaCard titles
    H418px / 1.125rem16px / 1rem1.35600 InterModal titles, list group headers
    Body16px / 1rem16px / 1rem1.5400 InterAll reading text. Never below 16px on mobile, so iOS does not zoom inputs
    Body Small14px / 0.875rem14px / 0.875rem1.45400/500 InterHelper text, labels, metadata
    Caption13px / 0.8125rem13px / 0.8125rem1.4600 InterBadges, chart labels. Never used for full sentences

    Tablets (600–1023px) use the mobile scale for Display through H2 and the desktop scale for H3 and below.

    Spacing and layout

    • Base unit: 4px. Scale: 4, 8, 12, 16, 20, 24, 32, 40, 48, 64 (--space-1 to --space-16).

    Rhythm: 16px between related elements, 24px between groups, 32–48px between page sections. Generous whitespace is part of the "calm" promise. When in doubt, add space instead of a divider.

    Touch targets: at least 48 × 48px on mobile and 40 × 40px on web pointer layouts (above the 44px of WCAG 2.1 SC 2.5.5).

    • Reading width: text blocks max out at 640px, so explanations stay readable on wide monitors.
    BreakpointRangeColumnsGutterOuter marginNavigation
    Mobile0–599px416px16px (+ safe-area insets)Bottom tab bar
    Tablet600–1023px824px32pxBottom tab bar (portrait), side rail (landscape)
    Desktop1024–1439px1224px40pxLeft sidebar, 248px
    Wide≥ 1440px1232pxauto, content max 1200pxLeft sidebar, 248px

    Iconography and illustration direction

    Icons are rounded line icons on a 24px grid with a 1.75px stroke, rounded caps and joins, and 2px corner radii. They draw in --color-ink or --color-ink-muted, and in --color-primary only when active. Illustrations are flat, soft shapes in Sage, Primary Soft and Surface Sunken, showing everyday objects (a jar, a plant, a calendar page) instead of money symbols.

    Do

    1. Pair every status icon with a text label, for example a small clock icon next to "Due in 3 days".
    2. Use illustrations on empty states and first-run screens, where they lower the stakes ("No bills yet, add one when you're ready").
    3. Keep icon metaphors literal and consistent: one icon per category (groceries, rent, transport) used everywhere that category appears.

    Don't

    1. Don't use dollar-sign piles, flames, sirens or exclamation-in-triangle icons for overspending. They turn a number into an emergency.
    2. Don't use filled and line icons together in one view. Filled is reserved for the active tab in the navigation bar.
    3. Don't use illustrations on screens where the user is reading their numbers (transactions, budget detail). The numbers are the content there.

    Phase 3: Component Rules

    Primary button

    Visual description: a solid Deep Teal (--color-primary) fill with white Inter SemiBold 16px text (--button-font-size, --button-font-weight). It is 48px tall (--button-height-md), or 40px compact for web toolbars (--button-height-sm), with 24px horizontal padding (--button-padding-x) and a 12px radius (--radius-md): rounded enough to feel friendly, not pill-shaped enough to feel playful. Hover goes to --color-primary-hover and pressed to --color-primary-pressed. There is no bounce or scale effect, only a 150ms color fade (--duration-fast), because a calm product doesn't jump. On mobile it spans the full width of the content area at the bottom of forms.

    When to use: the single most important action on a screen: "Save budget", "Add transaction", "Continue".

    When not to use: more than once per view. Not for destructive actions, which use the clay variant (--color-over fill, white text) and always open a confirmation modal. Not for navigation between sections, which uses the navigation bar or a text link.

    Accessibility note: WCAG 2.1 SC 2.4.7 Focus Visible. Keyboard focus shows a 2px --color-focus ring (--focus-ring-width) outside a 2px gap (--focus-ring-offset), because the ring is only 1.43:1 against the teal fill but 5.15:1 against the Surface behind the gap. Use :focus-visible so mouse clicks don't flash a ring.

    Input field

    Visual description: a white (--color-surface) field, 48px tall (--input-height), with a 1px --color-border outline (--input-border-width), an 8px radius (--radius-sm), 12px horizontal padding (--input-padding-x) and 16px body text. The label sits above the field in 14px Inter SemiBold (--font-size-body-sm) in Ink, never only as a placeholder. Helper text sits below in 14px Ink Muted. On focus the border becomes 2px --color-primary (--input-border-width-focus) plus the focus ring. Errors turn the border --color-over and show a sentence below the field that explains how to fix it ("Enter an amount, like 25 or 25.50"). Money inputs right-align their digits with tabular numerals and show the currency symbol as a fixed prefix.

    When to use: free entry of amounts, payee names, notes and budget names.

    When not to use: picking from a known set (categories, accounts), which uses a select or chip group, and yes/no choices, which use a toggle. Don't use an input for dates on mobile, where the native date picker is calmer and less error-prone.

    Accessibility note: WCAG 2.1 SC 3.3.1 Error Identification and 1.3.1 Info and Relationships. Every input has a programmatic <label>, and the error text is linked with aria-describedby and announced with aria-live="polite", so screen-reader users hear what went wrong without the color change.

    Card

    Visual description: a white Surface panel on the Paper background with a 16px radius (--radius-lg), a 1px --color-divider outline and a soft ink-tinted shadow (--shadow-sm) that lifts it just enough to separate it from Paper (1.06:1 alone would not). Padding is 20px on mobile (--card-padding-mobile) and 24px from tablet up (--card-padding-desktop). A budget card holds an H3 title, one Display or H2 amount, a progress bar (Sage track, Primary or status-color fill) and one line of plain-language context ("$120 left · 9 days to go").

    When to use: a summary of one thing the user can act on or open: one budget, one account, one upcoming bill.

    When not to use: wrapping whole page sections, or nesting cards inside cards. Long transaction lists use plain rows with Divider separators. Each card in a list would add visual noise the calm tone can't afford.

    Accessibility note: WCAG 2.1 SC 1.3.1 Info and Relationships. The card title is a real heading (<h3>). If the whole card is clickable, the link is on the title and its hit area is stretched with a pseudo-element, so a screen reader reads one link name instead of the whole card's contents.

    Navigation bar

    Visual description: on mobile, a bottom tab bar on Surface, 64px tall (--nav-height-mobile) plus the device safe-area inset, with four items: Home, Budgets, Activity, You. Each item is a 24px icon above a 13px Caption label in Ink Muted. The active item gets a filled icon, Primary text and a Primary Soft pill (--color-primary-soft, --radius-pill) behind the icon. On desktop it becomes a 248px left sidebar (--nav-width-desktop) with the wordmark at the top and the same four items as rows, each 48px tall. The bar sits at --z-nav, with a hairline --color-divider edge and no heavy shadow.

    When to use: the four top-level destinations, on every primary screen.

    When not to use: more than five destinations (move the extras into "You"), secondary actions such as "Export", or inside flows like onboarding or adding a transaction, where the bar hides so the user can focus.

    Accessibility note: WCAG 2.1 SC 4.1.2 Name, Role, Value. Wrap the bar in <nav aria-label="Main"> and mark the current item with aria-current="page", so the active state isn't carried by color and the Primary Soft pill alone. Each target is at least 48 × 48px (SC 2.5.5).

    Badge / tag

    Visual description: a compact pill, 24px tall (--badge-height), with 10px horizontal padding (--badge-padding-x), a full radius (--radius-pill) and a 13px SemiBold Caption label (--font-size-caption). There are four tones, each a soft background with its own strong text: On Track (--color-success on --color-success-soft), Heads-up (--color-caution on --color-caution-soft), Over (--color-over on --color-over-soft) and Neutral (--color-ink-muted on --color-surface-sunken). Labels use kind words: "On track", "Heads-up", "$18 over", never "DANGER" or "FAILED".

    When to use: a short status on a budget, bill or transaction ("Recurring", "Pending", "On track").

    When not to use: anything the user can tap (that's a chip or button), a full sentence, or more than two badges on one row. Don't badge every transaction "Over". Show the status once, at budget level.

    Accessibility note: WCAG 2.1 SC 1.4.1 Use of Color. Every badge states its status in words and, for the three status tones, carries a leading icon (check, clock, arrow-up), so color-blind users never have to tell the On Track green from the Over clay.

    Modal

    Visual description: on web, a centred Surface dialog up to 480px wide (--modal-max-width) with a 24px radius (--radius-xl), 24px padding (--modal-padding), --shadow-lg, and an ink-tinted scrim behind it (--color-scrim, 48% Ink). On mobile (< 600px) it becomes a bottom sheet with 24px top corners that slides up over 250ms (--duration-base), or simply fades when the user has reduced motion turned on. It has an H4 title, one or two sentences of body, a Primary action on the right (on desktop) or on top (on mobile), and a text "Cancel". The scrim sits at --z-scrim and the dialog at --z-modal.

    When to use: confirming something hard to undo (deleting a budget, disconnecting a bank), or a short focused task under five fields ("Edit amount").

    When not to use: welcome messages, tips, upsells or celebrations. Interrupting a stressed user for something non-essential breaks the calm promise. Use an inline banner instead. Never stack two modals.

    Accessibility note: WCAG 2.1 SC 2.4.3 Focus Order and 2.1.2 No Keyboard Trap. On open, focus moves to the dialog title. Tab cycles inside the dialog, Escape closes it, and focus goes back to the element that opened it. Use role="dialog", aria-modal="true" and aria-labelledby pointing at the title.


    Phase 4: Token Export

    :root {
      /* ---------- Color: neutrals ---------- */
      --color-ink: #1E2A32;              /* body text, headings, amounts - 13.82:1 on paper */
      --color-ink-muted: #56636C;        /* secondary/helper text, inactive nav labels - 5.83:1 on paper */
      --color-paper: #FAF8F4;            /* app background, web and mobile */
      --color-surface: #FFFFFF;          /* cards, inputs, modals, nav bars */
      --color-surface-sunken: #F1EEE8;   /* neutral badge background, table stripes, skeletons */
      --color-border: #7D8A84;           /* input and control outlines - 3.39:1 on paper (1.4.11) */
      --color-divider: #DDE2DF;          /* decorative card outlines and list separators only - 1.31:1 */
    
      /* ---------- Color: brand ---------- */
      --color-primary: #1F5F5B;          /* primary buttons, links, active nav, wordmark - white on it 7.38:1 */
      --color-primary-hover: #174A47;    /* primary hover (web) - white on it 9.97:1 */
      --color-primary-pressed: #123B38;  /* primary pressed state - white on it 12.29:1 */
      --color-primary-soft: #E3F0EE;     /* selected nav pill, selected chips - primary text on it 6.31:1 */
      --color-on-primary: #FFFFFF;       /* text and icons on primary fills */
      --color-sage: #A9C7BC;             /* illustration and progress-track fills only, never text */
    
      /* ---------- Color: status ---------- */
      --color-success: #2E7550;          /* "On track" text/icon, money in - 5.24:1 on paper */
      --color-success-soft: #E4F1E9;     /* On Track badge background - success on it 4.78:1 */
      --color-caution: #8A5A00;          /* "Heads-up" text/icon - 5.59:1 on paper */
      --color-caution-soft: #FBEFD5;     /* Heads-up badge background - caution on it 5.20:1 */
      --color-over: #A84530;             /* overspend, destructive fill and error border - 5.56:1 on paper */
      --color-over-soft: #F8E6E1;        /* Over badge background - over on it 4.89:1 */
      --color-info: #2F5D8A;             /* neutral tips - 6.48:1 on paper */
    
      /* ---------- Color: interaction ---------- */
      --color-focus: #2D6FB8;            /* focus ring - 4.86:1 on paper; always drawn outside the offset gap */
      --color-disabled-bg: #E6E9E7;      /* disabled button and input fill */
      --color-disabled-text: #6B767C;    /* disabled label text - 3.81:1 on disabled-bg */
      --color-scrim: rgba(30, 42, 50, 0.48); /* modal backdrop, ink at 48% */
    
      /* ---------- Typography: families ---------- */
      --font-family-display: "Plus Jakarta Sans", system-ui, -apple-system, "Segoe UI", Roboto, sans-serif; /* display and H1-H3 */
      --font-family-body: "Inter", system-ui, -apple-system, "Segoe UI", Roboto, sans-serif;               /* body, UI, H4, all numbers */
      --font-numeric: tabular-nums;      /* apply via font-variant-numeric on every amount */
    
      /* ---------- Typography: sizes (desktop; mobile overrides below) ---------- */
      --font-size-display: 2.5rem;       /* 40px - the one balance number per screen */
      --font-size-h1: 2rem;              /* 32px - screen titles */
      --font-size-h2: 1.5rem;            /* 24px - section titles */
      --font-size-h3: 1.25rem;           /* 20px - card titles */
      --font-size-h4: 1.125rem;          /* 18px - modal titles, list group headers */
      --font-size-body: 1rem;            /* 16px - all reading text and input text */
      --font-size-body-sm: 0.875rem;     /* 14px - labels, helper text, metadata */
      --font-size-caption: 0.8125rem;    /* 13px - badges, nav labels, chart labels; never sentences */
    
      /* ---------- Typography: weights and line heights ---------- */
      --font-weight-regular: 400;        /* body text */
      --font-weight-medium: 500;         /* emphasised metadata */
      --font-weight-semibold: 600;       /* labels, H2-H4, badges */
      --font-weight-bold: 700;           /* display and H1 */
      --line-height-tight: 1.1;          /* display amounts */
      --line-height-heading: 1.25;       /* H1-H4 */
      --line-height-body: 1.5;           /* body and helper text */
    
      /* ---------- Spacing (4px base) ---------- */
      --space-1: 0.25rem;                /* 4px - icon-to-label gap */
      --space-2: 0.5rem;                 /* 8px - tight inline spacing */
      --space-3: 0.75rem;                /* 12px - input horizontal padding */
      --space-4: 1rem;                   /* 16px - related elements, mobile outer margin */
      --space-5: 1.25rem;                /* 20px - mobile card padding */
      --space-6: 1.5rem;                 /* 24px - between groups, desktop card and modal padding */
      --space-8: 2rem;                   /* 32px - between sections, tablet margin */
      --space-10: 2.5rem;                /* 40px - desktop outer margin */
      --space-12: 3rem;                  /* 48px - large section breaks */
      --space-16: 4rem;                  /* 64px - page top/bottom on desktop */
      --content-max-width: 75rem;        /* 1200px - wide-screen content cap */
      --text-max-width: 40rem;           /* 640px - max width of reading text */
      /* Breakpoints (custom properties cannot be used in @media; mirror these in your build):
         mobile 0-599px, tablet 600-1023px, desktop 1024-1439px, wide >= 1440px */
    
      /* ---------- Border radius ---------- */
      --radius-sm: 0.5rem;               /* 8px - inputs */
      --radius-md: 0.75rem;              /* 12px - buttons */
      --radius-lg: 1rem;                 /* 16px - cards */
      --radius-xl: 1.5rem;               /* 24px - modals and mobile bottom-sheet top corners */
      --radius-pill: 999px;              /* badges, active nav pill */
    
      /* ---------- Box shadow (ink-tinted, never pure black) ---------- */
      --shadow-sm: 0 1px 2px rgba(30, 42, 50, 0.06), 0 1px 3px rgba(30, 42, 50, 0.08);   /* cards resting on paper */
      --shadow-md: 0 4px 12px rgba(30, 42, 50, 0.10);                                      /* dropdowns, popovers, toasts */
      --shadow-lg: 0 12px 32px rgba(30, 42, 50, 0.16);                                     /* modals and bottom sheets */
    
      /* ---------- Z-index layers ---------- */
      --z-base: 0;                       /* page content */
      --z-sticky: 50;                    /* sticky section headers */
      --z-nav: 100;                      /* bottom tab bar and sidebar */
      --z-dropdown: 200;                 /* selects, popovers */
      --z-scrim: 300;                    /* modal backdrop */
      --z-modal: 400;                    /* modal and bottom sheet */
      --z-toast: 500;                    /* toasts, always above modals */
    
      /* ---------- Motion ---------- */
      --duration-fast: 150ms;            /* button and nav color fades */
      --duration-base: 250ms;            /* bottom-sheet slide, modal fade */
      --easing-standard: cubic-bezier(0.2, 0, 0, 1); /* gentle ease-out, no overshoot */
    
      /* ---------- Focus ---------- */
      --focus-ring-width: 2px;           /* focus ring thickness */
      --focus-ring-offset: 2px;          /* gap between control and ring, keeps ring off teal fills */
    
      /* ---------- Component: primary button ---------- */
      --button-height-md: 3rem;          /* 48px - default and mobile button height */
      --button-height-sm: 2.5rem;        /* 40px - compact web toolbar button */
      --button-padding-x: var(--space-6);        /* 24px horizontal padding */
      --button-radius: var(--radius-md);         /* 12px corners */
      --button-font-size: var(--font-size-body); /* 16px label */
      --button-font-weight: var(--font-weight-semibold); /* 600 label */
    
      /* ---------- Component: input field ---------- */
      --input-height: 3rem;              /* 48px field height */
      --input-padding-x: var(--space-3); /* 12px horizontal padding */
      --input-radius: var(--radius-sm);  /* 8px corners */
      --input-border-width: 1px;         /* resting border, --color-border */
      --input-border-width-focus: 2px;   /* focus border, --color-primary */
    
      /* ---------- Component: card ---------- */
      --card-padding-mobile: var(--space-5);  /* 20px below 600px */
      --card-padding-desktop: var(--space-6); /* 24px from 600px up */
      --card-radius: var(--radius-lg);        /* 16px corners */
      --card-shadow: var(--shadow-sm);        /* lift off paper */
    
      /* ---------- Component: navigation bar ---------- */
      --nav-height-mobile: 4rem;         /* 64px bottom tab bar, plus env(safe-area-inset-bottom) */
      --nav-width-desktop: 15.5rem;      /* 248px left sidebar from 1024px */
      --nav-item-height: 3rem;           /* 48px sidebar row / minimum tab target */
    
      /* ---------- Component: badge ---------- */
      --badge-height: 1.5rem;            /* 24px pill height */
      --badge-padding-x: 0.625rem;       /* 10px horizontal padding */
      --badge-radius: var(--radius-pill);/* full pill */
    
      /* ---------- Component: modal ---------- */
      --modal-max-width: 30rem;          /* 480px centred dialog on web */
      --modal-padding: var(--space-6);   /* 24px inner padding */
      --modal-radius: var(--radius-xl);  /* 24px corners / sheet top corners */
    }
    
    /* ---------- Mobile type overrides (< 600px) ---------- */
    @media (max-width: 599px) {
      :root {
        --font-size-display: 2.125rem;   /* 34px balance number on phones */
        --font-size-h1: 1.75rem;         /* 28px screen title */
        --font-size-h2: 1.375rem;        /* 22px section title */
        --font-size-h3: 1.125rem;        /* 18px card title */
        --font-size-h4: 1rem;            /* 16px modal title */
      }
    }
    
    /* ---------- Dark theme ---------- */
    @media (prefers-color-scheme: dark) {
      :root {
        --color-paper: #12191D;          /* dark app background */
        --color-surface: #1B2429;        /* dark cards, sheets, nav */
        --color-surface-sunken: #24343A; /* dark neutral badge background */
        --color-ink: #EDEFEA;            /* dark body text - 15.34:1 on dark paper */
        --color-ink-muted: #A3AEB4;      /* dark secondary text - 6.97:1 on dark surface */
        --color-primary: #6FC2B6;        /* dark primary - 7.56:1 on dark surface */
        --color-on-primary: #12191D;     /* text on dark primary buttons - 8.51:1 */
        --color-primary-soft: #24343A;   /* dark selected nav pill - primary on it 6.19:1 */
        --color-border: #6E7B81;         /* dark input border - 3.62:1 on dark surface */
        --color-success: #7CCB9C;        /* dark on-track - 8.17:1 on dark surface */
        --color-caution: #E8B860;        /* dark heads-up - 8.61:1 on dark surface */
        --color-over: #E9917C;           /* dark over - 6.62:1 on dark surface */
        --color-focus: #7FB3EE;          /* dark focus ring - 7.20:1 on dark surface */
      }
    }
    
    /* ---------- Reduced motion ---------- */
    @media (prefers-reduced-motion: reduce) {
      :root {
        --duration-fast: 0ms;            /* no color fades */
        --duration-base: 0ms;            /* sheets appear without sliding */
      }
    }
    

    The dark block above changes only the tokens that differ. The soft status backgrounds (--color-success-soft and its siblings) need dark equivalents before dark mode ships. I've left them out rather than guess untested values. Derive them at roughly 15% of the dark status color over #1B2429, then check the text against them at 4.5:1.


    Phase 5: Style Guide

    Brand essence

    Ledgerly makes your money something you can look at without flinching.

    Swatch board

    Picture a warm, mostly empty sheet. About 70% of the board is Paper #FAF8F4, with white Surface cards floating on it. Ink #1E2A32 carries all the words and numbers. Deep Teal #1F5F5B is the one confident color, used sparingly for whatever the user should do next, so it should cover no more than about 10% of any screen. Sage #A9C7BC and Primary Soft #E3F0EE are the quiet supporting tints in progress tracks and illustrations. The three status pairs (On Track green, Heads-up amber, Over clay) sit off to the side as small chips. They show up only when there is something to say, and always as a soft background with darker text, never as a big block of color.

    Typography specimen

    Display, Plus Jakarta Sans Bold 40px, tabular: $1,284.50

    H1, Plus Jakarta Sans Bold 32px: Here's your month so far

    H2, Plus Jakarta Sans SemiBold 24px: Budgets

    H3, Plus Jakarta Sans SemiBold 20px: Groceries

    H4, Inter SemiBold 18px: Delete this budget?

    Body, Inter Regular 16px: You've spent $212 of your $300 grocery budget, with 9 days to go. That's about $9.80 a day if you want to finish on track.

    Body Small, Inter Regular 14px: Last synced 4 minutes ago from Checking ·· 4417

    Caption, Inter SemiBold 13px: ON TRACK · RECURRING · $18 OVER

    Voice and tone

    The voice is a friend who is good with money: plain, warm, specific, and never surprised by your numbers.

    Do

    1. Name the number, then the next step. "You're $18 over on eating out. Want to move $18 from Fun money?"
    2. Use "you" and short sentences. "Your rent is due Friday. You've got it covered."
    3. Notice the small wins. "That's three weeks in a row under your grocery budget."

    Don't

    1. Don't scold or moralise. Not "You overspent again!" Say "Eating out went $18 over this month."

    Don't use banking jargon. Not "Insufficient available balance for scheduled debit." Say "There might not be enough in Checking for Friday's rent."
    3.

    Don't manufacture urgency. Not "ACT NOW: budget limit exceeded!!" Say "Heads-up: you've used 90% of Transport with a week to go."

    Logo usage (wordmark)

    • The wordmark is

    "ledgerly" in lowercase Plus Jakarta Sans Bold with letter-spacing −0.01em, in --color-primary on Paper or Surface, or in --color-ink where teal is already used heavily nearby.

    • Reversed, it is white on --color-primary (7.38:1), or --color-primary from the dark theme on Dark Paper.
    • Clear space around it equals the height of the lowercase "l" on all sides.

    Minimum size is 20px cap height on screen, 24px tall in the mobile app header and 28px tall at the top of the desktop sidebar.

    Never stretch, outline, add shadows or gradients, rotate it, set it in another typeface, or color it in a status color (--color-over, --color-caution, --color-success). The brand must never look like it is warning you.

    The rule that must never be broken

    Never show a worrying number on its own. Every overspend, low balance, missed bill or failed sync appears with a plain-language label in text (not color alone) and one concrete next step the user can take.

    Rationale: Ledgerly's users already find money stressful. A bare "−$42.00" in clay, with no words and no way forward, confirms their fear and teaches them to stop opening the app. The trust Ledgerly earns comes from never leaving someone alone with a bad number. It also covers WCAG 1.4.1 for free, because the status is always stated in words.


    Verification Checklist

    • Every text pairing in the product uses a combination from the Phase 2 palette table at 4.5:1 or above. In particular, --color-sage (1.71:1) and --color-divider (1.31:1) never carry text.
    • The focus ring is always drawn with --focus-ring-offset: 2px outside the control, because --color-focus on --color-primary is only 1.43:1.
    • Dark mode never reuses the light --color-success #2E7550 (2.84:1 on Dark Surface). The prefers-color-scheme: dark block switches it to #7CCB9C.
    • The dark-theme soft status backgrounds have been derived and checked at 4.5:1 before dark mode ships (they are deliberately missing from Phase 4).
    • Every amount uses --font-family-body with font-variant-numeric: var(--font-numeric), and negative amounts use the true minus sign (U+2212), never red parentheses.
    • Every interactive target meets 48 × 48px on mobile: --button-height-md, --input-height and --nav-item-height are all 3rem.
    • Each screen has at most one primary button in --color-primary. Destructive actions use the --color-over variant and always open a modal at --z-modal.
    • Every badge carries a text label, and every On Track, Heads-up and Over badge also has a leading icon, so status never depends on color (SC 1.4.1).
    • Modals turn into bottom sheets below 600px with --modal-radius top corners, return focus to the element that opened them, and are never used for tips, upsells or celebrations.
    • Every overspend, low-balance, missed-bill and sync-error state in the product has been checked against the never-break rule: a plain-language label plus one next step, never a bare clay number.
    $5/mo

    Subscription · always the latest version

    • Secure checkout via Stripe
    • Cancel anytime
    • Delivered live via MCP

    About this skill

    Builds a production-ready design system for any product as a single Markdown document, from three things you tell it: what the product is, who it's for, and how it should feel. It's a working spec, not a mood board: every colour has a usage rule and a contrast ratio, every component rule points at a token, and the tokens come out as CSS you can paste.

    What it does

    The document runs in five phases. Brand identity gives three name directions with a rationale each, personality keywords and voice. Visual language covers a colour palette with hex values, usage rules and WCAG contrast notes, a type scale, spacing, radii and iconography. Component rules cover six core components (button, input, card, navigation, badge, modal) with their states. A CSS custom-properties block exports every token, and a style guide condenses it all. It ends with a ten-item checklist tied to the decisions it made, so the system can be checked, not just admired.

    Try it first

    Say "create a design system for a budgeting app for people in their twenties who find money stressful, calm but trustworthy, web and mobile". Check that the contrast ratios are stated as numbers and that the component rules use the token names.

    What it needs

    Nothing to install: no scripts, no network access and no API keys. Any agent that can write a long Markdown document.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Branding & Design.

    It writes the system as a document; it doesn't draw mockups, export Figma files or build a component library in code. Name directions aren't checked against trademarks or domains, and it says so. Contrast ratios are computed from the hex values for text on the stated backgrounds, so a colour used somewhere else needs its own check. Illustration and photography direction is described, not produced.

    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 buying a skill.

    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 to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 27 days ago

    Permissions

    Write Files
    Listed27 days ago

    What's inside

    Frequently Asked Questions

    Describe a product, its audience and its personality, and get a complete design system in one document: brand, colour with checked contrast, type, components, CSS tokens, style guide

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use Design System Generator on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Branding & Design