Designing audio interfaces with audio/ui
@audio-ui/react primitives are headless: they bring behavior, input and ARIA, and no look. This skill gives them one. Choose a direction first and say it in a sentence, then style every part from it; mixing three looks is what makes a panel read as a template.
When to Apply
- A synth, mixer, plugin, sampler or drum machine panel that should look like hardware, or like a named style
- Retro, skeuomorphic, minimalist or modern directions, with or without shadcn/ui or Tailwind
- Styling
@audio-ui/reactprimitives from scratch with a ready skin - A look the skins do not cover, or a reference the user names
- Reviewing a panel that looks flat, generic or uneven
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Design | HIGH | design- |
Quick Reference
1. Design (HIGH)
design-pick-a-direction- Choose retro, minimal or modern first, say it, and style every part from itdesign-structure-before-skin- Start fromstyles/base.css: every part needs a size, and the inline position is the part'sdesign-one-light-source- One light, four or five materials, glow only on lampsdesign-print-the-labels- Uppercase tracked labels, tabular values, printed ticksdesign-size-by-importance- Group by signal flow in labelled sections, three sizes at mostdesign-feedback-by-state- Drawdata-dragging,data-active,data-clippingand focus, not only hoverdesign-meter-zones- Zones on the channel, dimmed, lit by the indicator: a gradient on the indicator squeezes with the level
Workflow
- Choose a visual direction and say it in one sentence: retro hardware, minimal or modern (design.md).
- Copy
styles/base.css, one skin and thePanelmarkup from directions.md. Every part needs a size, and the inline position is the part's. - For a look the skins do not cover, or any reference the user names, compose it from
styles/materials.csswith taste.md. For retro, read hardware.md: what gives a panel taste, palettes by instrument. - Group by signal flow in labelled sections, with three sizes at most, and draw state (
data-dragging,data-active, focus), not only hover. - Verify. Render the page and look at a screenshot; check the panel at the size it ships.
Outside React the same skins apply, with styles/dom.css and the plain DOM kit of the core skill. Choosing, installing and wiring the components: the audio-ui skill.
How to Use
Read the rule files for the explanation and the incorrect and correct code:
rules/design-pick-a-direction.md
rules/design-one-light-source.md
- design.md: choosing a direction, what every direction shares, the part gotchas
- directions.md: retro, minimal and modern skins to copy (
styles/), with the verified markup - taste.md: composing any direction from a brief, with a vocabulary of looks and the slop signals to avoid
- hardware.md: what gives a retro panel taste, palettes by instrument
- Full docs: https://www.audio-ui.dev/llms.txt
Full Compiled Document
Every rule of this skill expanded in one file: AGENTS.md