Articulate — Design Vocabulary

Say precisely what you mean. Vague design feedback ("make it pop", "feels off", "cleaner") wastes iterations. A shared, precise vocabulary lets you name the exact property, state, or pattern at issue — so reviews, critiques, and handoffs land the first time.

Use this skill to choose the right word: when describing a UI issue, writing a critique or review, naming a token, or reaching for a term you half-remember. Reach for the precise term below instead of an approximation; if a needed term isn't here, consult the full reference at index.how/to/articulate.

When to use

• Writing or sharpening critique / review / audit copy — name the property, not the vibe.
• Design handoff / rationale — communicate decisions in terms a designer and engineer share.
• Describing a UI/interaction issue precisely (e.g. "the disabled state relies on opacity, not a muted token").
• Reaching for a term and unsure of the exact word (kerning vs tracking, voice vs tone, WCAG vs APCA).

Pairs with frontend:impeccable (design execution), frontend:impeccable (argument: critique, heuristic review), and frontend:web-design-guidelines (standards) — articulate supplies the words those skills' findings should be written in.

The 12 domains (quick reference)

Representative terms per domain; see the source for the complete ~188-entry set.