agentleFS
ZethRiseZethRise/ReadyDesign-Skill/SKILL.md

readydesign-skill

Skill14 starsChanged 3 months agoMITView on GitHub

Force UI work onto six ready-to-use libraries only: shadcn/ui, Ant Design, Kokonut UI, Motion (motion.dev), Bklit (bklit.com), and sashimi UI. Web-fetch each official site one-by-one and install the real components from those pages — never invent APIs, class names, colors, or components from memory. Use when building or restyling a UI, scaffolding a frontend, adding components, picking a design system, or when the user says ReadyDesign, ready-to-use components, shadcn, antd, kokonut, motion.dev, framer motion, bklit, sashimi, or runs /readydesign-skill or $readydesign-skill.

  • Installs packages

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. About 0 are common, 15 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Do not write UI until the fetches for this session have started.

    line 53
  2. Distinctive:

    Ask the required user questions (below).

    line 61
  3. Distinctive:

    If a fetch fails: retry that same URL once.

    line 68
  4. Very specific:

    If a catalog HTML page returns almost no content, fetch that source's markdown / llms.txt / .md docs URL instead (shadcn: …

    line 71
  5. Very specific:

    Do not put two primitive kits on the same control (no antd Button wrapped in a shadcn Button).

    line 87
  6. Distinctive:

    If the project is new and the user did not give a design, brand palette, or token file:

    line 93
  7. Distinctive:

    Keep each installed component's original colors, tokens, and theme CSS exactly as the official source ships them.

    line 96
  8. Distinctive:

    Do not change a hex, hsl, oklch, shade, radius, or shadow "to match."

    line 98
  9. Distinctive:

    Do not invent a custom palette.

    line 99
  10. Distinctive:

    If the user did give a design, apply their tokens and still use only these six sources.

    line 101
  11. Distinctive:

    Do not dump a questionnaire up front.

    line 106
  12. Distinctive:

    Should I use animations and motion on every place and action, or only on key interactions?

    line 110
  13. Distinctive:

    Do you have a brand/design, or should I keep each library's original colors untouched?

    line 114
  14. Distinctive:

    After the component page is fetched:

    line 122
  15. Distinctive:

    Do not hand-write a stand-in that "looks like" a library component.

    line 136
  16. Distinctive:

    If the official component exists, add it.

    line 137
  17. Distinctive:

    Every UI import in the change must map to a URL fetched in this session.

    line 141
  18. Distinctive:

    If you cannot point at that fetch, fetch it now or remove the import.

    line 142

≈ “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

ReadyDesign

UI may come only from these six official sources. Fetch their live docs one-by-one and install what those pages actually ship. Memory, training data, and "shadcn-like" custom rebuilds are not allowed.

Allowed sources

Fetch these pages. Do not substitute blogs, YouTube, or memory.

SourceUse forCatalog / start hereThen open
shadcn/uiApp primitives: button, form, dialog, table, sidebarhttps://ui.shadcn.com/llms.txthttps://ui.shadcn.com/docs/components and the component URL listed there
Ant DesignEnterprise / data-dense controlshttps://ant.design/components/overviewhttps://ant.design/components/`<name> or https://ant.design/components/<name>`.md
Kokonut UIDecorative / marketing sections, animated extrashttps://kokonutui.com/docsThe component page you will install from
MotionAll animation and gesture motionhttps://motion.dev/docs/reactThe specific guide (animation, gestures, layout, presence) plus https://motion.dev/examples
BklitCharts and data visualizationhttps://bklit.com/docs/componentshttps://bklit.com/docs/installation then the chart page you will add
sashimi UINative HTML/CSS, no-JS chromehttps://yuto-hasegawa.github.io/sashimi-ui/https://yuto-hasegawa.github.io/sashimi-ui/getting-started/

Agent extras, fetch when that source is in play:

Nothing else is a UI source. MUI, Chakra, Mantine, DaisyUI, Bootstrap, Flowbite, Magic UI, Aceternity, HeroUI, Radix Themes, GSAP, anime.js, Recharts/Tremor/Chart.js used directly, and handmade "inspired by" components are banned.

Fetch protocol (do this, in this order)

Do not write UI until the fetches for this session have started. Fetch one URL at a time with the host's page-fetch tool (WebFetch, web_fetch, open_page, curl, or equivalent). Never batch catalog fetches. Never skip a source because you "already know it." Search snippets are not a substitute for the official page.

  1. Fetch all six catalog / start-here URLs from the table, one after another. Record the real component names each page lists.
  2. Ask the required user questions (below). Use the answers to decide which sources you will actually install from.
  3. For every component you will add, fetch that component's official page (or its registry JSON) before you install or paste it.
  4. Install or copy using only the command, import path, and API shown on the page you just fetched. If the page and your memory disagree, the page wins.
  5. If a fetch fails: retry that same URL once. If it still fails, stop and tell the user which URL died. Do not invent the missing component.

If a catalog HTML page returns almost no content, fetch that source's markdown / llms.txt / .md docs URL instead (shadcn: https://ui.shadcn.com/llms.txt; antd: https://ant.design/components/`<name>`.md).

Pick a source

NeedSource
Charts, gauges, heatmaps, funnels, analyticsBklit
Motion, hover/tap, layout, exit, scroll animationMotion (motion/react)
Buttons, inputs, dialogs, tables, sidebars, toastsshadcn/ui
Heavy enterprise forms, dense admin, antd-only widgetsAnt Design
Hero treatments, particle buttons, decorative blocksKokonut UI
Semantic native HTML / CSS-only controlssashimi UI

Do not put two primitive kits on the same control (no antd Button wrapped in a shadcn Button). You may compose: shadcn/antd/sashimi structure + Kokonut decoration + Motion motion + Bklit charts.

Color lock

If the project is new and the user did not give a design, brand palette, or token file:

  • Keep each installed component's original colors, tokens, and theme CSS exactly as the official source ships them.
  • Do not change a hex, hsl, oklch, shade, radius, or shadow "to match."
  • Do not invent a custom palette. Do not restyle defaults.

If the user did give a design, apply their tokens and still use only these six sources.

Ask the user (2–4 times while working)

Do not dump a questionnaire up front. Ask 2 to 4 of these as real decisions come up. Wait for the answer before that part of the UI.

  • Are there any analysing charts?
  • Should I use animations and motion on every place and action, or only on key interactions?
  • Is this a marketing/landing surface, an app shell, or a data-dense admin?
  • Do you have a brand/design, or should I keep each library's original colors untouched?
  • Any forms that need heavy validation, dates, uploads, or steppers?

Skip a question only when the user already answered it in this thread.

Add the real thing

After the component page is fetched:

Do not hand-write a stand-in that "looks like" a library component. If the official component exists, add it.

Before you finish

Every UI import in the change must map to a URL fetched in this session. If you cannot point at that fetch, fetch it now or remove the import.

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.