Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/virastack/ai/ui-componentsgit clone --depth 1 https://github.com/virastack/aiWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.01012 |
| Opus 5 | $0.00000 | $0.00506 |
| Sonnet 5 | $0.00000 | $0.00202 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
ui-components scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Components
Constraints
- Hierarchy: Organize by
ui(stateless),shared(common), andfeature(domain logic). - Atomic: Keep
src/components/uipure; forbid API/Store dependencies. - Separation: Separate data (container) from UI (presentation).
- Composition: Prefer children-based composition over large prop objects.
- States: Implement Skeleton (matching dimensions), EmptyState, and ErrorState for data-driven parts.
- UX: Avoid empty screens; always provide meaningful states.
- Styling: Use Tailwind CSS,
cn(), and Design Tokens. No Hex/RGB or arbitrary values (use Tailwind scale strictly). When writing Tailwind CSS, always use v4 syntax and canonical classes (e.g., usebg-linear-to-*instead ofbg-gradient-to-*,size-*instead ofw-* h-*). - Primitive Components: Build primitive UI components (Button, Dialog, etc.) in
src/components/ui.- CRITICAL CHECK: Check
package.jsonfor UI primitives. - If
@radix-ui/*is installed, use Radix UI primitives. - If
@base-ui/reactis installed, use Base UI primitives. - If neither is installed, build accessible native HTML elements.
- CRITICAL CHECK: Check
- A11y: Enforce semantic HTML,
ariaattributes, and keyboard accessibility. - Typography: One
h1per page. Do not skip heading levels. Do not use heading styles for non-heading content. - Responsive: Mobile-first from 320px. Use and verify at Tailwind defaults: sm 640, md 768, lg 1024, xl 1280.
- Focus: Overlays/dialogs must move focus inside on open and restore it on close. Prefer Radix/Base UI primitives for focus trap; never invent a custom trap when a primitive is available.
- Exports: Use Named exports only.
Bans
- AI Aesthetic: Default purple/indigo palettes, excessive gradients, overuse of
rounded-2xl, generic card/grid layouts. - Magic Numbers: Arbitrary values (e.g.,
p-[13px]); use Tailwind’s spacing scale strictly. - UX/A11y:
divsoup, "Lorem Ipsum", oronClickon non-interactive elements without keyboard support. - Logic: Default exports or data fetching inside atomic components.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 88 lines · 0 tokens per session scan A c893e9183e8a
ui-components is a cursor rule published in the GitHub repository virastack/ai (23 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,012 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
marker-triage
Triage a Marker.io website-feedback backlog at scale. Use when asked to go through, categorize, prioritize, deduplicate, or make sense of many Marker.io issues at once. Splits content fixes from functional bugs, groups by page, rates criticality, flags duplicates and repeat reporters, surfaces quick wins, lists…
marker-client-report
Turn a project's completed Marker.io work into a client-ready report. Use when asked to write a weekly or monthly recap for a client, summarize what was shipped or fixed this period, or produce a status update for a website project from Marker.io. Read-only: it reads issues and writes a markdown report, it does not…
marker-insights
Aggregate Marker.io website feedback into recurring patterns. Use when asked to find the most common issues on a site, which pages get the most feedback, recurring content problems, or the content-vs-bug split across many Marker.io reports, and produce a prioritized brief for a website team or agency. Read-only: it…
marker-bug-to-fix
Take one Marker.io bug report and produce a ready-to-review code fix. Use when asked to fix, investigate, reproduce, or find the root cause of a specific Marker.io issue in the current repository. Pulls the issue's screenshot, console errors, network requests and DOM, locates the cause in code, proposes a minimal…
marker-sync
Keep Marker.io and your issue tracker (GitHub, Linear, Jira) in sync. Use when asked to pull new Marker.io issues into a tracker, enrich tracker tickets with Marker context, mark issues resolved or ready-to-test in both places, or reconcile status mismatches between Marker.io and the tracker.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.