reviewing-component-architecture

Audit React 19 component architectures for size, composition, and server/client boundaries.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/djankies/claude-configs --skill reviewing-component-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-component-architecture
Source: https://github.com/djankies/claude-configs/tree/main/react-19/skills/reviewing-component-architecture
Command: npx skills add https://github.com/djankies/claude-configs --skill reviewing-component-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps review component architecture focusing on size, composition, server/client boundaries, and anti-patterns.

Core Features & Use Cases

  • Enforce small components, single responsibility, and clear boundaries.
  • Promote composition over heavy prop APIs.
  • Detect anti-patterns like server components in client components and over-large components.

Quick Start

Evaluate a component tree against the checklist and propose refactors.

Frequently Asked Questions about reviewing-component-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit React component architecture for size and anti-patterns?

Auditing React component architecture involves reviewing components for size (keeping them under 300 lines), single responsibility, proper composition patterns, and anti-pattern violations. This Skill evaluates your component tree against these criteria and identifies refactoring opportunities to improve maintainability and performance.

What are the key rules for React 19 server and client component boundaries?

React 19 enforces clear server/client boundaries: use 'use client' directives correctly, fetch data only in Server Components, avoid server components inside client components, and prevent deep prop drilling. This Skill detects boundary violations and helps you structure components according to these rules.

How do I detect composition and anti-pattern issues in my React codebase?

Composition issues include over-sized components, improper Context usage, Web Components convention violations, and heavy prop APIs. This Skill reviews your component architecture systematically to flag these patterns and recommend composition-first refactors.

When should I refactor my React components for better architecture?

Refactor when components exceed 300 lines, violate single responsibility, drill props deeply, mix server and client concerns, or ignore composition principles. This Skill helps identify these signals during design reviews and refactoring cycles to guide your architectural decisions.

Can I use this to evaluate React 19 component design during code review?

Yes, this Skill applies to codebases undergoing design reviews, refactors, or architecture decisions. It evaluates component size, boundaries, composition patterns, and anti-patterns, making it ideal for systematic architectural assessment before merging component changes.

What's the best way to structure React components to avoid anti-patterns?

Best practices include keeping components small and focused, using composition over prop drilling, placing data fetching in Server Components, correctly applying 'use client' directives, and following Web Components conventions. This Skill enforces these patterns and surfaces violations for targeted refactoring.