loadout: Instructions file for GitHub Copilot

.github/instructions/reactjs.instructions.md

loadout reactjs.instructions.md is an instructions file for GitHub Copilot from stefaniuk/loadout. It costs 3,448 tokens per session, scanned A, original, MIT.

Engineering guidance for building React applications with modern function-based components and hooks. React is a library for creating interactive user interfaces from reusable components.

In plain words
What is it for?
Use it when creating or changing React pages, reusable components, hooks, state management, or responsive interfaces.
Why use it?
It helps keep React components, application state, and browser or server rendering patterns consistent.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is stefaniuk/loadout's own configuration. It tells GitHub Copilot how to work on loadout itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything loadout configures →

Reuse

Borrowing it

Nothing to install: this file belongs to stefaniuk/loadout. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/stefaniuk/loadout/main/.github/instructions/reactjs.instructions.md
Clone the repo
git clone --depth 1 https://github.com/stefaniuk/loadout

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 loadout reactjs.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/stefaniuk/loadout/reactjs/github.svg)](https://agentmods.dev/instructions/stefaniuk/loadout/reactjs)
Your own site
<a href="https://agentmods.dev/instructions/stefaniuk/loadout/reactjs"><img src="https://agentmods.dev/badge/instructions/stefaniuk/loadout/reactjs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for loadout reactjs.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/stefaniuk/loadout/reactjs"><img src="https://agentmods.dev/badge/instructions/stefaniuk/loadout/reactjs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,448 This file is loaded in full into every session.
When invoked 3,448 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.03448 $0.03448
Opus 5.5 $0.01379 $0.01379
Sonnet 5.5 $0.00690 $0.00690
Haiku 4.5 $0.00345 $0.00345

Measured 1mo ago against content hash 0cd87df1e672, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

loadout reactjs.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 1mo 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/reactjs.instructions.md · 222 lines

How it starts

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

ReactJS Engineering Instructions ⚛️

These instructions define React-specific patterns for building high-quality applications with modern hooks and component architecture.

They must remain applicable to:

  • React 19+ functional components with hooks
  • Single Page Applications (SPA) and Server-Side Rendering (SSR)
  • Component libraries and design systems
  • Mobile-responsive web applications

For general language and tooling guidance, defer to:

This file covers only what that file does not: React component design, hooks patterns, state management, and UI-specific concerns.

They are non-negotiable unless an exception is explicitly documented (with rationale and expiry) in an ADR/decision record.

Identifier scheme. Every normative rule carries a unique tag in the form [RJS-<prefix>-NNN], where the prefix maps to the containing section (for example QR for Quick Reference, CMP for Component Design, HK for Hooks, STM for State Management). Use these identifiers when referencing, planning, or validating requirements.


0. Quick reference (apply first) 🧠

This section exists so humans and AI assistants can reliably apply the most important rules even when context is tight.

  • [RJS-QR-001] Functional components only: no class components; use hooks for all stateful logic ([RJS-CMP-001]).
  • [RJS-QR-002] Component size limit: split components exceeding ~150 lines or 3 responsibilities ([RJS-CMP-003]).
  • [RJS-QR-003] Hooks at top level: never call hooks inside loops, conditions, or nested functions ([RJS-HK-001]).
  • [RJS-QR-004] Exhaustive deps: include all referenced values in dependency arrays; use ESLint rule ([RJS-HK-002]).
  • [RJS-QR-005] Cleanup effects: return cleanup functions from effects that subscribe, listen, or allocate ([RJS-HK-004]).
  • [RJS-QR-006] Props as interface: define props as a TypeScript interface (not type alias); avoid React.FC ([RJS-CMP-005]).
  • [RJS-QR-007] Error boundaries: wrap feature boundaries with Error Boundaries; provide fallback UI ([RJS-ERR-001]).
  • [RJS-QR-008] Semantic HTML first: use native elements before ARIA; <button> not <div onClick> ([RJS-A11Y-001]).
  • [RJS-QR-009] No inline object/array props: define outside render or memoize to prevent child re-renders ([RJS-PERF-001]).
  • [RJS-QR-010] Controlled forms: use controlled inputs with explicit value/onChange; avoid uncontrolled refs for form state ([RJS-FRM-001]).

Read the full file on GitHub · 222 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. 1mo ago First seen · 222 lines · 3,448 tokens per session scan A 0cd87df1e672

Subscribe to this mod's changes

loadout reactjs.instructions.md is an instructions file published in the GitHub repository stefaniuk/loadout (1 stars, last pushed yesterday), licensed MIT. It adds 3,448 tokens to every session, about $0.0138 per session on Opus 5.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

vscode buildNext.instructions.md

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 · 9,649 tokens

next.js AGENTS.md

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,257 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens