跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

feature-arch

React feature-based architecture guidelines for scalable applications. This skill should be used when writing, reviewing, or refactoring React code to ensure proper feature organization. When invoked on a project, the agent produces a concrete target-architecture blueprint at docs/architecture/FEATURE-ARCH-TARGET.md showing the desired directory tree, per-feature public APIs, import-boundary matrix, and a numbered migration plan. Triggers on tasks involving project structure, feature organization, module boundaries, cross-feature imports, data fetching patterns, or component composition.

pproenca · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add pproenca/dot-skills --skill feature-arch

技能说明


name: feature-arch description: React feature-based architecture guidelines for scalable applications. This skill should be used when writing, reviewing, or refactoring React code to ensure proper feature organization. When invoked on a project, the agent produces a concrete target-architecture blueprint at docs/architecture/FEATURE-ARCH-TARGET.md showing the desired directory tree, per-feature public APIs, import-boundary matrix, and a numbered migration plan. Triggers on tasks involving project structure, feature organization, module boundaries, cross-feature imports, data fetching patterns, or component composition.

Feature-Based Architecture Best Practices

Comprehensive architecture guide for organizing React applications by features, enabling scalable development with independent teams. Contains 43 rules across 8 categories, prioritized by impact from critical (directory structure, imports) to incremental (naming conventions). When invoked on a real project, the skill produces a project-specific blueprint that anchors every decision in those rules.

Primary Output: The Target Architecture Blueprint

When an agent invokes this skill on a real project, the deliverable is a single markdown file persisted at docs/architecture/FEATURE-ARCH-TARGET.md (or the repo's existing docs location). The blueprint contains:

  1. Project context — framework, state libraries, routing model, current shape.
  2. Identified features — confirmed with the user, sourced from routes, docs, openspec, and code clusters.
  3. Target directory tree — literal paths, not pseudo-trees.
  4. Per-feature public APIs — exact named exports of each index.ts.
  5. Import-boundary matrix — N×N table of feature relationships (allowed / forbidden / via app / via events).
  6. State & data ownership — server-state and client-state owner per feature.
  7. Cross-feature communication policy — composition, events, or shared slice — with rationale.
  8. Numbered migration plan — file-level move/create/delete steps with S/M/L effort estimates.
  9. Human conformance checklist — for code review and "definition of done".
  10. Open questions — anything that needs a human decision before migration.

Every section cites the specific rules below that govern its decisions, so the blueprint stays a projection of this skill — not a parallel authority.

How the agent generates the blueprint

Follow the process in references/_blueprint-process.md. Summary:

  1. Gather context (package.json, src/ tree, README, CLAUDE.md, openspec/).
  2. Identify candidate features from routes, docs, and code clusters.
  3. Confirm the feature list with the user via AskUserQuestion.
  4. Record explicit decisions (layer model, comm mechanism, state/routing owner).
  5. Fill in assets/templates/feature-arch-target.md.template — every {{placeholder}} replaced with a literal project value.
  6. Hand off: print path, summarise feature/step counts, list top-3 risks, suggest next action. Do not start executing migration steps in the same turn.

For very small projects (under ~10 source files), produce a one-page seed structure instead and note that a full blueprint should follow after the 2nd–3rd feature exists.

When to Apply

Reference these guidelines when:

  • A project asks for a feature-based architecture target (generate the blueprint).
  • 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.

Rule Categories by Priority

PriorityCategoryImpactPrefix
1Directory StructureCRITICALstruct-
2Import & DependenciesCRITICALimport-
3Module BoundariesHIGHbound-
4Data FetchingHIGHfquery-
5Component OrganizationMEDIUM-HIGHfcomp-
6State ManagementMEDIUMfstate-
7Testing StrategyMEDIUMtest-
8Naming ConventionsLOWname-

Quick Reference

1. Directory Structure (CRITICAL)

  • struct-feature-folders - Organize by feature, not technical type
  • struct-feature-self-contained - Make features self-contained
  • struct-shared-layer - Use shared layer for truly generic code only
  • struct-flat-hierarchy - Keep directory hierarchy flat
  • struct-optional-segments - Include only necessary segments
  • struct-app-layer - Separate app layer from features
  • struct-domain-folders - Group features into domains at large scale

2. Import & Dependencies (CRITICAL)

  • import-unidirectional-flow - Enforce unidirectional import flow
  • import-no-cross-feature - Prohibit cross-feature imports
  • import-public-api - Export through public API only
  • import-avoid-barrel-files - Avoid deep barrel file re-exports
  • import-path-aliases - Use consistent path aliases
  • import-type-only - Use type-only imports for types

3. Module Boundaries (HIGH)

  • bound-feature-isolation - Enforce feature isolation
  • bound-interface-contracts - Define explicit interface contracts
  • bound-feature-scoped-routing - Scope routing to feature concerns
  • bound-minimize-shared-state - Minimize shared state between features
  • bound-event-based-communication - Use events for cross-feature communication
  • bound-feature-size - Keep features appropriately sized

4. Data Fetching (HIGH)

  • fquery-single-responsibility - Keep query functions single-purpose
  • fquery-colocate-with-feature - Colocate data fetching with features
  • fquery-parallel-fetching - Fetch independent data in parallel
  • fquery-avoid-n-plus-one - Avoid N+1 query patterns
  • fquery-feature-scoped-keys - Use feature-scoped query keys
  • fquery-server-component-fetching - Fetch at server component level

5.

阅读完整来源 ↗