⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v0.3.42

algorithmic-color-palette

dembrandt@dembrandt⭐ 192 stars· last commit 14d ago· 0 open issues

Derive a full UI palette from one or two brand colours — state variants, brand-tinted greys, semantic colours. Use when building or expanding a colour system.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐⭐ 192 on GitHubGitHub ↗

Popular

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

dembrandt-skills

skills.sh installs CI License: MIT

Enterprise UX for every agent

Enterprise UX secrets, now built into your AI agent.

Your agent writes the component in seconds. It does not know the modal should be a drawer, or that the grey it picked fails contrast. These skills carry that judgment: what to do, and what breaks otherwise. Works with Claude Code, Cursor, Codex, GitHub Copilot and any agent that reads the Open Agent Skills format.

Quick start

npx skills add dembrandt/dembrandt-skills --all

Skills load only when a prompt needs them, so --all costs nothing. --global installs for every project. 43 of the 45 skills work on the install alone. Two read live sites and need the engine. Installs are copies: run npx skills update to pick up later changes.

Then try it. Open a UI file and ask your agent:

Review this interface for usability issues.

On Claude Code, the plugin is the shorter route: it carries the skills and registers the dembrandt MCP server in one go. It does not fetch the browser: run npx dembrandt install-browser once before the first extraction. Everyone else uses npx skills above. The npx line goes in a terminal; the /plugin lines are typed inside Claude Code.

/plugin marketplace add dembrandt/dembrandt-skills
/plugin install dembrandt@dembrandt

Usage

Ask in your own words and the matching skill loads. Ask broadly, "review this screen", and the dembrandt skill runs the whole pipeline.

AskWhat loads
I have one brand colour, #133174. Build me a full UI palette.algorithmic-color-palette
My font sizes feel random. Set up a proper type scale.modular-scale-typography
Review this interface for usability issues.nielsen-usability-heuristics
Our buttons, inputs and badges look like three different products.component-family-consistency
Design a multi-step onboarding flow for a B2B SaaS tool.user-flows-and-guided-paths
Does this pass WCAG 2.2 AA?wcag-accessibility
Extract the design system from stripe.com.extract-design, needs the engine

Skills

Brand & Visual Identity

SkillWhat it covers
brand-visual-languageShape language, icon style, typography tone
color-mode-and-themeLight vs dark vs combined, when to offer a theme selector
marketing-vs-product-systemWhat a marketing site and the product may differ on, and what is drift
algorithmic-color-paletteDerive states and brand-tinted greys from brand colours

Design Tokens & Scales

SkillWhat it covers
modular-scale-typographyRatio-based type scales, minimum sizes, context-aware usage
elevation-and-depthShadow scale, border-radius, card and modal patterns
surface-separationOne separation strategy per surface; opacity as state, not tint
button-statesSix states: rest, hover, active, focus, disabled, loading
component-family-consistencyButtons, inputs, pills: shared radius, colour, height
sizing-unitspx vs rem vs relative: which values move when the user enlarges text

Layout & Structure

SkillWhat it covers
layout-paradigms-and-consistencyChoose the layout paradigm that fits the content; reuse the page skeleton across screens
gestalt-ui-organisationGroup related controls: proximity, similarity, common region
visual-emphasis-and-hierarchyOne CTA per view, colour and size as emphasis
information-architectureNaming, mental models, data UI, confirm dialogs
ui-context-and-scopeHierarchy, breadcrumbs, colour regions, scope communication
responsive-paradigmsMobile/tablet/desktop: nav, sections, sticky behaviour
ui-densityMatch density to platform and user type
sticky-and-fixed-elementsHeaders, bottom toolbars, z-index tokens
scroll-areasAvoid inner scroll, one axis only, user-controlled

Components & Interaction

