frontend

Frontend rules for organizing React components, which are reusable pieces of a web interface. They cover component size, typed properties, composition, state ownership, and keeping display logic separate from data handling.

In plain words
What is it for?
They guide the creation of React components, shared UI modules, interactive elements, variant-based designs, and data flows between parent and child components.
Why use it?
They make frontend code easier to understand and maintain by limiting responsibilities and avoiding duplicated calculations or deeply passed properties.

Cursor rule for Claude Code

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/robinfaraj/one-context/frontend
Clone the repo
git clone --depth 1 https://github.com/robinfaraj/one-context

Made for: Claude Code.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 927 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.00927
Opus 5 $0.00000 $0.00464
Sonnet 5 $0.00000 $0.00185
Haiku 4.5 $0.00000 $0.00093

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

Security

Grade A, and why

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

.claude/skills/coding-style/references/frontend.mdc · 121 lines

How it starts

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

Frontend Patterns

Component Structure

  • Single responsibility, under 200 lines (refactor at 300+)
  • One component per file, props interface at top
  • Use unions for variants ("compact" | "default" not string)
  • Early returns for edge cases, logic before JSX
interface ComponentNameProps {
  variant: "compact" | "default";
  onAction: (value: string) => void;
}

export const ComponentName = ({ variant, onAction }: ComponentNameProps) => {
  if (variant === "compact") return <CompactView onAction={onAction} />;
  return <DefaultView onAction={onAction} />;
};

Naming: ComponentNameProps, ComponentNameConfig

Composition

  • Container/Presentational: Container handles state, passes to presentational children
  • Extract when: repeated in 2+ places, exceeds 30-40 lines, distinct responsibility
  • Parent computes, child displays: Don't recalculate derived values in children
  • Avoid prop drilling: Pass directly to consumers, not through intermediary wrappers
// ✅ Good: Parent calculates, child displays
const displayTime = useMemo(() => data?.naturalTime || data?.scheduledTime, [data]);
<Child displayTime={displayTime} />

// ❌ Bad: Child recalculates parent's work
const Child = ({ data }) => {
  const displayTime = data?.naturalTime || data?.scheduledTime; // Don't duplicate
}

Custom Hooks

Extract when the same useState + mutation pattern appears in 3+ components.

// hooks/[domain]/use[Domain][Action].ts
export function useManageDialog<T>(mutationFn: (item: T) => Promise<void>) {
  const [showDialog, setShowDialog] = useState(false);
  const [selectedItem, setSelectedItem] = useState<T | null>(null);

  const openDialog = (item: T) => { setSelectedItem(item); setShowDialog(true); };
  const closeDialog = () => { setShowDialog(false); setSelectedItem(null); };

  const handleConfirm = async () => {
    if (!selectedItem) return;
    await mutationFn(selectedItem);
    closeDialog();
  };

  return { showDialog, selectedItem, openDialog, closeDialog, handleConfirm };
}

Read the full file on GitHub · 121 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. yesterday First seen · 121 lines · 0 tokens per session scan A 0486987e3415

Subscribe to this mod's changes

frontend is a cursor rule published in the GitHub repository robinfaraj/one-context (43 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 927 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.