agentleFS
Sign inStart free
ouestlabsouestlabs/audio-ui/skills/design/SKILL.md

design

Skill202 starsChanged 29 days agoMITView on GitHub

Designs how an audio interface looks with audio/ui: picks a visual direction (retro hardware, skeuomorphic, minimalist, modern, and skins such as tape, phosphor, hifi, brutalist, y2k, console, synth70), ships ready CSS skins and the verified Panel markup for the headless @audio-ui/react primitives, and composes a look from a brief or a reference with materials, palettes, lighting and typography. Use when the user wants a synth, mixer, plugin, drum machine or DAW panel to look like hardware or like a named style, asks for retro, analog, skeuomorphic, minimal or modern audio UI, has no shadcn or Tailwind and needs the primitives styled, or when a panel looks flat, generic or AI-made and needs to read as an instrument.

197 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use banner-design, ui-styling and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • seikaikyoSkill

    banner-design

    Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with optional generated or supplied visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage.

    Also in 38 projects that use this

  • MicrosoftSkill

    ui-styling

    Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components.

    Also in 39 projects that use this

  • seikaikyoSkill

    brand

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

    Also in 43 projects that use this

  • mayankjain1815-commitsSkill

    infra-audit

    Reads docker-compose, env files, ORM configs, and connection strings to map current infrastructure. Flags missing layers (cache, queue, analytics) based on observed access patterns. Outputs a structured infrastructure manifest.

    Also in 3 projects that use this

  • JetBrainsSkill

    slides

    Create and edit presentation slide decks (`.pptx`) with PptxGenJS and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution.

    Also in 42 projects that use this

  • AnthropicSkill

    design-system

    Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.

    Also in 49 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the rule files for the explanation and the incorrect and correct code:

    line 52
  2. Distinctive:

    Every rule of this skill expanded in one file: AGENTS.md

    line 67

“Common” is measured: kept by at least 6 in 10 of the 174 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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/react primitives 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

PriorityCategoryImpactPrefix
1DesignHIGHdesign-

Quick Reference

1. Design (HIGH)

  • design-pick-a-direction - Choose retro, minimal or modern first, say it, and style every part from it
  • design-structure-before-skin - Start from styles/base.css: every part needs a size, and the inline position is the part's
  • design-one-light-source - One light, four or five materials, glow only on lamps
  • design-print-the-labels - Uppercase tracked labels, tabular values, printed ticks
  • design-size-by-importance - Group by signal flow in labelled sections, three sizes at most
  • design-feedback-by-state - Draw data-dragging, data-active, data-clipping and focus, not only hover
  • design-meter-zones - Zones on the channel, dimmed, lit by the indicator: a gradient on the indicator squeezes with the level

Workflow

  1. Choose a visual direction and say it in one sentence: retro hardware, minimal or modern (design.md).
  2. Copy styles/base.css, one skin and the Panel markup from directions.md. Every part needs a size, and the inline position is the part's.
  3. For a look the skins do not cover, or any reference the user names, compose it from styles/materials.css with taste.md. For retro, read hardware.md: what gives a panel taste, palettes by instrument.
  4. Group by signal flow in labelled sections, with three sizes at most, and draw state (data-dragging, data-active, focus), not only hover.
  5. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free