design-consultation

Originally fromgarrytan/gstack
Installation
SKILL.md

Design Consultation

Propose a coherent design system for the user's product and show it in a realistic preview. Begin with existing DESIGN.md, theme/tokens, components, brand assets and rendered pages. Match that foundation unless the user requests a new direction.

Direction

Resolve consequential unknowns about audience, task, constraints and desired character. Reuse supplied answers; do not require a questionnaire for a clear brief. Offer an opinionated direction with reasons and let the user adjust it.

Research current alternatives when requested or needed to support a recommendation. Use actual rendered pages for claims about competitors' visuals. Label interpretations and avoid treating brand reputation as observed evidence.

Choose typography, color, layout/density, spacing, borders, imagery/icons and motion that reinforce the product. Avoid defaulting every project to brutalism or generic feature cards; intentional grids, familiar fonts and unusual combinations may fit the brief. Treat aesthetic preferences as preferences, not universal defects or proof of AI authorship.

Specify font roles/weights/fallbacks, actual supported loading sources, semantic color pairs, relevant component tokens and responsive states. Preserve supported themes; propose additions separately. Explain coherence tradeoffs without reopening settled choices.

Accessibility and verification

Normal text needs 4.5:1 contrast at WCAG AA. Large text is at least 18pt (24px) regular or 14pt (about 18.67px) bold and needs 3:1. Label any stricter house targets separately from the standard. Verify relevant exceptions and non-text requirements against W3C when necessary.

Include keyboard/focus behavior, non-color cues and reduced motion where applicable. Do not equate a recommended 44px touch target with every WCAG AA requirement; check the applicable criterion and spacing exceptions.

Installs
50
Repository
borkweb/skills
GitHub Stars
8
First Seen
May 19, 2026