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

gauge-ui

Skill0 starsChanged 2 days agoLicence not identifiedView on GitHub

Install and integrate gauge-ui (gauge-ui.dev): MIT-licensed, free, composable SVG gauge primitives for React by Thordur (github.com/thordursk/gauge-ui). It covers speedometers, dials, meters, ring/donut progress, tick-fill bars, compass and clock faces, low–high range gauges, nested dials and draggable knob/slider gauges. It ships as one copy-in shadcn registry item (`npx shadcn@latest add https://gauge-ui.dev/r/gauge.json`, or `@gauge-ui/gauge` via a components.json namespace) with zero npm deps and its own spring/tween engine (no motion or framer-motion). Caveats: it requires React 19.2+, because `tooltip.tsx` imports `useEffectEvent`, so React 18 and 19.0/19.1 fail the build. On React 18 / Tailwind v3 it needs two fixes, both in references/integration.md: a useEffectEvent shim and token colours that match the repo's token format, including the dot halo (install with `shadcn@latest add` even on v3). Display gauges carry no ARIA, so you add role="meter" yourself. Use this whenever a task involves gauge-ui.dev or an @gauge-ui install, a gauge, speedometer, tachometer, dial, meter, radial or ring progress, capacity or redline indicator, compass/heading or time-of-day dial, an SLO/target-range dial, a rotary knob or circular slider, or a system-monitor / pipeline-health dashboard (RocketRide pipeline monitoring). Also use it to decide whether a dial is the right form at all; defer that judgment and all colour choices to the dataviz skill.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    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.