general

A set of coding rules for Wonder Blocks, a user-interface design system built with TypeScript and React. It describes naming, styling, testing, routing, and component conventions.

In plain words
What is it for?
Use it when building or reviewing Wonder Blocks components. It covers file names, exports, TypeScript types, React patterns, Aphrodite styling, tests, Storybook, and link behaviour.
Why use it?
It keeps new and changed interface code consistent with the project's established patterns. It also clarifies boundaries such as avoiding data fetching inside design-system components.

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/khan/wonder-blocks/general
Clone the repo
git clone --depth 1 https://github.com/Khan/wonder-blocks

Made for: Cursor.

Per session 5,190 This file is loaded in full into every session.
When invoked 5,190 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.05190 $0.05190
Opus 5 $0.02595 $0.02595
Sonnet 5 $0.01038 $0.01038
Haiku 4.5 $0.00519 $0.00519

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

Security

Grade A, and why

general 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/general.mdc · 386 lines

How it starts

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

Wonder Blocks Design System

Technology Stack

  • Language: TypeScript (Strict mode enforced).
  • Framework: React (Functional Components and Hooks are standard).
  • Styling: Aphrodite (aphrodite) for CSS-in-JS, leveraging Wonder Blocks tokens (@khanacademy/wonder-blocks-tokens) and themes.
  • State Management: Primarily local state (useState) and React Context API (useContext with custom provider hooks).
  • Data Fetching: There should be no data fetching in the design system UI components.
  • Routing: Design system components that have link functionality should also support React-Router routes.
  • Testing: Jest, React Testing Library (RTL), @testing-library/user-event, Storybook.

Coding Conventions & Style

1. File Naming

  • ✅ Use kebab-case for files and directories (e.g., activity-button.tsx, utils.ts)
  • ✅ Test files: *.test.ts(x)
  • ✅ Storybook files: *.stories.tsx

2. Export Naming

  • ✅ PascalCase for React components and TSX types/interfaces (e.g., Button, type ButtonProps)
  • ✅ camelCase for functions, variables, hooks (e.g., getButtonProps, useButtonFunctionality)

3. TypeScript

  • ✅ Use strict mode
  • ✅ Define clear interfaces/types (colocated or in types.ts). Use type for props and state, interface for shared structures where appropriate
  • ✅ Use utility types (Partial, Omit, Pick, Readonly, etc.)
  • ✅ Use the satisfies operator for type-safe object literals when you want both type checking and type inference
  • ✅ Prefer type-only imports where applicable: import type {...} for types
  • ❌ Avoid any; use unknown or specific types instead

4. React

  • ✅ Imports: Always use import * as React from "react" (required for JSX transformation)
  • ✅ Functional Components & Hooks: Use useState, useEffect, useContext, useCallback, useMemo, and custom hooks
  • ✅ Props: Define explicit Props types. Use object destructuring. Pass complex objects/callbacks with stable references (useCallback, useMemo) if they are dependencies of effects or memoized children
  • ✅ State: Keep component state minimal. Lift state up when necessary
  • ✅ Keys: Provide stable key props for lists (use item IDs if available)
  • ✅ Composition: Build complex UI by composing smaller Wonder Blocks when possible
  • ✅ Refs: Use React.forwardRef when components need to expose DOM refs
  • ✅ Custom Hooks: Extract reusable logic into custom hooks (e.g., useFieldValidation, useIsMounted from @khanacademy/wonder-blocks-core)
  • ✅ Event Handlers: Internal handlers should be prefixed with handle (e.g., handleClick, handleChange). Callback props should be prefixed with on (e.g., onClick, onChange)
  • ❌ Don't use React.FC<Props> when defining functional components, use (props: Props) => instead
  • ❌ Avoid creating new class components. Refactor existing ones if making significant changes

Read the full file on GitHub · 386 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. 2d ago First seen · 386 lines · 5,190 tokens per session scan A ae2b2cf96384

Subscribe to this mod's changes

general is a cursor rule published in the GitHub repository Khan/wonder-blocks (163 stars, last pushed 4d ago), licensed MIT. It adds 5,190 tokens to every session, about $0.0260 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.