feature-arch

Organize React applications using feature-based architecture principles.

193|17|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/pproenca/dot-skills --skill feature-arch-pproenca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-arch
Source: https://github.com/pproenca/dot-skills/tree/main/skills/.curated/feature-arch
Command: npx skills add https://github.com/pproenca/dot-skills --skill feature-arch-pproenca

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining large, complex React applications by providing a structured approach to code organization, ensuring scalability, maintainability, and independent feature development.

Core Features & Use Cases

  • Feature-Based Organization: Structures code around business domains, not technical types, reducing navigation complexity.
  • Module Boundaries: Enforces clear separation and isolation between features to prevent coupling.
  • Scalable Architecture: Provides guidelines for managing dependencies, data fetching, and component composition in growing codebases.
  • Use Case: When starting a new React project or refactoring an existing one, apply these principles to establish a robust, scalable architecture that teams can easily contribute to.

Quick Start

Apply the feature-arch skill to refactor the current project's directory structure according to feature-based principles.

Frequently Asked Questions about feature-arch

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

FAQPage Schema
How do I structure a large React application for scalability?

Structure large React applications using feature-based architecture to organize code around business domains rather than technical types. This approach enforces module boundaries and feature isolation, reducing navigation complexity and ensuring independent feature development.

What is the best way to enforce module boundaries in a React codebase?

Enforce module boundaries in React by applying unidirectional import flows and feature isolation. This prevents coupling between distinct business domains by ensuring features cannot import from each other unpredictably, maintaining strict separation and codebase stability.

How do I refactor an existing React project to use feature-based architecture?

Refactor an existing React project by reorganizing the directory structure around business domains. Apply the 42 rules across 8 categories to establish feature isolation, colocate related code, and enforce unidirectional import flows for enhanced maintainability.

Can I use feature-based architecture for managing data fetching and component composition?

Yes, feature-based architecture provides specific guidelines for managing data fetching and component composition. Colocating these concerns within isolated feature modules ensures that growing codebases remain scalable and maintainable as application complexity increases.

When should I avoid organizing React code by technical types instead of features?

Avoid organizing by technical types when your React application scales and multiple teams contribute simultaneously. Feature-based architecture becomes necessary to prevent module coupling, reduce navigation complexity, and enable independent feature development.