Levels design skill for AI agents
Overview
The Levels design skill is a comprehensive, implementation-ready design system guideline built for AI agents. It encodes the entire visual identity, component specifications, and interaction standards of the Levels brand into a single SKILL.md file that any AI coding assistant can follow.
Levels design focuses on removing friction, building trust, and guiding users toward a specific action through clarity, psychology, and speed. Every rule in this skill file is anchored to a concrete token, threshold, or example — no ambiguous adjectives.
Style foundations
The Levels design system is built on a modern, clean visual style with carefully defined foundations.
Typography
The type scale uses Inter as the primary and display font, with JetBrains Mono for code and monospaced elements. The scale follows a progression of 12 / 14 / 16 / 20 / 24 / 32 pixels, and all nine font weights (100–900) are available for precise typographic control.
Color palette
| Token | Hex | Usage |
|---|---|---|
| Primary | #27272A |
Primary actions and text |
| Secondary | #8B5CF6 |
Accents and secondary actions |
| Success | #16A34A |
Positive states and confirmations |
| Warning | #D97706 |
Cautionary states and alerts |
| Danger | #DC2626 |
Error states and destructive actions |
| Surface | #FFFFFF |
Backgrounds and card surfaces |
| Text | #111827 |
Body text and headings |
The system uses semantic tokens across five palettes — primary, neutral, success, warning, and danger — so components reference tokens rather than raw hex values.
Spacing
All spacing follows a 4 / 8 / 12 / 16 / 24 / 32 pixel scale to maintain a consistent vertical and horizontal rhythm across every component.
Component families
The Levels skill covers a wide range of component families, organized into logical groups:
- Inputs and forms — buttons, inputs, textareas, selects/comboboxes, checkboxes, radios, switches, date/time pickers, file uploaders
- Data display — cards, tables, data lists, data grids, charts, stats/metrics, badges/chips, avatars
- Navigation — breadcrumbs, pagination, steppers, sidebars, top bars/headers, tabs, command palette
- Overlays — modals, drawers/sheets, tooltips, popovers/menus
- Feedback — alerts/toasts, notifications center, progress indicators, skeletons, empty states
- Pages — authentication screens, settings pages, onboarding, documentation layouts, pricing blocks, search
- Visualization — data visualization wrappers, carousels, accordions
Each component family includes defined states (default, hover, focus-visible, active, disabled, loading, error), interaction behavior for keyboard, pointer, and touch, explicit token usage, and responsive behavior with edge cases.
Accessibility
This skill targets WCAG 2.2 AA compliance with keyboard-first interactions and visible focus states. Every accessibility statement in the file is testable in implementation. When conflicts arise between aesthetics and accessibility, accessibility wins.
How to use this skill with AI agents
Pull the skill file into your project with a single command:
npx typeui.sh pull levels
This saves the SKILL.md file directly into your project. From there you can use it with any AI coding tool — Claude, ChatGPT, Cursor, Windsurf, Copilot, or any other agent that accepts context files, system prompts, or knowledge documents.
The file is standard markdown. Copy it into a project knowledge base, reference it as context in a prompt, upload it as a knowledge file, or drop it into a rules directory. The structured format ensures consistent results regardless of which AI platform you use.
Design principles
The Levels skill enforces three core rules:
- Prefer semantic tokens over raw values — always reference design tokens instead of hardcoded colors, sizes, or spacing
- Preserve visual hierarchy — maintain clear distinctions between headings, body text, and supporting elements
- Keep interaction states explicit — every interactive element must define its full state set
And three strict anti-patterns to avoid:
- No low contrast text — all text must meet WCAG AA contrast ratios
- No inconsistent spacing rhythm — every measurement must align to the spacing scale
- No ambiguous labels — interactive elements must have clear, descriptive labels
Writing tone
All content generated with this skill follows a concise, confident, and helpful tone. Labels are clear. Instructions are direct. There is no unnecessary jargon or decoration.