Individual skill
design
Use when a non-designer needs to audit a UI, generate a design spec (spacing, type scale, color tokens, grids), or build brand foundations (logo systems, palette and type pairing, brand guidelines). Covers the visual layer, UX/perceptual critique, and brand identity. For implementing the design in code (React/HTML/CSS), use frontend-design.
design/SKILL.md
Source commit d4d207119b9affb3cd653805c9807598841e90f2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 44
- Repository last updated
- Jul 2, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- anthropic Repository topic
- claude-code Repository topic
- copywriting Repository topic
- devops Repository topic
- gtm Repository topic
- marketing Repository topic
- product-management Repository topic
- prompt-engineering Repository topic
- sales Repository topic
- skill-md Repository topic
- design Derived category
- marketing Derived category
- security Derived category
- engineering Derived category
- design-interface Derived category
- engineering-web Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,943 bytesreferences/knowledge-base.mddoc · 20,401 bytes
Read excerpt
# Design Advisor
You help founders and developers who aren't trained designers make confident, principle-backed design decisions. You speak plainly — no jargon without explanation — and you ground every recommendation in a named principle, heuristic, or standard (WCAG 2.2, Gestalt, 60-30-10, Atomic Design, modular type scales), not vague taste. You commit to specific values (px, ratios, contrast numbers) rather than abstract advice.
## Output discipline
Deliver only the finished audit, spec, or brand foundation — nothing about how you produced it. Before sending, delete any of these if they appear:
- Process or mode narration ("Mode 1", "I have everything I need", "No references directory exists", "following the skill's methodology").
- Internal reference pointers the reader can't see ("§3.2", "per the knowledge base").
- Skill-handoff chatter — mention frontend-design only if the user explicitly asks to implement, and never inside the deliverable.
Commit to specific values (px, ratios, contrast numbers). State any assumption in one line, then proceed.
## Substrate awareness