agentleFS
Sign inStart free
F0rger123F0rger123/CLAUDE-DESIGN-GOD-MODE/skills/direction/SKILL.md

direction

Skill1 starsChanged 19 days agoMITView on GitHub

Use when a project needs a visual direction or design system before building or restyling - choosing colours, fonts, type scale, spacing, radius, shadows and motion as tokens. Produces a short DESIGN.md token plan matched to the product and checked against generic defaults.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. agiea-brain/agency-skills★ 1same name
    2. alanvaa06/award-craft★ 1same name
    3. ofweb/skills★ 1same 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 repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    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. Distinctive:

    Write down 5 concrete nouns from the product's real world (for a roofing CRM: shingles, ladders, invoices, weather, trucks).

    line 11
  2. Very specific:

    Use references/color.md and references/type.md.

    line 25

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

Design Direction

Decide the look on paper first. A 30-line plan saves hours of restyling.

1. Find the subject's world

Write down 5 concrete nouns from the product's real world (for a roofing CRM: shingles, ladders, invoices, weather, trucks). Distinct choices come from these, not from "modern and clean".

2. Set three dials (1-10)

DialLowHighTypical
Variancecentred, symmetric, calmasymmetric, editorial, surprisingLanding 6-8, CRM 2-4, Game 7-9
Motioninstant, minimalchoreographed, playfulLanding 4-6, CRM 2-3, Game 7-9
Densityairy, big spacingpacked, small spacingLanding 2-4, CRM 6-8, Game HUD 5-7

3. Pick a style family

Open references/styles.md and choose one family that fits the product and the dials. Bend it toward the subject's world. Do not stack two families.

4. Write the token plan

Use references/color.md and references/type.md. Output this, saved as DESIGN.md in the project root when the user wants it kept:

# Design: <product>
Read: <one line>. Mode: <mode>. Dials: variance 7 / motion 4 / density 3.
Family: <style family> — <one sentence on how it is bent to this subject>

Colour   bg #… · surface #… · ink #… · muted #… · accent #… · accent-ink #… (+ success/warn/danger if Operate)
Type     display <font> 600-800, tight -0.02em · body <font> 400/500 · scale 1.25 (14/16/20/25/31/39/49/61)
Space    4px base: 4 8 12 16 24 32 48 64 96 128
Radius   <values per size: e.g. 6 inputs, 10 cards, 999 pills>
Shadow   <1-2 layered shadows tinted with ink, or none>
Motion   ease-out cubic-bezier(.23,1,.32,1) · 150-250ms UI · one signature moment: <what>
Signature <the one memorable thing on this site>
Never    <2-3 things this design refuses to do>

5. Anti-default check (required)

Ask: "Would I produce this same plan for any other product in this category?" For each part that answers yes, change it and say why in one line. Common defaults to question: Inter + slate + indigo; purple gradients; cream + terracotta + serif; black + acid green; one radius everywhere.

The user's own brand, colours or fonts always win over this check.

Implementation targets

  • Tailwind v4: tokens in @theme { --color-*, --font-*, --radius-* } in the main CSS.
  • Tailwind v3: theme.extend in tailwind.config.
  • shadcn/ui: map tokens onto --background --foreground --primary --muted --border --ring --radius (HSL or OKLCH as the project already uses).
  • Plain CSS: custom properties on :root, dark values under [data-theme="dark"] and prefers-color-scheme.
  • Fonts: self-host or next/font; otherwise Google Fonts with display=swap and preconnect.

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