component-architecture

A codebase rule for organising a React and Next.js website into reusable components, with separate files for code, styles, data queries, and tests where needed.

In plain words
What is it for?
Use it when adding, testing, or reorganising layout, form, button, dialog, toast, and other website components.
Why use it?
It gives developers a consistent place to find and maintain each part of the interface.

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/thematters/matters-web/component-architecture
Clone the repo
git clone --depth 1 https://github.com/thematters/matters-web

Made for: Cursor.

Per session 281 This file is loaded in full into every session.
When invoked 281 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.00281 $0.00281
Opus 5 $0.00140 $0.00140
Sonnet 5 $0.00056 $0.00056
Haiku 4.5 $0.00028 $0.00028

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

Security

Grade A, and why

component-architecture 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.

.cursor/rules/component-architecture.mdc · 35 lines

What it actually says

Component Architecture

Matters Web follows a component-based architecture using React and Next.js.

Component Organization

Reusable components are organized in the src/components/ directory, each in its own folder with the following structure:

ComponentName/
  ├── index.tsx              # Main component export
  ├── styles.module.css      # Component styles
  ├── gql.ts                 # GraphQL queries/mutations (if needed)
  └── ComponentName.test.tsx # Component tests

Component Types

  • UI Components: Pure presentational components
  • Compositions Components: Components that are built on top of other UI components and may include GraphQL fragments as part of their UI requirements

Key Component Directories

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. 2d ago First seen · 35 lines · 281 tokens per session scan A f61e4ed9329b

Subscribe to this mod's changes

component-architecture is a cursor rule published in the GitHub repository thematters/matters-web (86 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 281 tokens to every session, about $0.0014 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-30.