agentleFS
shashidharbabushashidharbabu/rocketride-design-skills/skills/arc-ui/SKILL.md

arc-ui

Skill0 starsChanged 2 days agoLicence not identifiedView on GitHub

Install and integrate Arc (uiarc.dev, "Arc UI") — Elia Kuratli's agent-oriented React library of 112 free MIT components + 22 free blocks (56 components / 72 blocks more behind Arc Pro, $129/yr or $199 lifetime), distributed as copy-in source through a shadcn registry (`@uiarc/<id>` → https://uiarc.dev/r/{name}.json) and styled with CSS Modules + its own oklch CSS-variable token layer (not Tailwind classes), animated with `motion/react` — into Next.js 14–16, React 18–19, Tailwind v3.4 or v4 repos, alone or beside shadcn/ui. Use this whenever a task mentions uiarc, uiarc.dev, Arc UI, an `@uiarc/` or `@uiarc-pro/` install, `components/arc/foundation.css` or `@/components/arc/...` imports; whenever an app wants a calm, neutral, Linear-like product UI base as an alternative to shadcn; or whenever it needs a finished product-UI interaction piece — confirm-in-place / hold-to-confirm / morphing delete button, sliding segmented control, KPI metric cards with rolling numbers, icon morph, expanding button group, swipe row actions, ridgeline / streamgraph / waffle / slope / treemap charts, or settings / pricing / dashboard / sign-in blocks with motion. Also use it before letting Arc's own vendor skill near a repo (don't — see below). Install pre-flight, the token-collision bridge with shadcn, and every verified fix live in references/integration.md.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.