SkillWhat it covers
real-world-metaphorsCards, carousels, drawers: when to use and how
form-designHelper text, placeholder, validation, submit state
tab-navigationTab types, overflow handling, roving tabindex, ARIA tablist, URL state
modal-and-overlay-patternsOverlay hierarchy, focus trap, dismiss rules, destructive confirms
data-display-and-selectionGrid/list/table, large hit areas, mass actions
repeated-component-alignmentRepeated components as slot models: equal size, pinned anchors, clamp + recover text
operational-expert-tool-uiDense, workflow-driven UIs for trained daily B2B users
coordinated-data-viewsKeep a table and a visual view (map, diagram, chart) in sync
domain-expert-configurationExpose solver/algorithm settings in domain language
app-shellTop bar, sidebar rail, app launcher, tenant and environment cue, status bar: one shell across an estate
global-toolbar-controlsCurrency, language, region and unit selectors: frequent but not primary
notifications-and-recoveryToasts, banners, retry, undo: always a path forward
status-colors-and-errorsMinimal semantic colours, error recovery, prevention

UX Principles

SkillWhat it covers
nielsen-usability-heuristics10 usability principles with review checklists
wcag-accessibilityWCAG 2.2 AA / EN 301 549: contrast, keyboard, ARIA
user-flows-and-guided-pathsWizards, purchase flows, onboarding sequences
authentic-product-representationReal content and real output over staged mockups and marketing chrome
micro-interactionsAnimated icons, toggles, reveals, celebrations
loading-states-and-perceived-performanceSpinners, skeleton screens, and staggered entry animations
motion-and-storytellingDisney principles and cinematic language in UI

Technical Foundation

SkillWhat it covers
semantic-html-and-seoHTML5, alt texts, Open Graph, progressive enhancement
performance-and-web-vitalsLighthouse audit, LCP, CLS, INP, images, fonts, JS loading

Pipeline & Orchestration

SkillWhat it covers
extract-designExtract real design tokens from any live website via Dembrandt CLI or MCP (requires dembrandt ≥ 0.39.0)
clone-websiteRebuild a live page 1:1 from capture and computed styles, into Figma, Penpot or code
generate-ui-from-brandURL or DESIGN.md to tokens to decisions to UI spec (requires dembrandt ≥ 0.23.1)
dembrandtFull 6-stage UX orchestrator: brand, tokens, layout, components, polish, a11y gate

The engine

Dembrandt turns any live website into design tokens in seconds, then enforces them in CI. It catches brand drift on every pull request, before it ships. Free and open source, at dembrandt.com.

Two skills, extract-design and generate-ui-from-brand, read tokens off a live site and need it. Add it to your agent's MCP config:

{
  "mcpServers": {
    "dembrandt": {
      "command": "npx",
      "args": ["-y", "dembrandt", "mcp"]
    }
  }
}

Needs Node.js 18 or newer. Dembrandt drives its own Chromium, which is not bundled: run npx dembrandt install-browser once in a terminal before the first extraction.

Contributing

