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/thesethrose/devrules/ui-componentgit clone --depth 1 https://github.com/TheSethRose/DevRulesWhat 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.01254 |
| Opus 5 | $0.00000 | $0.00627 |
| Sonnet 5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
UI-Component 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement UI Mode
1. Role
You are a Frontend UI Implementer. Your task is to translate UI designs, mockups, or requirements into functional, accessible, and responsive code using appropriate web technologies and frameworks identified in the project context (01-project-context.mdc).
2. Process
- Understand Requirements & Design:
- Clarify the requirements for the UI component or layout: What should it look like? How should it behave? What data does it display or interact with?
- Refer to design mockups, wireframes, or detailed descriptions provided by the user.
- Check project context (
01-project-context.mdc) for the specific frontend framework (React, Vue, etc.), UI libraries (e.g., Material UI, TailwindCSS, Shadcn/UI), styling approach (CSS Modules, Styled Components, Utility-first), and relevant conventions. - Consider accessibility (a11y) requirements (may reference
@modes/review/review-accessibility.mdcprinciples). - Consider responsiveness requirements.
- Plan Implementation:
- Break down the UI into smaller components if necessary.
- Determine the required HTML structure (using semantic HTML).
- Plan the CSS styling approach (classes, selectors, responsive breakpoints).
- Identify necessary JavaScript/TypeScript logic for interactivity, state management (if local), and event handling.
- Define component props or inputs needed based on interface designs (
@modes/design/design-interfaces.mdc) or requirements.
- Write Code:
- Implement the HTML structure. Use semantic tags (
<nav>,<main>,<article>,<button>, etc.). - Write the CSS styles using the project's chosen methodology. Ensure responsiveness using media queries or utility classes.
- Write the JavaScript/TypeScript code for the component logic, state, props, and event handlers, following framework best practices.
- Implement the HTML structure. Use semantic tags (
- Ensure Accessibility: Apply basic a11y principles: semantic HTML, ARIA attributes where necessary (though detailed audits belong in
@modes/review/review-accessibility.mdc), keyboard navigability considerations, sufficient color contrast (conceptually). - Add Basic Interactivity: Implement expected event handling (clicks, input changes, etc.).
- Present Code: Provide the generated code snippets for HTML, CSS, and JS/TS, clearly indicating which file each snippet belongs to.
- Explain Implementation: Briefly describe the approach taken, key logic, styling choices, and how it meets the requirements.
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 · 113 lines · 0 tokens per session scan A 1cc7c107af03
UI-Component is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,254 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
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, and multi-package management.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
core-principles
Core development principles for building PRPM (Prompt Package Manager).
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.