Reorganize modules into four-layer feature boundaries with strict import rules.
npx skills add https://github.com/beeman/skills --skill feature-structure-beeman
Please help me install this Agent Skill. Skill: feature-structure Source: https://github.com/beeman/skills/tree/main/feature-structure Command: npx skills add https://github.com/beeman/skills --skill feature-structure-beeman
Use when reorganizing code around feature boundaries, splitting monolithic screen components or state hooks, deciding whether logic belongs in data-access, feature, ui, or child features, or moving orchestration out of prop-heavy UI files.
Refactor the repository's feature code into a parent feature with child features and separate UI leaves following the four-layer boundaries.
High-intent search queries and answers about installing and using this skill.
Split monolithic screen components by applying a four-layer architecture with strict import boundaries, reorganizing them into parent features, child features, and separate leaf UI components. This decomposition moves orchestration logic out of prop-heavy UI files into explicit parent-child feature contracts.
The four-layer pattern organizes code into data-access, feature or feature-<app>, ui or ui-<app>, and optional util layers. It enforces strict import boundaries between these layers to clearly separate data fetching, business orchestration, and presentation concerns.
Logic placement follows strict four-layer import boundaries: data-access handles data fetching, feature manages workflow orchestration and gating, and ui handles presentation. This separation prevents prop-heavy UI files and keeps modules aligned with feature boundaries.
Refactor around feature boundaries by reusing existing wiring and layout where possible, moving monolithic screens into parent and child features while preserving repository naming conventions. This approach minimizes disruption while establishing strict parent-child feature contracts.
Reorganize modules by feature boundaries when splitting monolithic screen components or state hooks, deciding where logic belongs across data-access and UI layers, or moving orchestration out of prop-heavy UI files into explicit parent-child feature contracts.
SethGammonGenerate new project files matching existing codebase conventions and wiring.
p-o-ke-naeDesign modular monolith clean-architecture structures with strict dependency boundaries.
michelveGenerate interactive HTML dependency graphs from React component imports.
deepnoodle-aiIdentify and apply software architecture patterns to organize codebases.
