algorithmic-color-pale…
Derive a full UI colour palette algorithmically from one or two brand colours. Darker and lighter variants for interactive states, desaturated greys from the…
Quick global settings — currency, language, region, units — belong in a persistent, low-profile location such as a header toolbar or footer. These controls are frequent but not primary, so they use small typography and stay out of the main content hierarchy. Use when designing
$ npx -y skills add dembrandt/dembrandt-skills --skill global-toolbar-controls --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/global-toolbar-controlsContext preview
The summary Claude sees to decide when to auto-load this skill.
Quick global settings — currency, language, region, units — belong in a persistent, low-profile location such as a header toolbar or footer. These controls are frequent but not primary, so they use small typography and stay out of the main content hierarchy. Use when designing
name: global-toolbar-controls
description: Quick global settings — currency, language, region, units — belong in a persistent, low-profile location such as a header toolbar or footer. These controls are frequent but not primary, so they use small typography and stay out of the main content hierarchy. Use when designing global selectors, locale switchers, or user preference controls that apply across the whole product.
metadata:
priority: 5
pathPatterns:
- "components/**"
- "src/components/**"
- "**/*.tsx"
- "**/*.jsx"
- "design-system/**"
- "ui/**"
promptSignals:
phrases:
- "currency"
- "language"
- "locale"
- "region"
- "global settings"
- "toolbar"
- "header controls"
- "units"
retrieval:
aliases:
- global settings
- locale switcher
- currency selector
- language switcher
- toolbar controls
- header utility bar
intents:
- add currency switcher
- design language selector
- place global settings in layout
- add locale controls to header
examples:
- where should the currency selector go
- add a language switcher to the header
- design global settings controls for the toolbarGlobal controls affect the entire product experience but are not the user's primary task. They are reached occasionally — once per session or less — and should not compete visually with primary navigation or content.
Typical global toolbar controls:
These are distinct from user account settings (which live in a profile menu) and from contextual settings (which live adjacent to the feature they affect).
A secondary row above or within the main header, right-aligned. Common on e-commerce and international sites.
[Logo] [EN | EUR | 🌍] [Account] [Cart] ──────────────────────────────────────────────────────────── [Main navigation]
Inline with the main header, far right, using small typography and minimal visual weight.
[Logo] [Nav items ...] [EUR ▾] [EN ▾] [Account ▾]
For controls the user sets once and rarely revisits. Language and region selectors frequently appear in footers on large international sites (Airbnb, Apple). Appropriate when the control is truly infrequent.
For more complex preference sets, a Settings page or panel is cleaner than cramming everything into the toolbar. The toolbar should link to it, not contain it.
Global toolbar controls are secondary UI — they should not draw the eye away from primary content.
.toolbar-control {
font-size: var(--text-sm); /* 13–14px */
color: var(--color-text-secondary);
font-weight: 400;
padding: 4px 8px;
}Global controls typically use a **compact dropdown** — clicking the label opens a small popover or select with the available options.
UX and design-system skills for AI agents. Install once, and your agent knows how to design. --all installs every skill at once. They load only when a prompt needs them, so there is no runtime cost to having them all. Want to pick by hand?
Repo: dembrandt/dembrandt-skills
Derive a full UI colour palette algorithmically from one or two brand colours. Darker and lighter variants for interactive states, desaturated greys from the…
The persistent shell around an application — the top bar, the app launcher, the tenant and environment cue, and in heavy tools a status bar. In an estate of…
Product visuals — hero shots, demos, screenshots, landing-page panels — must reproduce the real product, not a stylised poster of it. Design with real content…
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and…
Every interactive element needs a complete set of visual states — rest, hover, active/pressed, focus, disabled, and loading. States should be derived…
Rebuild an existing web page 1:1 from measurement instead of by eye — into Figma, Penpot, or code. Captures the rendered page, the raw source and the computed…