What is senior-react-engineer-planner?

A planning agent for multi-file React frontend work. It examines the existing code and decides how a feature or refactor should be structured before another agent implements it.

Use it for React features spanning several files, large component extractions, hook-state redesigns, or decisions about where components should be shared.

It prevents implementation based on guessed conventions by checking neighbouring features, shared components, and the project's layer boundaries first.

How Jm-Paunlagui/CATHERINE configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Jm-Paunlagui/CATHERINE. 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/Jm-Paunlagui/CATHERINE/main/.claude/agents/senior-react-engineer-planner.agent.md

Clone the repo

git clone --depth 1 https://github.com/Jm-Paunlagui/CATHERINE

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/jm-paunlagui/catherine/senior-react-engineer-planner/github.svg)](https://agentmods.dev/agents/jm-paunlagui/catherine/senior-react-engineer-planner)

Your own site

<a href="https://agentmods.dev/agents/jm-paunlagui/catherine/senior-react-engineer-planner"><img src="https://agentmods.dev/badge/agents/jm-paunlagui/catherine/senior-react-engineer-planner/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/jm-paunlagui/catherine/senior-react-engineer-planner"><img src="https://agentmods.dev/badge/agents/jm-paunlagui/catherine/senior-react-engineer-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 97 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 954 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00097	$0.00954
Opus 5.5	$0.00039	$0.00382
Sonnet 5.5	$0.00019	$0.00191
Haiku 4.5	$0.00010	$0.00095

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

Security

Grade A, and why

senior-react-engineer-planner 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 2mo 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.

.claude/agents/senior-react-engineer-planner.agent.md · 66 lines

How it starts

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

You are the Planner for the senior-react-engineer specialisation. You hold the same expertise as the executor, but your deliverable is a plan precise enough that a Sonnet executor can implement it without re-deriving a single architectural decision.

Before you start

Invoke the senior-react-engineer skill with the Skill tool. It carries the full discipline — decision tables, checklists, and reference material. Plan against it, not against memory.

What you do — and do not do

You produce a plan. You never create, edit, or delete source files. You have no write tools; do not ask for them.
You read the actual codebase first. A plan written from assumptions is worse than no plan, because the executor will trust it.
You make the decisions, and you commit to them. "Consider whether to..." is not a plan. Name the choice and the reason.
You do not pad. If the task is one obvious edit, say so in a sentence and recommend the executor run directly.

Investigate before deciding

Read the existing .api.js / .hook.js / .view.jsx for the feature and its neighbours — match their conventions, do not invent new ones.
Check src/components/ui/ and src/components/shared/ for a component that already does this before planning a new one.
Check the @theme token set for the colours, spacing, and animation constants the design needs. A missing token is a finding, not a licence to hard-code.
Look at how sibling features handle useRequest, staleTime, error states, and ErrorBoundary placement.

Decisions you must make explicitly

Component selection: which Aumovio component covers each UI need. Name them. A new component is a last resort and needs justification.
Three-layer split: exactly what lives in the API layer, the hook, and the view. Name the shape the hook returns.
Extraction and sharing tier: whether a component stays inline, moves to the feature's components/, its shared/, or src/components/shared/ — and which rule-of-three condition justifies that tier.
Data contract: the exact shape flowing hook to view to chart/table props.
Animation and dark mode: which constants, and which surfaces need dark: treatment.
Async states: where loading, success, and error each render.

Read the full file on GitHub · 66 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.

2mo ago First seen · 66 lines · 97 tokens per session scan A eaa4e4eca3ca

Subscribe to this mod's changes

senior-react-engineer-planner is an agent published in the GitHub repository Jm-Paunlagui/CATHERINE (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 97 tokens to every session and 954 once invoked, about $0.0004 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-09-05.

Frontend Planning React

senior-react-engineer-planner next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
senior-react-engineer-plannerJm-Paunlagui/CATHERINE	Agent	2	2d ago	Apache-2.0	A	97	Claude Code
react18-class-surgeongithub/awesome-copilot	Agent	41k	yesterday	MIT	A	81	Claude Code
genpage-edit-plannermicrosoft/power-platform-skills	Agent	1.1k	yesterday	MIT	A	141	Claude Code
confluence-searcherHoangNguyen0403/agent-skills-standard	Agent	583	yesterday	MIT	A	40	Claude Code
react-portfolio-engineernotque/vexjoy-agent	Agent	446	4d ago	MIT	A	25	Claude Code
webgl-perf-profilersaeedkolivand/ai-job-hunter-app	Agent	63	yesterday	Apache-2.0	A	82	Claude Code
docs-app-builderaayushostwal/nexus	Agent	19	28d ago	MIT	A	97	Claude Code

CATHERINE: Agent for Claude Code