ui_component_patterns

A rule that checks whether UI component files and folders follow a consistent structure and PascalCase naming, such as Button.tsx or UserProfile.

In plain words
What is it for?
Use it to validate paths and naming for simple and nested UI components.
Why use it?
It catches inconsistent component organization and names before they spread through a codebase.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/gitmaxd/ai-init/ui_component_patterns
Clone the repo
git clone --depth 1 https://github.com/Gitmaxd/ai-init

Made for: Cursor.

Per session 305 This file is loaded in full into every session.
When invoked 305 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00305 $0.00305
Opus 5 $0.00152 $0.00152
Sonnet 5 $0.00061 $0.00061
Haiku 4.5 $0.00030 $0.00030

Measured yesterday against content hash ce15d24352f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ui_component_patterns 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 yesterday.

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.

lib/templates/next/.cursor/rules/ui_component_patterns.mdc · 39 lines

What it actually says

  Example component structure:
  ```
  src/components/
  ├── Button.tsx         # Basic UI component
  ├── UserProfile/       # Complex component with subcomponents
  │   ├── index.tsx      # Main component export
  │   ├── ProfileImage.tsx
  │   └── UserDetails.tsx
  └── Layout/
      ├── index.tsx
      └── Header.tsx
  ```

examples:

  • input: "src/components/Button.tsx" output: "Valid: PascalCase for component file"
  • input: "src/components/user-profile.tsx" output: "Invalid: Should use PascalCase (UserProfile.tsx)"
  • input: "components/UserProfile.tsx" output: "Valid: Correctly uses PascalCase" metadata: priority: medium version: 1.1
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. yesterday First seen · 39 lines · 305 tokens per session scan A ce15d24352f2

Subscribe to this mod's changes

ui_component_patterns is a cursor rule published in the GitHub repository Gitmaxd/ai-init (8 stars, last pushed 1y ago), licensed MIT. It adds 305 tokens to every session, about $0.0015 per session on Opus 5. 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.