agentleFS
Sign inStart free
adityareddy-devadityareddy-dev/deskstudio/skills/design-system/SKILL.md

design-system

Skill43 starsChanged 23 days agoMITView on GitHub

Generate, extract or audit the project's design tokens: writes or lints .desk/DESIGN.md and exports CSS custom properties or a Tailwind theme. Use when a project needs its tokens made, pulled out of existing code, or checked for drift.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-engine, team-level 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.
  • CoralGameSkill

    setup-engine

    Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.

    Also in 13 projects that use this

  • CoralGameSkill

    team-level

    Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

    Also in 12 projects that use this

  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • +2 more from CoralGame
  • +6 more from lilangMax

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run: Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 175 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

Make or check a token system as the Design Manager.

Deliverable and standard. A token set: colour by job, type scale, spacing, radii, motion. The brand-kit standard's DESIGN.md front matter is the shape, and the sheet renders to the dashboard standard's density rules. Three modes:

  • generate: from a brief or one colour, three directions of palette and type, one picked, written to .desk/DESIGN.md.
  • extract: read the project (CSS custom properties, Tailwind config, tokens files, the live site's header) with the brand-from-project procedure and write .desk/DESIGN.md from what is there, naming the sources.
  • audit: lint the project against .desk/DESIGN.md: colours off the palette, sizes off the scale, spacing off the grid, radii not in the set, each with file and line.

Desks.

DeskAgentTierDoes
Design System Leaddesk:design-system-leadseniorowns the token set, the naming and the audit rules
Typographerdesk:typographerseniorthe type scale, weights, fallback stack
Accessibility Specialistdesk:accessibility-specialistseniorevery text pair's contrast, focus and border colours
Design Engineerdesk:design-engineerbuilderthe exports and the sheet, polish rounds
Art Directordesk:art-directordirectorthe pick between the three directions (generate only)
Creative Directordesk:creative-directordirectorsign-off on the rendered sheet

Inputs. Text (a brief, one or two hex colours), a path to a project or a tokens file, or a URL to pull a palette from.

Proof sizes. desktop for the sheet, light and dark.

Output under .desk/out/<id>/:

  • DESIGN.md in the exact front matter shape, copied to .desk/DESIGN.md on sign-off (generate and extract).
  • tokens.css with every token as a custom property in :root and [data-theme="dark"], and tailwind.theme.js exporting theme.extend, by --export (default both).
  • sheet.html: the tokens rendered: palette with contrast ratios, the scale as real text, spacing and radii, the four motion moves.
  • audit.md (audit only): findings as file, line, value, nearest token, grouped by kind.

Run. Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above. Command name for state and events: design-system. Changes to the loop for this command:

  • generate runs the full loop: three rough sheets (Design Engineer at the senior model, each with a palette and type direction from the Typographer), pick, polish, proof, sign-off.
  • extract skips roughs and the pick: one sheet, polish until proof passes and the Creative Director signs it.
  • audit skips roughs, pick, polish and sign-off: the Design System Lead's report is the deliverable. Exit with the findings count in the handback.
  • Step 0's brand check is skipped: this command writes the brand file.

The ask: $ARGUMENTS

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