accessible-content
Use when writing or structuring any user-facing content — interface copy, labels, error messages, help text, headings, alt text,…
Use when building layouts, choosing colours, setting typography, establishing visual hierarchy, designing responsive behaviour, or making any visual design decision — ensures every visual choice serves both aesthetics and accessibility
$ npx -y skills add Owl-Listener/designpowers --skill ui-composition --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/ui-compositionContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when building layouts, choosing colours, setting typography, establishing visual hierarchy, designing responsive behaviour, or making any visual design decision — ensures every visual choice serves both aesthetics and accessibility
name: ui-composition description: Use when building layouts, choosing colours, setting typography, establishing visual hierarchy, designing responsive behaviour, or making any visual design decision — ensures every visual choice serves both aesthetics and accessibility
Visual design is where intent becomes tangible. Every colour, every spacing decision, every typographic choice either includes or excludes people. This skill ensures visual decisions are principled, systematic, and inclusive.
Before making visual decisions, confirm you have:
**Grid system:**
**Visual hierarchy:**
**Spacing system:**
**Palette construction:**
**Colour independence:**
**Dark mode / high contrast:**
**Type scale:**
**Readability:**
**Font selection:**
Design for these breakpoints (adjust to project needs):
At every breakpoint:
For each visual decision, document:
| Element | Requirement | |---------|------------| | Text contrast | 4.5:1 (AA) or 7:1 (AAA) | | Large text contrast | 3:1 minimum | | UI component contrast | 3:1 against adjacent colours | | Touch target | 44x44px minimum | | Focus indicator | Visible, 3:1 contrast against adjacent | | Text resize | Content usable at 200% zoom | | Colour alone | Never the sole indicator of state or meaning |
An agent design team you control. 10 agents that run an inclusive design process while you direct. The system notices how you design and reflects it back. Designpowers is an open, model-agnostic design workflow that gives you a team of 10 design agents.
Use when writing or structuring any user-facing content — interface copy, labels, error messages, help text, headings, alt text,…
Use when designing for user preferences — motion sensitivity, contrast needs, colour schemes, text sizing, information density,…
Use when evaluating mental load, wayfinding, focus management, memory demands, or decision complexity in any interface — ensures…
Use when a design direction is uncertain, when the team could go multiple ways, or when the user wants to see competing…
Use when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to…
You MUST use this before any creative or design work — building features, creating components, designing interfaces, modifying…