global-toolbar-controls

Name: global-toolbar-controls
Author: dembrandt

262installs5forks

How to install global-toolbar-controls?

dembrandt/dembrandt-skills/global-toolbar-controls

$npx -y skills add dembrandt/dembrandt-skills --skill global-toolbar-controls

Installs into the current project.

Summary

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 gl

Files · 1

View on GitHub

SKILL.md

1	# Global Toolbar Controls
2
3	## What Belongs Here
4
5	Global 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.
6
7	Typical global toolbar controls:
8	- Currency selector (e-commerce, financial tools)
9	- Language / locale switcher
10	- Region or market selector
11	- Unit system (metric / imperial)
12	- Theme toggle (light / dark)
13	- Accessibility preferences (font size, contrast)
14
15	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).
16
17	## Where to Place Them
18
19	### Header utility strip
20	A secondary row above or within the main header, right-aligned. Common on e-commerce and international sites.
21
22	```
23	[Logo] [EN \| EUR \| 🌍] [Account] [Cart]
24	────────────────────────────────────────────────────────────
25	[Main navigation]
26	```
27
28	### Header right — compact
29	Inline with the main header, far right, using small typography and minimal visual weight.
30
31	```
32	[Logo] [Nav items ...] [EUR ▾] [EN ▾] [Account ▾]
33	```
34
35	### Footer
36	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.
37
38	### Dedicated settings area
39	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.
40
41	## Typography and Visual Treatment
42
43	Global toolbar controls are secondary UI — they should not draw the eye away from primary content.
44
45	- Font size: 13–14px — deliberately smaller than body text (14px maximum per the type scale)
46	- Colour: muted — use a secondary text colour (`--color-text-secondary`), not the primary text colour
47	- No bold — regular weight only
48	- Compact spacing — tighter padding than primary navigation items
49	- Separator — a `\|` or thin vertical rule between adjacent controls (language \| currency) keeps them grouped without using full button chrome
50
51	```css
52	.toolbar-control {
53	font-size: var(--text-sm); /* 13–14px */
54	color: var(--color-text-secondary);
55	font-weight: 400;
56	padding: 4px 8px;
57	}
58	```
59
60	## Interaction Pattern
61
62	Global controls typically use a compact dropdown — clicking the label opens a small popover or select with the available options.
63
64	- Show the current value as the trigger label: `EUR ▾`, `EN ▾`
65	- Use a flag icon + language code for locale, or currency symbol + code for currency
66	- Keep the option list short — if it exceeds ~20 items, add a search input inside the dropdown
67	- On selection, apply immediately and confirm with a brief status update (toast or inline update) if the change has a visible effect
68
69	## Review Checklist
70
71	- [ ] Are global controls placed consistently in one location across all pages?
72	- [ ] Is the typography smaller and more muted than primary navigation?
73	- [ ] Does the control show the current value as its label?
74	- [ ] Is the dropdown or popover compact and keyboard-navigable?
75	- [ ] Are global controls separated from user account settings?
76	- [ ] On mobile, are global controls accessible without being prominent? (Often moved to a menu or footer on small screens)

People who liked this also viewed

6 picks

Type

global-toolbar-controls

262installs5forks

View on GitHub

How to install global-toolbar-controls?

dembrandt/dembrandt-skills/global-toolbar-controls

$npx -y skills add dembrandt/dembrandt-skills --skill global-toolbar-controls

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Global Toolbar Controls
2
3	## What Belongs Here
4
5	Global 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.
6
7	Typical global toolbar controls:
8	- Currency selector (e-commerce, financial tools)
9	- Language / locale switcher
10	- Region or market selector
11	- Unit system (metric / imperial)
12	- Theme toggle (light / dark)
13	- Accessibility preferences (font size, contrast)
14
15	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).
16
17	## Where to Place Them
18
19	### Header utility strip
20	A secondary row above or within the main header, right-aligned. Common on e-commerce and international sites.
21
22	```
23	[Logo] [EN \| EUR \| 🌍] [Account] [Cart]
24	────────────────────────────────────────────────────────────
25	[Main navigation]
26	```
27
28	### Header right — compact
29	Inline with the main header, far right, using small typography and minimal visual weight.
30
31	```
32	[Logo] [Nav items ...] [EUR ▾] [EN ▾] [Account ▾]
33	```
34
35	### Footer
36	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.
37
38	### Dedicated settings area
39	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.
40
41	## Typography and Visual Treatment
42
43	Global toolbar controls are secondary UI — they should not draw the eye away from primary content.
44
45	- Font size: 13–14px — deliberately smaller than body text (14px maximum per the type scale)
46	- Colour: muted — use a secondary text colour (`--color-text-secondary`), not the primary text colour
47	- No bold — regular weight only
48	- Compact spacing — tighter padding than primary navigation items
49	- Separator — a `\|` or thin vertical rule between adjacent controls (language \| currency) keeps them grouped without using full button chrome
50
51	```css
52	.toolbar-control {
53	font-size: var(--text-sm); /* 13–14px */
54	color: var(--color-text-secondary);
55	font-weight: 400;
56	padding: 4px 8px;
57	}
58	```
59
60	## Interaction Pattern
61
62	Global controls typically use a compact dropdown — clicking the label opens a small popover or select with the available options.
63
64	- Show the current value as the trigger label: `EUR ▾`, `EN ▾`
65	- Use a flag icon + language code for locale, or currency symbol + code for currency
66	- Keep the option list short — if it exceeds ~20 items, add a search input inside the dropdown
67	- On selection, apply immediately and confirm with a brief status update (toast or inline update) if the change has a visible effect
68
69	## Review Checklist
70
71	- [ ] Are global controls placed consistently in one location across all pages?
72	- [ ] Is the typography smaller and more muted than primary navigation?
73	- [ ] Does the control show the current value as its label?
74	- [ ] Is the dropdown or popover compact and keyboard-navigable?
75	- [ ] Are global controls separated from user account settings?
76	- [ ] On mobile, are global controls accessible without being prominent? (Often moved to a menu or footer on small screens)

People who liked this also viewed

6 picks

Type