Individual skill
feature-arch
Feature-based React folder structure and module boundaries.
skills/feature-arch/SKILL.md
Source commit b210600fdf49441ee1efeca2cbdc05599ec03019
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 42
- Repository last updated
- Nov 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-coding-assistant Repository topic
- claude-code Repository topic
- codex Repository topic
- cursor Repository topic
- frontend Repository topic
- nextjs Repository topic
- opencode Repository topic
- react Repository topic
- engineering Derived category
- engineering-web Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,753 bytesreferences/bound-event-based-communication.mddoc · 2,618 bytesreferences/bound-feature-isolation.mddoc · 2,339 bytesreferences/bound-feature-scoped-routing.mddoc · 2,384 bytesreferences/bound-feature-size.mddoc · 2,400 bytesreferences/bound-interface-contracts.mddoc · 2,146 bytesreferences/bound-minimize-shared-state.mddoc · 2,248 bytesreferences/fcomp-colocate-styles.mddoc · 2,275 bytesreferences/fcomp-composition-over-props.mddoc · 2,428 bytesreferences/fcomp-container-presentational.mddoc · 2,599 bytesreferences/fcomp-error-boundaries.mddoc · 2,519 bytesreferences/fcomp-props-as-data-boundary.mddoc · 2,528 bytesreferences/fcomp-single-responsibility.mddoc · 2,664 bytesreferences/fquery-avoid-n-plus-one.mddoc · 2,317 bytesreferences/fquery-colocate-with-feature.mddoc · 2,052 bytesreferences/fquery-feature-scoped-keys.mddoc · 2,161 bytesreferences/fquery-parallel-fetching.mddoc · 2,202 bytesreferences/fquery-server-component-fetching.mddoc · 2,369 bytesreferences/fquery-single-responsibility.mddoc · 2,051 bytesreferences/fstate-context-sparingly.mddoc · 2,194 bytesreferences/fstate-feature-scoped-stores.mddoc · 2,274 bytesreferences/fstate-lift-minimally.mddoc · 2,379 bytesreferences/fstate-reset-on-unmount.mddoc · 2,404 bytesreferences/fstate-server-state-separation.mddoc · 2,627 bytesreferences/import-avoid-barrel-files.mddoc · 2,025 bytesreferences/import-no-cross-feature.mddoc · 2,435 bytesreferences/import-path-aliases.mddoc · 1,786 bytesreferences/import-public-api.mddoc · 2,090 bytesreferences/import-type-only.mddoc · 2,115 bytesreferences/import-unidirectional-flow.mddoc · 2,281 bytesreferences/name-descriptive-exports.mddoc · 2,085 bytesreferences/name-feature-naming.mddoc · 1,966 bytesreferences/name-file-conventions.mddoc · 2,338 bytesreferences/struct-app-layer.mddoc · 2,006 bytesreferences/struct-feature-folders.mddoc · 2,094 bytesreferences/struct-feature-self-contained.mddoc · 1,886 bytesreferences/struct-flat-hierarchy.mddoc · 1,686 bytesreferences/struct-optional-segments.mddoc · 1,979 bytesreferences/struct-shared-layer.mddoc · 2,063 bytesreferences/test-colocate-with-feature.mddoc · 2,067 bytesreferences/test-feature-isolation.mddoc · 2,278 bytesreferences/test-integration-at-app-layer.mddoc · 2,790 bytesreferences/test-shared-utilities.mddoc · 2,517 bytes
Read excerpt
# Feature-Based Architecture Best Practices
Comprehensive architecture guide for organizing React applications by features, enabling scalable development with independent teams. Contains 42 rules across 8 categories, prioritized by impact from critical (directory structure, imports) to incremental (naming conventions).
## When to Apply
Reference these guidelines when:
- Creating new features or modules
- Organizing project directory structure
- Setting up import rules and boundaries
- Implementing data fetching patterns
- Composing components from multiple features
- Reviewing code for architecture violations
