web-design-guidelines-design
Web Design Guidelines Design
Overview
Use this skill to establish a strong design direction before implementation and prevent generic output. It is for moments when the interface needs a deliberate point of view, not a default UI blend.
Workflow
- Identify the UI surface, the intended audience, the constraints, and the host product conventions that must stay recognizable.
- Check the project for a local design system or style guide. Look for files such as
docs/**/design-system.md,DESIGN_SYSTEM.md,docs/**/style-guide.md, theme files (theme.ts,theme/index.ts), or any file referenced in the project'sCLAUDE.mdas the design system. If found, read it first — its explicit decisions take precedence over universal plugin guidance on specifics; the plugin guidance fills gaps. - Read the relevant files under
references/design/and only the core constraints that materially shape the direction. - Present two or three viable directions with trade-offs so the options are explicit, not implicit.
- Recommend one direction, commit to it, and explain why it best fits the product goals and constraints.
- Name one memorable differentiator that should still be visible after implementation.
Reference Map
All paths below are relative to this file's directory. Resolve them as
{dir_of_SKILL.md}/{path}before reading.
references/design/direction.mdreferences/design/typography-color.mdreferences/design/motion-composition.mdreferences/design/anti-slop.mdreferences/core/layout.mdreferences/core/content-accessibility.md
Guardrails
- Preserve established product systems unless the task explicitly asks for a stronger redesign.
- Distinctive minimalism is acceptable; generic output is not.
- Keep the chosen direction compatible with accessibility, responsiveness, and interactions.
- Do not trade away keyboard support, contrast, or narrow-width behavior for style.
- When a project-local design system is present, its explicit decisions take precedence over universal plugin guidance on specifics; the plugin guidance fills gaps.
More from mrclrchtr/skills
agent-orchestrator
Orchestrate complex work via a phase-gated multi-agent loop (audit → design → implement → review → validate → deliver). Use when you need to split work into subsystems, run independent audits, reconcile findings into a confirmed issue list, delegate fixes in clusters, enforce PASS/FAIL review gates, and drive an end-to-end validated delivery. Do not use for small, single-file tasks.
38git-commit
Creates a commit: detects conventions, stages intentionally, writes a clear subject, add a concise body when useful, and commits.
22agent-orchestrator-standalone
Orchestrate complex work via a phase-gated multi-agent loop (audit → design → implement → review → validate → deliver). Use when you need to split work into subsystems, run independent audits, reconcile findings into a confirmed issue list, delegate fixes in clusters, enforce PASS/FAIL review gates, and drive an end-to-end validated delivery. Do not use for small, single-file tasks.
16commit
Creates a commit with repo-matching style and intentional staging.
5web-fetch-to-markdown
Fetches and normalizes http(s) web pages into clean Markdown for LLM ingestion. Use when a task includes a URL, needs to fetch docs or asks to convert web docs/articles/pages into Markdown for summarizing, quoting, diffing, or saving.
5web-design-guidelines-apply
Use when building or modifying frontend UI and implementation choices should follow shared web interface guidelines for interactions, accessibility, forms, motion, performance, responsive behavior, or copy.
5