terracotta
bergside/awesome-design-skills
Earthy editorial design system with warm clay tones, serif typography, and terracotta accents for content-first interfaces.
What is terracotta?
Terracotta is a design-system skill that provides guidance for building editorial interfaces with warm, clay-toned aesthetics. Use it when creating long-form reading experiences, blogs, or storytelling layouts where readability and visual hierarchy are priorities.
- Generate design-system guidelines for consistent component implementation
- Define semantic design tokens (colors, typography, spacing) aligned to WCAG 2.2 AA accessibility
- Specify component anatomy, interaction states, and responsive behavior with concrete examples
- Create accessibility acceptance criteria and QA checklists for code review
- Provide anti-patterns and migration guidance for inconsistent existing UI
- Author content and tone standards with implementation-ready examples
How to install terracotta
npx skills add https://github.com/bergside/awesome-design-skills --skill terracottaHow to use terracotta
- 1.Install the skill using the provided npx command
- 2.Reference the Terracotta brand foundations (warm cream surfaces, ink-brown serif headlines, terracotta accent)
- 3.Use the guideline-authoring workflow to generate component-specific rules
- 4.Apply design tokens (primary=#C56A3C, secondary=#F3E9D8, etc.) and spacing scale (4/8/12/16/24/32)
- 5.Include accessibility requirements (WCAG 2.2 AA, 44px+ touch targets, visible focus states) in all guidance
- 6.Execute the QA checklist during code review to verify consistency
Use cases
- Building a blog or editorial publication with consistent visual language
- Creating design-system documentation for a team implementing a clay-toned interface
- Defining component rules (buttons, forms, cards) with accessibility-first constraints
- Establishing typography and spacing scales for long-form reading experiences
- Authoring migration guidance when refactoring existing UI to match Terracotta aesthetics
- Design-system authors and documentation writers
- Product engineers implementing component libraries
- Design leads establishing brand consistency across editorial products
- Teams building accessible, content-first interfaces
terracotta FAQ
Primary and display font is DM Serif Display; monospace is JetBrains Mono. Scale: 14/16/18/24/32/40px with weights 100–900.
Primary terracotta (#C56A3C), secondary cream (#F3E9D8), success (#16A34A), warning (#D97706), danger (#DC2626), surface white (#FFFFFF), and text dark gray (#111827).
Yes. It meets WCAG 2.2 AA, enforces keyboard-first interactions, visible focus states, 44px+ touch targets, and high-contrast support.
Use it for editorial layouts, blogs, long-form reading, and storytelling where visual rhythm, readability, and content hierarchy are central.
Restating design intent, defining tokens and foundations, specifying component anatomy and states, accessibility criteria, content standards, anti-patterns, and a QA checklist.
Full instructions (SKILL.md)
Source of truth, from bergside/awesome-design-skills.
name: "terracotta" description: "A sun-baked, clay-toned editorial interface built on warm cream surfaces, ink-brown headlines set in a display serif, and a single terracotta accent." metadata: author: typeui.sh
<!-- TYPEUI_SH_MANAGED_START -->Terracotta Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Terracotta. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
A sun-baked, clay-toned editorial interface built on warm cream surfaces, ink-brown headlines set in a display serif, and a single terracotta accent. Earthy, human, and content-first — tuned for long-form reading, blogs, storytelling, and editorial layouts where readability and visual rhythm matter.
Style Foundations
- Visual style: modern, clean, high-contrast, playful
- Typography scale: 14/16/18/24/32/40 | Fonts: primary=DM Serif Display, display=DM Serif Display, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#C56A3C, secondary=#F3E9D8, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 4/8/12/16/24/32
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states, 44px+ touch targets, high-contrast support
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.
Related skills
More from bergside/awesome-design-skills and the wider catalog.

