agentleFS
Sign inStart free
ishwar-iyer12ishwar-iyer12/design-toolkit/skills/awesome-design/SKILL.md

awesome-design

Skill0 starsChanged 45 days agoMITView on GitHub

A library of DESIGN.md files describing the visual systems of well-known products. Use when asked to build UI "in the style of" a named product, or when a project needs a concrete visual reference to start from.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. fernandomoralesabogado-netizen/CLAUDE-SKILLS★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read that DESIGN.md in full before writing code.

    line 13
  2. Very specific:

    If the project has no tokens yet, copy the chosen file to the project root as DESIGN.md and treat it as the reference.

    line 14
  3. Distinctive:

    If nothing matches, say so and offer the three closest.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Awesome design

This folder holds 74 DESIGN.md files from the awesome-design-md collection by VoltAgent, vendored under the MIT licence. Each one describes the colours, type, spacing and components of one product's public website. I wrote this SKILL.md; the files in design-md/ are theirs. See NOTICE.md for what was changed.

How to use it

  1. List design-md/ and find the folder that matches the product named in the request. Folder names are lowercase, for example linear.app, stripe, notion.
  2. Read that DESIGN.md in full before writing code. The front matter holds the tokens. The prose explains how they are used.
  3. If the project has no tokens yet, copy the chosen file to the project root as DESIGN.md and treat it as the reference.
  4. If nothing matches, say so and offer the three closest. Do not blend several files into one.

Limits

  • These are descriptions of other companies' sites, written by a third party. They are a reference for style, not permission to copy a brand. Do not reproduce logos, product names or trademarked assets.
  • Many of them name proprietary fonts. Use the open fallback the file suggests.
  • The taste skill still applies. Where a DESIGN.md asks for gradients or shadows, keep them to the places that file names.
  • The files were accurate when vendored. Sites change. The upstream project publishes current versions at https://getdesign.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