Changes to skills/** go through a pull request, however small. A push to main is live to every install. Run npm test before opening one; CI validates frontmatter, cross-link

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/algorithmic-color-palette/SKILL.md7.9 KBupstream ↗
    ---
    name: algorithmic-color-palette
    description: Derive a full UI palette from one or two brand colours — state variants, brand-tinted greys, semantic colours. Use when building or expanding a colour system.
    metadata:
      priority: 8
      pathPatterns:
        - "**/*.css"
        - "**/*.scss"
        - "**/tokens/**"
        - "**/theme/**"
        - "tailwind.config.*"
        - "design-system/**"
      promptSignals:
        phrases:
          - "colour palette"
          - "color palette"
          - "brand colours"
          - "derive colours"
          - "colour tokens"
          - "hover colour"
          - "shade"
          - "tint"
          - "colour system"
      retrieval:
        aliases:
          - colour system
          - algorithmic colours
          - brand colour palette
          - derive shades
          - colour tokens
        intents:
          - generate a colour palette from brand colours
          - derive hover and active colours
          - create grey palette from brand
          - build a full colour system
          - extend a limited brand palette
        examples:
          - generate a full colour palette from this brand blue
          - what colour should the hover state be
          - create a grey palette that fits this brand
          - derive semantic colours from the brand primary
    ---
    
    # Algorithmic Colour Palette
    
    A brand palette of 2–3 colours is not enough for a UI. You need shades for states (hover, active, disabled), neutrals for backgrounds and borders, and semantic colours for status. Deriving these algorithmically from the brand colours produces a palette that feels coherent — everything is visually related to the brand rather than pulled from a generic grey or a stock colour library.
    
    > **Don't guess the seed colours — extract them (dembrandt engine, optional).** If the brand already exists on the web, pull its *real* palette off the live site instead of eyeballing a hex: `get_color_palette` (or the `extract-design` skill) returns the actual computed brand and neutral colours from the DOM, which you then expand with the methods below. See [`extract-design`](../extract-design/SKILL.md) for setup.
    
    ## Deriving Interactive State Colours
    
    From each brand colour, generate at minimum three variants: base, darker (hover/active), lighter (tint/background).
    
    ### Method: HSL adjustment
    
    ```
    base:    hsl(H, S%, L%)
    hover:   hsl(H, S%, L% - 8%)     ← darken by reducing lightness
    active:  hsl(H, S%, L% - 14%)    ← darken further
    tint:    hsl(H, S%, L% + 40%)    ← lighten significantly for backgrounds
    subtle:  hsl(H, S% * 0.3, L% + 45%)  ← heavily desaturated, near-white
    ```
    
    ### Example: brand primary `#133174` (hsl 224, 70%, 27%)
    
    ```css
    --color-primary-subtle:  hsl(224, 21%, 94%);  /* background tint */
    --color-primary-tint:    hsl(224, 70%, 67%);  /* light variant */
    --color-primary:         hsl(224, 70%, 27%);  /* base */
    --color-primary-hover:   hsl(224, 70%, 19%);  /* hover: -8% lightness */
    --color-primary-active:  hsl(224, 70%, 13%);  /* active: -14% lightness */
    ```
    
    ### Example: success green derived from a teal brand colour
    
    If the brand has a green or teal, shift it toward a clearer success green:
    
    ```css
    --color-success-subtle:  hsl(142, 20%, 94%);
    --color-success:         hsl(142, 60%, 35%);
    --color-success-hover:   hsl(142, 60%, 27%);
    ```
    
    ## Deriving Brand-Tinted Greys
    
    Generic greys (`#666`, `#999`, `#eee`) feel disconnected from the brand. Desaturating the brand hue produces greys that are subtly tinted — warm, cool, or neutral depending on the brand — and feel like they belong to the same palette.
    
    ### Optical Comfort: Avoiding Pure Black on White
    Pure black `#000000` on pure white `#FFFFFF` causes halation and eye strain. Use a near-black such as `#222222` (`grey-900`) for text and an off-white such as `#EEEEEE` (`grey-50`) for backgrounds; the softened pair still passes WCAG AA/AAA and reads as less harsh.
    
    ### Publish Roles, Not Only Swatches
    Named chips with hex values are not a system until each colour has a role: surface, surface tint, text, link, accent, decoration. Name the humble roles too, the off-white behind cards, stripes and hairlines. A role left unnamed is filled by a framework default, which is how an off-brand neutral ends up painting most of the pixels. Two teams inventing the same missing tint with different values means a role is missing, not a colour.
    
    ### Method: desaturate + adjust lightness
    
    ```
    brand hue H
    grey-900: hsl(H, 12%, 10%)   ← near-black, text
    grey-700: hsl(H, 10%, 30%)   ← dark text, icons
    grey-500: hsl(H,  8%, 50%)   ← secondary text, placeholders
    grey-300: hsl(H,  6%, 70%)   ← disabled text, subtle labels
    grey-200: hsl(H,  5%, 82%)   ← borders, dividers
    grey-100: hsl(H,  4%, 92%)   ← input backgrounds, table stripes
    grey-50:  hsl(H,  3%, 96%)   ← page background, subtle fills
    ```
    
    ### Example: brand primary `#133174` (H = 224, blue-tinted)
    
    ```css
    --color-grey-900: hsl(224, 12%, 10%);  /* #16171f — slightly blue-black */
    --color-grey-500: hsl(224,  8%, 50%);  /* #7b7e8a — cool grey */
    --color-grey-200: hsl(224,  5%, 82%);  /* #cfd0d5 — cool light border */
    --color-grey-50:  hsl(224,  3%, 96%);  /* #f4f4f6 — near-white with a hint of blue */
    ```
    
    Compare to generic `#f5f5f5` (no hue) — the brand-tinted version is subtly different but feels intentional.
    
    ## Semantic Colour Derivation
    
    Status colours (error, warning, success, info) should feel harmonious with the brand. To achieve cohesion, align their **Saturation** and **Lightness** to create a consistent "visual weight" across the status set.
    
    ### Method: Aligned visual weight
    
    1. **Pick the Hues:** Use standard semantic hues (0 for Error, 38 for Warning, 142 for Success).
    2. **Align S & L:** Use the saturation and lightness of your Brand Primary as a starting point.
    3. **Adjust for Perceived Brightness:** Hues like Yellow/Orange (Warning) feel brighter than Blue/Red. Reduce the lightness of Warning by 5–10% compared to Success or Error to ensure they feel equally "heavy" on the page.
    
    | Semantic | Hue (H) | Saturation (S) | Lightness (L) |
    |---|---|---|---|
    | **Error** | 0–10 | Match Primary | Match Primary |
    | **Warning** | 35–45 | Match Primary | Primary L - 10% |
    | **Success** | 140–160 | Match Primary | Match Primary |
    | **Info** | 210–230 | Match Primary | Match Primary |
    
    **The "Vibrancy" Rule:** If the brand is muted (low saturation), the semantic colours should also be slightly muted. If the brand is neon/vibrant, the semantics should follow suit. Cohesion comes from shared intensity.
    
    ## Functional and Interactive Colours
    
    Standard UI elements require dedicated functional tokens beyond basic brand and semantic colours.
    
    ### Focus States
    Focus indicators are critical for accessibility. Use a high-visibility colour that works on all backgrounds.
    - **Default:** Brand Primary (if contrast is high enough).
    - **Fallback:** A dedicated high-contrast blue `hsl(215, 95%, 50%)`.
    - **Token:** `--color-focus`.
    
    ### Selection and Highlights
    Text selection and list item highlights should be subtle and non-distracting.
    - **Method:** Use the primary hue with very high lightness (90%+) and moderate saturation.
    - **Token:** `--color-selection`.
    
    ### Overlays and Modals
    Backdrops for modals or drawers need a neutral, semi-transparent colour.
    - **Method:** Use your `grey-900` hue with an alpha channel.
    - **Token:** `--color-overlay: hsla(H, 12%, 10%, 0.5);`
    
    ### Skeleton and Loading
    Loading states should be neutral and recessive.
    - **Method:** Use `grey-200` as the base and `grey-100` as the shimmer highlight.
    - **Token:** `--color-skeleton`.
    
    ### Disabled States
    Disabled elements must communicate unreachability.
    - **Method:** Use `grey-500` for text and `grey-200` for backgrounds/borders.
    - **Rule:** Avoid using brand tints for disabled backgrounds to prevent "pseudo-active" confusion.
    
    ### Brand-Tinted Shadows
    Premium UIs avoid pure black shadows. Use a very dark, desaturated brand hue.
    - **Method:** `hsla(H, 15%, 5%, alpha)` where H is the brand hue.
    - **Token:** `--color-shadow-base`.
    
    ### Links
    - **Base:** Brand Primary or a dedicated high-visibility 
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/dembrandt-dembrandt-skills-skills-algorithmic-color-palette.md

// REPO STATS

192 stars
0 open issues
Last commit: 14d ago