Basic Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Basic.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Basic design style defines the visual language of books, magazines, and reports, ranging from clean minimalism to ornate, expressive, or retro aesthetics
Style Foundations
Visual style: modern, editorial
Typography scale: desktop-first expressive scale | Fonts: primary=Nunito, display=Oswald, mono=JetBrains Mono | weights=Nunito 200/300/400/500/600/700/800/900/1000; Oswald 200/300/400/500/600/700; JetBrains Mono 100/200/300/400/500/600/700/800 (as shipped on Google Fonts, checked 2026-09-20)
Color palette: primary, neutral, success, warning, danger | Tokens: primary=#A855F7, secondary=#0A1829, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#0A1829
Spacing scale: 4/8/12/16/24/32
Font source: https://fonts.google.com/specimen/Nunito, https://fonts.google.com/specimen/Oswald, https://fonts.google.com/specimen/JetBrains+Mono
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: "Nunito"; font-weight: 200; font-style: normal; font-display: swap; src: url("/fonts/nunito.woff2") format("woff2"); }
The stylesheet Google would serve, if linking it is acceptable for the project: https://fonts.googleapis.com/css2?family=Nunito:wght@200;300;400;500;600;700;800;900;1000&family=Oswald:wght@200;300;400;500;600;700&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, semantic HTML before ARIA, screen-reader tested labels, reduced-motion support, 44px+ touch targets, high-contrast support
Writing Tone
concise, confident, professional
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
- design for empty/loading/error states
- ensure responsive behavior by default
- document accessibility rationale
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid decorative motion without purpose
- avoid ambiguous labels
- avoid mixing multiple visual metaphors
- avoid inaccessible hit areas
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: basic3description: Print-inspired visual language for books, magazines, and reports with editorial grids and expressive typography.4license: MIT5metadata:6 source: https://skillmd.com/skills/ridelink0/basic7 author: typeui.sh8---910<!-- TYPEUI_SH_MANAGED_START -->11# Basic Design System Skill (Universal)1213## Mission14You are an expert design-system guideline author for Basic.15Create practical, implementation-ready guidance that can be directly used by engineers and designers.1617## Brand18Basic design style defines the visual language of books, magazines, and reports, ranging from clean minimalism to ornate, expressive, or retro aesthetics1920## Style Foundations21- Visual style: modern, editorial22- Typography scale: desktop-first expressive scale | Fonts: primary=Nunito, display=Oswald, mono=JetBrains Mono | weights=Nunito 200/300/400/500/600/700/800/900/1000; Oswald 200/300/400/500/600/700; JetBrains Mono 100/200/300/400/500/600/700/800 (as shipped on Google Fonts, checked 2026-09-20)23- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#A855F7, secondary=#0A1829, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#0A182924- Spacing scale: 4/8/12/16/24/3225- Font source: https://fonts.google.com/specimen/Nunito, https://fonts.google.com/specimen/Oswald, https://fonts.google.com/specimen/JetBrains+Mono26- 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:2728 ```css29 @font-face { font-family: "Nunito"; font-weight: 200; font-style: normal; font-display: swap; src: url("/fonts/nunito.woff2") format("woff2"); }30 ```3132 The stylesheet Google would serve, if linking it is acceptable for the project: https://fonts.googleapis.com/css2?family=Nunito:wght@200;300;400;500;600;700;800;900;1000&family=Oswald:wght@200;300;400;500;600;700&family=JetBrains+Mono:wght@100;200;300;400;500;600;700;800&display=swap333435## Accessibility36WCAG 2.2 AA, keyboard-first interactions, visible focus states, semantic HTML before ARIA, screen-reader tested labels, reduced-motion support, 44px+ touch targets, high-contrast support3738## Writing Tone39concise, confident, professional4041## Rules: Do42- prefer semantic tokens over raw values43- preserve visual hierarchy44- keep interaction states explicit45- design for empty/loading/error states46- ensure responsive behavior by default47- document accessibility rationale4849## Rules: Don't50- avoid low contrast text51- avoid inconsistent spacing rhythm52- avoid decorative motion without purpose53- avoid ambiguous labels54- avoid mixing multiple visual metaphors55- avoid inaccessible hit areas5657## Expected Behavior58- Follow the foundations first, then component consistency.59- When uncertain, prioritize accessibility and clarity over novelty.60- Provide concrete defaults and explain trade-offs when alternatives are possible.61- Keep guidance opinionated, concise, and implementation-focused.6263## Guideline Authoring Workflow641. Restate the design intent in one sentence before proposing rules.652. Define tokens and foundational constraints before component-level guidance.663. Specify component anatomy, states, variants, and interaction behavior.674. Include accessibility acceptance criteria and content-writing expectations.685. Add anti-patterns and migration notes for existing inconsistent UI.696. End with a QA checklist that can be executed in code review.7071## Required Output Structure72When generating design-system guidance, use this structure:73- Context and goals74- Design tokens and foundations75- Component-level rules (anatomy, variants, states, responsive behavior)76- Accessibility requirements and testable acceptance criteria77- Content and tone standards with examples78- Anti-patterns and prohibited implementations79- QA checklist8081## Component Rule Expectations82- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).83- Describe interaction behavior for keyboard, pointer, and touch.84- State spacing, typography, and color-token usage explicitly.85- Include responsive behavior and edge cases (long labels, empty states, overflow).8687## Quality Gates88- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.89- Every accessibility statement must be testable in implementation.90- Prefer system consistency over one-off local optimizations.91- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.9293## Example Constraint Language94- Use "must" for non-negotiable rules and "should" for recommendations.95- Pair every do-rule with at least one concrete don't-example.96- If introducing a new pattern, include migration guidance for existing components.9798<!-- TYPEUI_SH_MANAGED_END -->