react-architect-skills

Enforce scalable React module architecture with folder-based feature, container, hook, and domain layers.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/pelith/Project-Remora-Frontend --skill react-architect-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react-architect-skills
Source: https://github.com/pelith/Project-Remora-Frontend/tree/main/.agents/skills/react-architect-skills
Command: npx skills add https://github.com/pelith/Project-Remora-Frontend --skill react-architect-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle with growing React apps as they scale, leading to tangled code, duplicated logic, and fragile dependencies. This Skill provides a structured approach to organizing codebases with clear module boundaries, folder conventions, and architecture guidelines to improve maintainability and collaboration.

Core Features & Use Cases

  • Folder-based module boundaries: Enforces colocated modules (features, components, hooks, and tests) to minimize cross-feature coupling.
  • Layered Architecture: Defines Presentational (UI), Integration (containers/pages), Domain (hooks/utils), and Data (api/store) layers to separate concerns.
  • Naming & Boundaries: Establishes consistent naming, public API boundaries (index.ts), and module isolation to support safe refactors.
  • Use Case: When refactoring a large React project, apply these guidelines to reorganize code into feature modules with stable public APIs.

Quick Start

Audit an existing React project against the guidelines and draft a modularization plan outlining feature modules, colocated directories, and public APIs.

Frequently Asked Questions about react-architect-skills

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

FAQPage Schema
How do I structure a scalable React architecture with clear module boundaries?

Structure scalable React architecture by organizing folder-based projects into feature modules with colocated components, hooks, and tests, defining Presentational, Integration, Domain, and Data layers to separate concerns and minimize cross-feature coupling.

What is the best way to enforce layer separation in a large React project?

Enforce layer separation by defining Presentational (UI), Integration (containers/pages), Domain (hooks/utils), and Data (api/store) layers, establishing consistent naming and public API boundaries via index.ts to ensure module isolation and maintainability.

How do I refactor tangled React code into modular feature modules?

Refactor tangled React code by auditing the project against modularization guidelines, drafting a plan to reorganize code into feature modules with colocated directories, stable public APIs, and strict module isolation to support safe refactors.

Does this React architecture Skill work with folder-based projects using TanStack Router?

This Skill applies to folder-based React projects using features, containers, hooks, and domain layers, guiding modularization and boundaries, making it compatible with folder-driven routing setups like TanStack Router.

Why should I use public API boundaries and index.ts files in React feature modules?

Use public API boundaries and index.ts files in React feature modules to establish module isolation, enforce consistent naming conventions, and ensure maintainable code across teams by preventing unauthorized cross-feature imports.

When should I not use a layered architecture for my React application?

Avoid a layered architecture for small React applications where the overhead of defining Presentational, Integration, Domain, and Data layers outweighs the benefits, as this Skill targets growing apps struggling with tangled code and fragile dependencies.