What is component-structure?

A set of rules for organising each interface component into its own folder, with separate files for its types, fixed values, tests, and optional helper parts.

Use it when creating or restructuring components, features, reusable interface pieces, tests, constants, and accessibility-focused controls.

It keeps component files focused and makes related code easy to find without creating unnecessary files.

component-structure — Cursor rule for Cursor by ddebixx

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.

Clone the repo

git clone --depth 1 https://github.com/ddebixx/frontend-template

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/ddebixx/frontend-template/component-structure/github.svg)](https://agentmods.dev/rules/ddebixx/frontend-template/component-structure)

Your own site

<a href="https://agentmods.dev/rules/ddebixx/frontend-template/component-structure"><img src="https://agentmods.dev/badge/rules/ddebixx/frontend-template/component-structure/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/ddebixx/frontend-template/component-structure"><img src="https://agentmods.dev/badge/rules/ddebixx/frontend-template/component-structure.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 233 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00233
Opus 5.5	$0.00000	$0.00093
Sonnet 5.5	$0.00000	$0.00047
Haiku 4.5	$0.00000	$0.00023

Measured 25d ago against content hash 5128b2a66610, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

component-structure 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 25d 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/component-structure.mdc · 27 lines

What it actually says

Components

Encapsulate component-only types, utils, and constants inside the component folder.
Keep ComponentName.tsx UI-only. Export types from ComponentName.types.ts and constants from ComponentName.constants.ts.
Create sibling files only when they have content.
Nest subcomponents so the folder tree mirrors the UI tree.
Use the same layout under src/features/.
Keep presentational UI in components/. Compose UI and wire data in features/.

ComponentName/
  ComponentName.tsx
  ComponentName.types.ts
  ComponentName.constants.ts   # omit if none
  ComponentName.test.ts
  utils/                       # optional
  SubComponent/                # optional

Details: docs/frontend/conventions/COMPONENT_STRUCTURE.md

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.

25d ago Changed · -2 lines 5128b2a66610
2mo ago First seen · 29 lines · 0 tokens per session scan A 55120b41d2c4

Subscribe to this mod's changes

component-structure is a cursor rule published in the GitHub repository ddebixx/frontend-template (5 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 233 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.

component-structure next to 6 cursor rules from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
component-structureddebixx/frontend-template	Cursor rule	5	26d ago	MIT	A	0	Cursor
ponytailDietrichGebert/ponytail	Cursor rule	186k	9d ago	MIT	A	604	Cursor
angular-20angular/angular	Cursor rule	101k	today	MIT	A	0	Cursor
dev-standardapache/superset	Cursor rule	75k	today	Apache-2.0	A	1,147	Cursor
prefer-direct-imports-over-module-mocksprisma/orm	Cursor rule	48k	yesterday	Apache-2.0	A	0	Cursor
config-validation-and-normalizationprisma/orm	Cursor rule	48k	yesterday	Apache-2.0	A	0	Cursor
control-plane-descriptorsprisma/orm	Cursor rule	48k	yesterday	Apache-2.0	A	0	Cursor