JasonColapietro/suede-creator-skills / skills/suede-design
suede-design
VerifiedUse when asked "review this UI diff" or "audit this flow"; to design interface hierarchy, tokens, color, type, accessibility or a design system; run a whole-flow review; restyle a dashboard; or verify a visual build. NOT FOR: component state workbenches or live variants (use suede-component-lab), source-backed effect explanations (use suede-interface-explain), sales copy (use suede-copy), funnel architecture (use suede-site-alchemy), or general code/security review (use suede-code).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 5.3 KB |
| LICENSE.jakubkrehel-skills-MIT.txt | markdown | 1.0 KB |
| SKILL.md | skill md | 20.8 KB |
| agents/openai.yaml | config | 580 B |
| references/build-delivery.md | markdown | 4.1 KB |
| references/design-laws.md | markdown | 3.8 KB |
| references/interface-accessibility.md | markdown | 3.4 KB |
| references/interface-behavior.md | markdown | 3.4 KB |
| references/interface-color.md | markdown | 2.8 KB |
| references/interface-layout.md | markdown | 3.3 KB |
| references/interface-review.md | markdown | 8.4 KB |
| references/interface-typography.md | markdown | 3.1 KB |
| references/interface-writing.md | markdown | 3.4 KB |
| references/restyle-playbook.md | markdown | 6.0 KB |
| references/scoped-bans.md | markdown | 5.7 KB |
| references/surface-lenses.md | markdown | 3.0 KB |
| references/ui-component-sources.md | markdown | 5.1 KB |
| references/usage-contract.md | markdown | 2.6 KB |
references/interface-color.md
View on GitHub# Color: roles, contrast and consistency
Use the project's color notation, semantic tokens and theme mechanism. A
consistent hex palette is not worse than OKLCH, and black/white is not a defect.
Do not apply Suede marketing colors to another UI or infer original brand
tokens from approximate screenshot samples.
## Trace the semantic role
Map each inspected value from primitive → semantic token → component → state.
Check themes and variants. A separator token reused for body text can silently
break when borders change; report the role mismatch and confirmed consumers.
Do not create unused ramps or migrate the whole palette to correct one pair.
State meaning must remain understandable without color alone. Validate actual
text/icon/shape cues for error, selection, success, disabled and permission
states. A hue shared by brand and destructive actions is not automatically a
violation; test whether the action's treatment communicates its consequence.
## Measure the pair that appears
Start with declared values for source analysis, then inspect computed and
composited foreground/background for a rendered claim. Account for opacity,
ancestor backgrounds, images, gradients, blending, hover/focus states and theme.
A token pair calculation is not proof of a translucent label over an image.
Report the pair, state, method, measured ratio and applicable threshold. Apply
WCAG criteria and exceptions from `interface-accessibility.md`; do not apply a
body-text threshold to every decorative or disabled element. Never invent a
contrast measurement or treat a sampled JPEG value as an original design token.
For gradients/images, inspect the portions behind the actual text and necessary
controls. If the available evidence cannot establish the pair across relevant
content, state what remains unverified instead of reporting a single average.
## Correct the shared cause when authorized
Prefer the existing semantic action or text pair. If a shared semantic value
changes, inspect confirmed consumers in both revisions. An unchanged component
can carry a regression caused by the token diff. Correct the semantic pair,
not one leaf's literal color, unless the component's role is itself wrong.
Check light/dark, hover/focus, disabled and any relevant status variants after a
fix. A one-state contrast pass does not establish the full component. Preserve
brand hue and established emphasis where an accessible value within the system
solves the issue; flag a conflicting reference and use the smallest approved
accessible solution.
For a new palette within a design brief, choose only roles the product uses.
Measure generated values and supported color-gamut behavior; notation or a
theoretical ramp does not guarantee usable pairs. Use existing project tooling,
not a newly fetched color library solely to perform the review.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |