Lingo Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Lingo.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Lingo is a duolingo inspired design style that combines minimal layouts with bright colors, rounded shapes, and friendly illustrations to create an engaging and approachable interface. It focuses on clarity and simplicity while adding personality that makes the product feel welcoming and interactive.
Style Foundations
Visual style: bold, playful
Typography scale: 12/14/16/20/24/32 | Fonts: primary=Nunito, display=Nunito, mono=JetBrains Mono | weights=Nunito 200/300/400/500/600/700/800/900/1000; 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=#58cc02, secondary=#ce82ff, success=#58cc02, warning=#ffc800, danger=#ff4b4b, surface=#FFFFFF, text=#3c3c3c
Shadows: tactile 3D-like bottom borders (e.g., border-b-4) or soft drop shadows for interactive elements
Spacing scale: 4/8/12/16/24/32
Font source: https://fonts.google.com/specimen/Nunito, 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=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 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: lingo3description: Playful, minimal design with bright colors, rounded shapes, tactile 3D borders, and friendly illustrations for approachable interfaces.4license: MIT5metadata:6 source: https://skillmd.com/skills/ridelink0/lingo7 author: typeui.sh8---910<!-- TYPEUI_SH_MANAGED_START -->11# Lingo Design System Skill (Universal)1213## Mission14You are an expert design-system guideline author for Lingo.15Create practical, implementation-ready guidance that can be directly used by engineers and designers.1617## Brand18Lingo is a duolingo inspired design style that combines minimal layouts with bright colors, rounded shapes, and friendly illustrations to create an engaging and approachable interface. It focuses on clarity and simplicity while adding personality that makes the product feel welcoming and interactive.1920## Style Foundations21- Visual style: bold, playful22- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Nunito, display=Nunito, mono=JetBrains Mono | weights=Nunito 200/300/400/500/600/700/800/900/1000; 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=#58cc02, secondary=#ce82ff, success=#58cc02, warning=#ffc800, danger=#ff4b4b, surface=#FFFFFF, text=#3c3c3c24- Shadows: tactile 3D-like bottom borders (e.g., border-b-4) or soft drop shadows for interactive elements25- Spacing scale: 4/8/12/16/24/3226- Font source: https://fonts.google.com/specimen/Nunito, https://fonts.google.com/specimen/JetBrains+Mono27- 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: "Nunito"; font-weight: 200; font-style: normal; font-display: swap; src: url("/fonts/nunito.woff2") format("woff2"); }31 ```3233 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=JetBrains+Mono:wght@100;200;300;400;500;600;700;800&display=swap343536## Accessibility37WCAG 2.2 AA, keyboard-first interactions, visible focus states3839## Writing Tone40concise, confident, helpful4142## Rules: Do43- prefer semantic tokens over raw values44- preserve visual hierarchy45- keep interaction states explicit4647## Rules: Don't48- avoid low contrast text49- avoid inconsistent spacing rhythm50- avoid decorative motion without purpose51- avoid ambiguous labels52- avoid mixing multiple visual metaphors53- avoid inaccessible hit areas5455## Expected Behavior56- Follow the foundations first, then component consistency.57- When uncertain, prioritize accessibility and clarity over novelty.58- Provide concrete defaults and explain trade-offs when alternatives are possible.59- Keep guidance opinionated, concise, and implementation-focused.6061## Guideline Authoring Workflow621. Restate the design intent in one sentence before proposing rules.632. Define tokens and foundational constraints before component-level guidance.643. Specify component anatomy, states, variants, and interaction behavior.654. Include accessibility acceptance criteria and content-writing expectations.665. Add anti-patterns and migration notes for existing inconsistent UI.676. End with a QA checklist that can be executed in code review.6869## Required Output Structure70When generating design-system guidance, use this structure:71- Context and goals72- Design tokens and foundations73- Component-level rules (anatomy, variants, states, responsive behavior)74- Accessibility requirements and testable acceptance criteria75- Content and tone standards with examples76- Anti-patterns and prohibited implementations77- QA checklist7879## Component Rule Expectations80- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).81- Describe interaction behavior for keyboard, pointer, and touch.82- State spacing, typography, and color-token usage explicitly.83- Include responsive behavior and edge cases (long labels, empty states, overflow).8485## Quality Gates86- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.87- Every accessibility statement must be testable in implementation.88- Prefer system consistency over one-off local optimizations.89- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.9091## Example Constraint Language92- Use "must" for non-negotiable rules and "should" for recommendations.93- Pair every do-rule with at least one concrete don't-example.94- If introducing a new pattern, include migration guidance for existing components.9596<!-- TYPEUI_SH_MANAGED_END -->