copilot-instructions react.instructions.md

A set of instructions for building React applications, which are web interfaces made from reusable components. It covers component structure, TypeScript, hooks, naming, testing, and other development conventions.

In plain words
What is it for?
Use it to guide the structure and implementation of React components, including file placement, naming, exports, composition, and TypeScript-based props.
Why use it?
It gives developers and Copilot a shared set of rules, making React code more consistent and easier to maintain.

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/pplancq/copilot-instructions/react
Clone the repo
git clone --depth 1 https://github.com/pplancq/copilot-instructions

Made for: GitHub Copilot.

Per session 2,395 This file is loaded in full into every session.
When invoked 2,395 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.02395 $0.02395
Opus 5 $0.01197 $0.01197
Sonnet 5 $0.00479 $0.00479
Haiku 4.5 $0.00239 $0.00239

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

Security

Grade A, and why

copilot-instructions react.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 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.

.github/instructions/react.instructions.md · 374 lines

How it starts

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

React Development Instructions

Instructions for building high-quality React applications with modern patterns, hooks, and best practices following the official React documentation at https://react.dev.

Project Context

  • Latest React version (React 19+)
  • TypeScript for type safety
  • Functional components with hooks as default
  • Follow React's official style guide and best practices
  • Use modern build tools (Vite, Create React App, or custom Webpack setup)
  • Implement proper component composition and reusability patterns

Component Architecture

Naming and Structure Convention

  • Components must always be placed in a folder/file <ComponentName>/<ComponentName>.tsx.

  • Only one React component should be declared per file.

  • The component name must be in PascalCase.

  • The component must be a function, preferably an arrow function.

  • The component must be exported at the declaration:

    export const MyComponent = () => {};
    

Component Design

  • Follow the single responsibility principle for components.
  • Use descriptive and consistent naming conventions.
  • Implement proper prop validation with TypeScript.
  • Design components to be testable and reusable.
  • Keep components small and focused on a single concern.
  • Use composition patterns (render props, children as functions).
  • Organize components by feature or domain for scalability.
  • Separate presentational and container components clearly.
  • Implement proper component hierarchies with clear data flow.

Development Principles

  • Follow SOLID, DRY, KISS principles.
  • Prefer code simplicity and clarity.
  • Factorize common code.
  • Do not declare more than one React component per file (react/no-multi-comp).
  • Do not use conditional rendering that could cause leaked renders (react/jsx-no-leaked-render).
  • Follow the react/function-component-definition rule: always declare components as arrow functions.
  • Implement component composition over inheritance.

TypeScript and Typing

Read the full file on GitHub · 374 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 · 374 lines · 2,395 tokens per session scan A db2ee3f047b4

Subscribe to this mod's changes

copilot-instructions react.instructions.md is an instructions file published in the GitHub repository pplancq/copilot-instructions (4 stars, last pushed 7mo ago), licensed MIT. It adds 2,395 tokens to every session, about $0.0120 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-31.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens