agentleFS
aniq-ui-proaniq-ui-pro/agent-skills/skills/design-rules/SKILL.md

design-rules

Skill1 starsChanged 2 days agoMITView on GitHub

Use when asked to improve, polish, restyle or fix the design of a page or component in a project that already has a design system (CSS variables, a Tailwind theme, light and dark themes, maybe a right-to-left language). Keeps every change inside the project's own tokens, theme-safe and RTL-safe, with a check after each step. Not for designing a new brand from scratch.

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. xenodeve/xeno-skills★ 2same 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Read the token file(s): CSS custom properties (globals.css, theme*.css, @theme in Tailwind 4) or tailwind.config.*.

    line 14
  2. Very specific:

    Run the checker on the files you will touch and save the counts: node ${CLAUDE_SKILL_DIR}/scripts/design-check.mjs <files or folder> --save …

    line 23
  3. Distinctive:

    If you can, screenshot the page in light and dark, and in RTL if the project has it.

    line 25
  4. Very specific:

    Every link and button shows keyboard focus (focus-visible: ring or outline in a token colour).

    line 41
  5. Distinctive:

    Keep the brand: same fonts, same accent, same imagery.

    line 44
  6. Very specific:

    Check (after each section you change): run the checker with --against /tmp/design-before.json.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Design rules for an existing design system

The project already made its big choices: palette, fonts, radius, spacing. Your job is to make the page better inside those choices, not to bring new ones. Work in this order and run each check before you move on.

1. Find the system

Read the token file(s): CSS custom properties (globals.css, theme*.css, @theme in Tailwind 4) or tailwind.config.*. Note the colour tokens, the type scale, the radius scale, the fonts, how dark mode switches (data-theme, .dark, media query) and whether a locale runs right to left (dir="rtl", an ar/he/fa message file). Check: you can name the token for page background, card fill, text, muted text, border and accent, plus the radius and heading steps. If you cannot, read more before editing.

2. Take a baseline

Run the checker on the files you will touch and save the counts: node ${CLAUDE_SKILL_DIR}/scripts/design-check.mjs <files or folder> --save /tmp/design-before.json If you can, screenshot the page in light and dark, and in RTL if the project has it. Check: the counts file exists and you have the "before" pictures.

3. Edit by these rules

  • Colours come from tokens only. No new hex, rgb or palette classes (bg-blue-500). If a colour is really missing, add a token with a value in every theme block.
  • Sizes come from the scale: use the project's heading, text and radius steps before any text-[37px]. Two headings of the same rank get the same size.
  • Directions are logical: ms-/me-, ps-/pe-, inset-s-/inset-e- (start-/end- before Tailwind 4.2), text-start, and rtl:-scale-x-100 on arrows and chevrons. Never ml-, pr-, left-, text-left.
  • Hover changes colour (fill, text, border), never size: no hover:scale-*, no zoom on photos.
  • A container separates by its fill. Borders belong on real edges and controls: inputs, table rules, dividers between siblings, outline buttons.
  • One radius per kind of thing: panels share one step, cards inside them share a smaller one.
  • Every link and button shows keyboard focus (focus-visible: ring or outline in a token colour). Never remove an outline without a replacement.
  • Visible text lives in the message files of every locale, never in JSX.
  • Keep the brand: same fonts, same accent, same imagery. Improve spacing, hierarchy and consistency first; they are most of the gain.

Check (after each section you change): run the checker with --against /tmp/design-before.json. It exits 1 if any count went up. Fix that before the next section.

4. Look at both themes and both directions

Open the page in light and dark, and in the RTL locale. Look for: text that vanished on one theme, a panel that stayed dark on the light page, arrows pointing the wrong way, anything that overflows sideways, numbers that broke out of their order. Check: four views (light/dark x LTR/RTL) with no horizontal scroll (document.documentElement.scrollWidth <= innerWidth) and nothing hidden.

5. Report

List the files and lines changed, the checker counts before and after, and the screenshots. Say what you did not change and why. Check: the type checker and the linter pass (tsc --noEmit, eslint on the changed files). </content> </invoke>

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.