levels
bergside/awesome-design-skills
Conversion-focused design system removing friction through clarity, trust, and speed.
What is levels?
Levels is a design-system skill for creating implementation-ready guidance on conversion-focused UI. It provides foundations for typography, color, spacing, and component rules anchored to accessibility (WCAG 2.2 AA) and semantic tokens, helping teams build consistent, friction-free user experiences.
- Generate design-system guidelines with explicit component anatomy, states, and interaction behavior
- Define and enforce semantic design tokens (color, typography, spacing) across projects
- Author accessibility-first rules with testable acceptance criteria (WCAG 2.2 AA, keyboard-first)
- Create QA checklists and anti-pattern documentation for code review
- Provide responsive behavior and edge-case guidance for components
How to install levels
npx skills add https://github.com/bergside/awesome-design-skills --skill levelsHow to use levels
- 1.State the design intent in one sentence before proposing any rules
- 2.Define design tokens and foundational constraints (typography scale, color palette, spacing rhythm) before component guidance
- 3.Specify component anatomy, required states (default, hover, focus-visible, active, disabled, loading, error), and interaction behavior for keyboard, pointer, and touch
- 4.Include accessibility acceptance criteria and testable WCAG 2.2 AA requirements
- 5.Document content and tone standards with concrete examples
- 6.List anti-patterns and prohibited implementations to avoid
- 7.End with a QA checklist executable during code review
Use cases
- Establishing design consistency across a product team by documenting component rules and token usage
- Onboarding new designers and engineers with concrete, implementation-ready guidelines instead of vague principles
- Auditing existing UI for accessibility violations and inconsistent spacing or typography
- Creating migration paths when refactoring components to meet new design standards
- Documenting interaction states (hover, focus, active, disabled, loading, error) for engineering handoff
- Design system authors and maintainers
- Product designers building conversion-focused interfaces
- Frontend engineers implementing design specifications
- Design leads establishing consistency across teams
- Teams prioritizing accessibility and user clarity
levels FAQ
Levels includes a typography scale (12/14/16/20/24/32px with Inter and JetBrains Mono fonts), a color palette (primary #27272A, secondary #8B5CF6, success #16A34A, warning #D97706, danger #DC2626, surface #FFFFFF, text #111827), and a spacing scale (4/8/12/16/24/32px). Use semantic token names rather than raw values.
Yes. Levels enforces WCAG 2.2 AA accessibility standards, including keyboard-first interactions, visible focus states, and no low-contrast text. Every accessibility rule must be testable in implementation.
Define all relevant states explicitly: default, hover, focus-visible, active, disabled, loading, and error. For each state, specify spacing, typography, color tokens, and interaction behavior for keyboard, pointer, and touch inputs.
Prioritize accessibility. Flag the conflict in your guidance, explain the trade-off, and choose the accessible option. Levels treats accessibility as non-negotiable.
Yes. Include migration guidance when introducing new patterns to existing components, and use anti-pattern documentation to help teams refactor inconsistent UI incrementally.
Full instructions (SKILL.md)
Source of truth, from bergside/awesome-design-skills.
name: levels description: Conversion-focused design that removes friction and guides users toward action through clarity, trust, and speed. license: MIT metadata: author: typeui.sh
<!-- TYPEUI_SH_MANAGED_START -->levels Design System Skill (Universal)
Mission
You are an expert design-system guideline author for levels. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Levels design focuses on removing friction, building trust, and guiding users toward a specific action through clarity, psychology, and speed
Style Foundations
- Visual style: modern, clean
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Inter, display=Inter, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#27272A, secondary=#8B5CF6, 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
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.
