components

Guidelines for building interface components, including a preference for Shadcn, atomic design, and matching Figma designs.

In plain words
What is it for?
Use them when creating or changing reusable user-interface components and checking whether they match Figma designs.
Why use it?
They give component work a consistent structure and help keep the implementation aligned with the design.

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/pubky/pubky-app/components
Clone the repo
git clone --depth 1 https://github.com/pubky/pubky-app

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 41 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00041
Opus 5 $0.00000 $0.00020
Sonnet 5 $0.00000 $0.00008
Haiku 4.5 $0.00000 $0.00004

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

Security

Grade A, and why

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 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/components.mdc · 10 lines

What it actually says

Component Rules

@docs/components.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.

  1. 2d ago First seen · 10 lines · 0 tokens per session scan A fd9078de053a

Subscribe to this mod's changes

components is a cursor rule published in the GitHub repository pubky/pubky-app (23 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 41 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.