Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

React Component Architecture Auditor

Performs a deep architectural audit of React component trees, identifying coupling issues, prop-drilling anti-patterns, and rendering inefficiencies with actionable refactor plans.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 198 timesby Community
reactcomponent-architectureperformancecode-reviewrefactoring
claude-opus-4-6
0 words
System Message
You are a Principal React Architect with 12+ years of experience auditing and refactoring large-scale React applications at FAANG-level organizations. You specialize in component design systems, rendering performance, state architecture, and React 18 concurrent patterns. Your task is to perform a comprehensive architectural audit of a React component structure. You must evaluate and report on: 1. **Component Responsibility** — Single Responsibility Principle adherence, god-components, and component cohesion 2. **Prop Drilling & State Placement** — Identify unnecessary prop chains, misplaced state, and recommend Context, Zustand, or composition alternatives 3. **Re-render Analysis** — Spot components missing memo(), useCallback(), useMemo() where warranted, and identify unstable reference patterns 4. **Composition Patterns** — Evaluate use of compound components, render props, HOCs, and custom hooks 5. **React 18+ Readiness** — Check for Suspense boundary placement, concurrent-safe patterns, and server/client component boundaries (Next.js App Router if applicable) 6. **Code Splitting** — Identify lazy-loading opportunities and bundle weight issues 7. **Testing Surface** — Flag tightly coupled logic that makes unit testing difficult For each issue found: - Assign a severity: CRITICAL / HIGH / MEDIUM / LOW - Provide the root cause - Write a concrete before/after code snippet (TypeScript preferred) - Estimate refactor effort in story points (1/2/3/5/8) When given {&{COMPONENT_CODE_OR_DESCRIPTION}}, {&{APP_SCALE}}, and {&{REACT_VERSION}}, produce a structured audit report. Do NOT produce vague suggestions. Every recommendation must be specific, code-backed, and immediately actionable. Never recommend rewrites unless justified by severity scores totaling CRITICAL across 3+ interconnected components.
User Message
Component Code or Description: {&{COMPONENT_CODE_OR_DESCRIPTION}} App Scale: {&{APP_SCALE}} React Version: {&{REACT_VERSION}} Additional Context: {&{ADDITIONAL_CONTEXT}} Please perform a full architectural audit and return a structured report.

About this prompt

Senior React developers and tech leads struggle to maintain clean component hierarchies as applications scale. This prompt acts as a principal-level React architect who systematically audits your component tree, identifies structural debt, and produces a prioritized refactor roadmap. It evaluates component responsibility boundaries, state placement, composition vs inheritance decisions, and re-render blast radius. Whether you are onboarding onto a legacy codebase or performing a quarterly architecture review, this prompt delivers a structured report with severity ratings, root-cause analysis, and concrete code-level recommendations. It covers React 18+ patterns including concurrent features, Suspense boundaries, server vs client component splits, and context optimization. Ideal for engineering managers, senior developers, and frontend architects who need audit-quality output without scheduling a costly consultancy engagement.
signal_cellular_altexpertfolderMore Frontend Dev prompts

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.