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).
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfeature-archExecute the skills CLI command in your project's root directory to begin installation:
Fetches feature-arch from pproenca/dot-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate feature-arch. Access via /feature-arch in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
95
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
95
stars
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).
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Directory Structure | CRITICAL | struct- |
| 2 | Import & Dependencies | CRITICAL | import- |
| 3 | Module Boundaries | HIGH | bound- |
| 4 | Data Fetching | HIGH | fquery- |
| 5 | Component Organization | MEDIUM-HIGH | fcomp- |
| 6 | State Management | MEDIUM | fstate- |
| 7 | Testing Strategy | MEDIUM | test- |
| 8 | Naming Conventions | LOW | name- |
struct-feature-folders - Organize by feature, not technical typestruct-feature-self-contained - Make features self-containedstruct-shared-layer - Use shared layer for truly generic code onlystruct-flat-hierarchy - Keep directory hierarchy flatstruct-optional-segments - Include only necessary segmentsstruct-app-layer - Separate app layer from featuresimport-unidirectional-flow - Enforce unidirectional import flowimport-no-cross-feature - Prohibit cross-feature importsimport-public-api - Export through public API onlyimport-avoid-barrel-files - Avoid deep barrel file re-exportsimport-path-aliases - Use consistent path aliasesimport-type-only - Use type-only imports for typesbound-feature-isolation - Enforce feature isolationbound-interface-contracts - Define explicit interface contractsbound-feature-scoped-routing - Scope routing to feature concernsbound-minimize-shared-state - Minimize shared state between featuresbound-event-based-communication - Use events for cross-feature communicationbound-feature-size - Keep features appropriately sizedfquery-single-responsibility - Keep query functions single-purposefquery-colocate-with-feature - Colocate data fetching with featuresfquery-parallel-fetching - Fetch independent data in parallelfquery-avoid-n-plus-one - Avoid N+1 query patternsfquery-feature-scoped-keys - Use feature-scoped query keysfquery-server-component-fetching - Fetch at server component levelfcomp-single-responsibility - Apply single responsibility to componentsfcomp-composition-over-props - Prefer composition over prop drillingfcomp-container-presentational - Separate container and presentational concernsfcomp-props-as-data-boundary - Use props as feature boundariesfcomp-colocate-styles - Colocate styles with componentsfcomp-error-boundaries - Use feature-level error boundariesfstate-feature-scoped-stores - Scope state stores to featuresfstate-server-state-separation - Separate server state from client statefstate-lift-minimally - Lift state only as high as necessaryfstate-context-sparingly - Use context sparingly for feature statefstate-reset-on-unmount - Reset feature state on unmounttest-colocate-with-feature - Colocate tests with featurestest-feature-isolation - Test features in isolationtest-shared-utilities - Create feature-specific test utilitiestest-integration-at-app-layer - Write integration tests at app layername-feature-naming - Use domain-driven feature namesname-file-conventions - Use consistent file naming conventionsname-descriptive-exports - Use descriptive export namesRead individual reference files for detailed explanations and code examples:
references/{prefix}-{slug}.mdfeature-spec skilltanstack-query skillreact-19 skillFor the complete guide with all rules expanded: AGENTS.md
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
pproenca/dot-skills
pproenca/dot-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
We added feature-arch from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added feature-arch from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: feature-arch is focused, and the summary matches what you get after install.
feature-arch fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for feature-arch matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in feature-arch — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
feature-arch has been reliable in day-to-day use. Documentation quality is above average for community skills.
feature-arch fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
feature-arch is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: feature-arch is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 31