wonder-blocks frontend-rules.instructions.md

wonder-blocks frontend-rules.instructions.md is an instructions file for GitHub Copilot from Khan/wonder-blocks. It costs 3,560 tokens per session, scanned A, original, MIT.

Frontend coding rules for building Wonder Blocks, Khan Academy’s interface component library, with React and TypeScript.

In plain words
What is it for?
Use them when creating or changing Wonder Blocks components, hooks, styles, links, tests, or Storybook examples.
Why use it?
They keep components consistent and make naming, styling, testing, and data-handling decisions predictable across the design system.

Instructions file for GitHub Copilot

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

Made for: GitHub Copilot.

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.

agentmods badge for wonder-blocks frontend-rules.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/khan/wonder-blocks/frontend-rules.svg)](https://agentmods.dev/instructions/khan/wonder-blocks/frontend-rules)
Your own site
<a href="https://agentmods.dev/instructions/khan/wonder-blocks/frontend-rules"><img src="https://agentmods.dev/badge/instructions/khan/wonder-blocks/frontend-rules.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,560 This file is loaded in full into every session.
When invoked 3,560 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.03560 $0.03560
Opus 5 $0.01780 $0.01780
Sonnet 5 $0.00712 $0.00712
Haiku 4.5 $0.00356 $0.00356

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

Security

Grade A, and why

wonder-blocks frontend-rules.instructions.md 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 3d 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.

.github/instructions/frontend-rules.instructions.md · 311 lines

How it starts

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

Wonder Blocks Design System - Frontend Rules

This file provides frontend development instructions for the Wonder Blocks design system.

Technology Stack

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

Coding Conventions

File & Export Naming

  • Use kebab-case for files and directories (e.g., activity-button.tsx, utils.ts)
  • Test files: *.test.ts(x)
  • Storybook files: *.stories.tsx
  • PascalCase for React components and types (e.g., Button, type ButtonProps)
  • camelCase for functions, variables, hooks (e.g., getButtonProps, useButtonFunctionality)

TypeScript

  • Use strict mode
  • Define clear interfaces/types. 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
  • Prefer type-only imports: import type {...} for types
  • Avoid any; use unknown or specific types instead

React

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

Read the full file on GitHub · 311 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. 3d ago First seen · 311 lines · 3,560 tokens per session scan A f15e791bd5c4

Subscribe to this mod's changes

wonder-blocks frontend-rules.instructions.md is an instructions file published in the GitHub repository Khan/wonder-blocks (163 stars, last pushed 5d ago), licensed MIT. It adds 3,560 tokens to every session, about $0.0178 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.