agentleFS
sukirman1901sukirman1901/frontend-expert/skills/tokens/SKILL.md

tokens

Skill9 starsChanged 2 months agoMITView on GitHub

Choose and apply CSS design tokens via decision tree (project system, explicit preset, Plasma hard-gate, or scored pack preset) — colors, spacing, radius, typography; no raw hex. Use whenever building or styling any user-facing UI, page, layout, component, theme, or brand look — including chats like "bikin halaman", "styling", "warna", or "design system" even if the user never types /ui.

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use audit.

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.
  • OpenAISkill

    audit

    Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    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 Tailwind theme / :root CSS variables / theme provider

    line 45
  2. Very specific:

    Never invent raw hex like #7c3aed

    line 59

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

Overview

Enforce token-based styling. Use CSS custom properties from tokens/ presets, or the project's existing design system — never invent raw hex or off-scale spacing.

When to Use

  • Starting UI work that needs a visual system
  • Applying colors, spacing, radius, or typography
  • /ui --token <file> or /ui --custom

Decision tree

Canonical tree + scoring math: references/token-preset-scoring.md (follow that file; first matching branch wins).

--custom / existing theme / keep palette?
  YES → CUSTOM: style-infer → project vars (no score)
  NO  ↓
--token <file> / user named a preset?
  YES → EXPLICIT: that file (no score)
  NO  ↓
Explicit Plasma brand?
  YES → HARD-GATE: plasma-landing.css
  NO  ↓
SCORE PATH: signals → score all presets → penalties → #1 (+ runner-up ≤2)
         → emit Token score → apply

Workflow

  1. Walk the decision tree (above) — do not skip to affinity-hint vibes.
  2. Custom branch — style inference before inventing visuals:
    • Read Tailwind theme / :root CSS variables / theme provider
    • Skim 2–3 existing buttons, cards, forms (padding, radius, shadow, type)
    • Reuse those patterns; store nothing exotic outside the project language
  3. Score branch — mandatory when tree lands on SCORE PATH:
    • Extract signals: Surface · Density · Expression · Warmth · Radius · Accent · Inspiration
    • Weighted score per preset (max 24); apply purple/Plasma penalties
    • Choose #1; runner-up if within 2 points
    • Emit Token score; Conventions: Tokens: … (score n/24)
    • Top < 8 + thin signals → one clarifying Q, then rescore once
  4. Explicit / hard-gate — apply that file; Conventions note (explicit) or (hard-gate)
  5. Apply rules (after source chosen)
    • HSL presets (stone-emerald, etc.): hsl(var(--primary)), hsl(var(--muted)), …
    • OKLCH / hex presets (neutral-oklch*.css, stone-oklch.css, plasma-landing.css): var(--primary) — do not wrap in hsl()
    • Plasma landing also exposes native names: var(--bg-main), var(--primary-color), …
    • Never invent raw hex like #7c3aed
    • Spacing: 0.25rem increments only
    • Radius: match --radius from the token file
    • Type: h1 → h2 → h3 → body → small; one h1 per page

Preset index (scoring hints only — not a picker)

FileBasePrimaryRadiusAffinity hint (not a picker)
neutral-oklch.cssneutralmono (OKLCH)0Modern minimal / sharp UI
neutral-oklch-rounded.cssneutralmono (OKLCH)0.625remMono OKLCH + soft radius
stone-oklch.csswarm stonemono warm (OKLCH)0Editorial / warm minimal
plasma-landing.csszinc-950purple #6C5CE714pxPlasma marketing landing
stone-emerald.cssstoneemerald0Clean, minimal
zinc-blue.csszincblue0.5Professional dashboards
neutral-purple.cssneutralviolet0.75Creative portfolios (brand cue required)
slate-cyan.cssslatecyan1Data-heavy interfaces
rose-amber.cssroseamber1.5Warm, friendly products

Checklist

  • Decision tree walked (custom / explicit / hard-gate / score)
  • If score path: signals + ranked scores emitted
  • Style inferred from existing components when custom
  • No raw hex / RGB outside token definitions
  • Spacing on 0.25rem scale
  • Border radius matches token file
  • Light/dark variables respected if present

Depth

Decision tree + scoring rubric: references/token-preset-scoring.md.
Token CSS files + import notes: tokens/README.md.
Style inference: references/design-axes.md.
Color theory + neutrals/accent/semantic recipe: references/ux-foundations.md.
Component usage: references/component-patterns.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.