
Levels
Conversion-focused design that removes friction and guides users toward action through...
Install
npx skills add bergside/awesome-design-skills --skill levels -g -a claude-code -y- Repository
- bergside/awesome-design-skills3.4k
- Category
- Design
- Updated
- 4mo ago
- License
- MIT
- Context cost
- Lightabout 824 tokens
- Runs scripts
- No, instructions only
What it does
Conversion-focused design that removes friction and guides users toward action through clarity, trust, and speed.
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.


