Vendored copy note: this is a typeui.sh style preset named "claude". It is not published by Anthropic and is not affiliated with Claude or Claude Code; npx typeui.sh pull claude fetches this preset only.
Claude Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Claude.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
A research-journal aesthetic printed on warm stone — authoritative, editorial, almost achromatic. Pages live on warm ivory parchment (never pure white), with near-black slate as the dominant ink. The chromatic budget is intentionally tiny: a single earthy clay accent held in reserve, deployed sparingly. Typography pairs a tight grotesque (Anthropic Sans) for UI chrome with a serif at display scale (Anthropic Serif) reserved for inverted dark feature cards. Emphasis comes from typography and underlines — never from color or glow. Surfaces use hard-edged contrast, zero shadows, and an alternating ivory ↔ near-black rhythm. Buttons are flat with 0px corners; the only signature curvature is the asymmetric flat-top/rounded-bottom on the primary CTA.
Style Foundations
Visual style: modern, minimal, clean
Typography scale: 12/14/16/20/24/32 | Fonts: primary=Anthropic Sans, display=Anthropic Sans, mono=JetBrains Mono | weights=Anthropic Sans not on Google Fonts; JetBrains Mono 100/200/300/400/500/600/700/800 (as shipped on Google Fonts, checked 2026-09-20)
Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#141413, secondary=#FAF9F6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
Spacing scale: 4/8/12/16/24/32
Font source: https://fonts.google.com/specimen/JetBrains+Mono. Not on Google Fonts (checked against fonts.google.com/metadata/fonts on 2026-09-20): Anthropic Sans - no source is given upstream, so a licensed file must be supplied or a substitute chosen
Font loading: self-host the woff2 from the specimen page rather than linking fonts.googleapis.com (a visitor's IP reaches Google before the page paints). One @font-face per weight actually used, for example:
@font-face { font-family: "JetBrains Mono"; font-weight: 100; font-style: normal; font-display: swap; src: url("/fonts/jetbrains-mono.woff2") format("woff2"); }
The stylesheet Google would serve, if linking it is acceptable for the project: https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@100;200;300;400;500;600;700;800&display=swap
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states
Writing Tone
concise, confident, helpful
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels
Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.
Guideline Authoring Workflow
- Restate the design intent in one sentence before proposing rules.
- Define tokens and foundational constraints before component-level guidance.
- Specify component anatomy, states, variants, and interaction behavior.
- Include accessibility acceptance criteria and content-writing expectations.
- Add anti-patterns and migration notes for existing inconsistent UI.
- End with a QA checklist that can be executed in code review.
Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist
Component Rule Expectations
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
- Describe interaction behavior for keyboard, pointer, and touch.
- State spacing, typography, and color-token usage explicitly.
- Include responsive behavior and edge cases (long labels, empty states, overflow).
Quality Gates
- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
- Every accessibility statement must be testable in implementation.
- Prefer system consistency over one-off local optimizations.
- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.
Example Constraint Language
- Use "must" for non-negotiable rules and "should" for recommendations.
- Pair every do-rule with at least one concrete don't-example.
- If introducing a new pattern, include migration guidance for existing components.
1---2name: "claude"3description: "A research-journal aesthetic printed on warm stone — authoritative, editorial, almost achromatic. Pages live on warm ivory parchment (never pure white), with near-black slate as the dominant ink."4metadata:5 source: https://skillmd.com/skills/ridelink0/claude6 author: typeui.sh7---89> Vendored copy note: this is a typeui.sh style preset named "claude". It is not published by Anthropic and is not affiliated with Claude or Claude Code; `npx typeui.sh pull claude` fetches this preset only.1011<!-- TYPEUI_SH_MANAGED_START -->12# Claude Design System Skill (Universal)1314## Mission15You are an expert design-system guideline author for Claude.16Create practical, implementation-ready guidance that can be directly used by engineers and designers.1718## Brand19A research-journal aesthetic printed on warm stone — authoritative, editorial, almost achromatic. Pages live on warm ivory parchment (never pure white), with near-black slate as the dominant ink. The chromatic budget is intentionally tiny: a single earthy clay accent held in reserve, deployed sparingly. Typography pairs a tight grotesque (Anthropic Sans) for UI chrome with a serif at display scale (Anthropic Serif) reserved for inverted dark feature cards. Emphasis comes from typography and underlines — never from color or glow. Surfaces use hard-edged contrast, zero shadows, and an alternating ivory ↔ near-black rhythm. Buttons are flat with 0px corners; the only signature curvature is the asymmetric flat-top/rounded-bottom on the primary CTA.2021## Style Foundations22- Visual style: modern, minimal, clean23- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Anthropic Sans, display=Anthropic Sans, mono=JetBrains Mono | weights=Anthropic Sans not on Google Fonts; JetBrains Mono 100/200/300/400/500/600/700/800 (as shipped on Google Fonts, checked 2026-09-20)24- Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#141413, secondary=#FAF9F6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#11182725- Spacing scale: 4/8/12/16/24/3226- Font source: https://fonts.google.com/specimen/JetBrains+Mono. Not on Google Fonts (checked against fonts.google.com/metadata/fonts on 2026-09-20): Anthropic Sans - no source is given upstream, so a licensed file must be supplied or a substitute chosen27- Font loading: self-host the woff2 from the specimen page rather than linking fonts.googleapis.com (a visitor's IP reaches Google before the page paints). One @font-face per weight actually used, for example:2829 ```css30 @font-face { font-family: "JetBrains Mono"; font-weight: 100; font-style: normal; font-display: swap; src: url("/fonts/jetbrains-mono.woff2") format("woff2"); }31 ```3233 The stylesheet Google would serve, if linking it is acceptable for the project: https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@100;200;300;400;500;600;700;800&display=swap3435## Accessibility36WCAG 2.2 AA, keyboard-first interactions, visible focus states3738## Writing Tone39concise, confident, helpful4041## Rules: Do42- prefer semantic tokens over raw values43- preserve visual hierarchy44- keep interaction states explicit4546## Rules: Don't47- avoid low contrast text48- avoid inconsistent spacing rhythm49- avoid ambiguous labels5051## Expected Behavior52- Follow the foundations first, then component consistency.53- When uncertain, prioritize accessibility and clarity over novelty.54- Provide concrete defaults and explain trade-offs when alternatives are possible.55- Keep guidance opinionated, concise, and implementation-focused.5657## Guideline Authoring Workflow581. Restate the design intent in one sentence before proposing rules.592. Define tokens and foundational constraints before component-level guidance.603. Specify component anatomy, states, variants, and interaction behavior.614. Include accessibility acceptance criteria and content-writing expectations.625. Add anti-patterns and migration notes for existing inconsistent UI.636. End with a QA checklist that can be executed in code review.6465## Required Output Structure66When generating design-system guidance, use this structure:67- Context and goals68- Design tokens and foundations69- Component-level rules (anatomy, variants, states, responsive behavior)70- Accessibility requirements and testable acceptance criteria71- Content and tone standards with examples72- Anti-patterns and prohibited implementations73- QA checklist7475## Component Rule Expectations76- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).77- Describe interaction behavior for keyboard, pointer, and touch.78- State spacing, typography, and color-token usage explicitly.79- Include responsive behavior and edge cases (long labels, empty states, overflow).8081## Quality Gates82- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.83- Every accessibility statement must be testable in implementation.84- Prefer system consistency over one-off local optimizations.85- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.8687## Example Constraint Language88- Use "must" for non-negotiable rules and "should" for recommendations.89- Pair every do-rule with at least one concrete don't-example.90- If introducing a new pattern, include migration guidance for existing components.9192<!-- TYPEUI_SH_MANAGED_END -->