ui-components

ui-components is a cursor rule for Cursor from jaycewalzer1/SilverKey-Inc.. It costs 0 tokens per session (2,803 once invoked), scanned A, original, MIT.

A set of rules requiring user interfaces to use standardized components from the project's ui/ directory.

In plain words
What is it for?
Use it when adding or changing interface elements so they follow the project's shared component library.
Why use it?
It prevents different parts of an application from rebuilding the same interface elements in inconsistent ways.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { Button } from "../ui";.

Good fit Use it when adding or changing interface elements so they follow the project's shared component library.

Compare 6 cursor rules from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/jaycewalzer1/SilverKey-Inc.
agentmods
npx agentmods add rules/jaycewalzer1/silverkey-inc./ui-components

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ui-components

README.md
[![agentmods](https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./ui-components/github.svg)](https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./ui-components)
Your own site
<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./ui-components"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./ui-components/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ui-components

Your own site · 80×15
<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./ui-components"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./ui-components.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,803 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02803
Opus 5.5 $0.00000 $0.01121
Sonnet 5.5 $0.00000 $0.00561
Haiku 4.5 $0.00000 $0.00280

Measured 1mo ago against content hash 53736f02e295, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.cursor/rules/frontend/ui-components.mdc · 290 lines

How it starts

The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UI Component Standardization Rules

Overview

All UI components (buttons, text, forms) MUST use standardized components from Client/packages/ui/ (import via packages/ui, @/components/ui, or @ui per Client/tsconfig.base.json). Custom implementations are FORBIDDEN unless explicitly approved.

Standardized Components

Layout Primitives (Box / View)

  • Use a unified layout primitive (e.g. Box or View) for block-level layout instead of raw <div> or framework-specific containers. <div> (block) vs RN <View> (flex column by default) is a major source of layout bugs when sharing or migrating code.
  • Rule: Prefer a shared Box (or equivalent) that standardizes flex defaults and behavior across web and (when present) React Native, so one mental model applies and moving folders does not break layout.

Buttons

Location: Client/packages/ui/components/button/

Available Components:

  • Button - Main button component with variants (primary, secondary, outline, ghost, danger, success, warning, cancel)
  • CancelButton - Standardized cancel button (wrapper around Button with outline/ghost variant)
  • CloseButton - Standardized close button with X icon (for modals/dialogs)
  • IconButton - Icon-only buttons
  • CircularButton - Circular button variant
  • NavigationButton - Link-like navigation buttons
  • NavigationButtons - Navigation button groups
  • RefreshButton - Specialized refresh button

Rules:

  • ❌ NEVER create custom <button> elements with inline className styles
  • ❌ NEVER use raw button elements with custom padding, colors, or hover states
  • ✅ ALWAYS use Button component for standard buttons
  • ✅ ALWAYS use CancelButton for cancel actions
  • ✅ ALWAYS use CloseButton for closing modals/dialogs
  • ✅ ALWAYS use IconButton for icon-only buttons
  • ✅ ALWAYS import from packages/ui (barrel), @/components/ui, or @ui — not ad-hoc paths under apps/web

Examples:

// ❌ WRONG: Custom button implementation
<button
  onClick={handleClick}
  className="px-4 py-2 bg-blue-500 text-white rounded hover:bg-blue-600"
>
  Click me
</button>

// ✅ CORRECT: Use Button component
import { Button } from "../ui";

<Button variant="primary" size="md" onClick={handleClick}>
  Click me
</Button>

// ❌ WRONG: Custom cancel button
<button
  onClick={onCancel}
  className="px-4 py-2 border border-gray-300 bg-white rounded hover:bg-gray-50"
>
  Cancel
</button>

// ✅ CORRECT: Use CancelButton
import { CancelButton } from "../ui";

<CancelButton onClick={onCancel} size="md">
  Cancel
</CancelButton>

// ❌ WRONG: Custom close button
<button onClick={onClose} className="absolute right-2 top-2 text-gray-400">
  <X className="w-5 h-5" />
</button>

// ✅ CORRECT: Use CloseButton
import { CloseButton } from "../ui";

<CloseButton onClick={onClose} size="sm" className="absolute right-2 top-2" />

Read the full file on GitHub · 290 lines

Changes

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.

  1. 1mo ago First seen · 290 lines · 0 tokens per session scan A 53736f02e295

Subscribe to this mod's changes

ui-components is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,803 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-31.