Agent skill

Feature Arch

React feature-based architecture guidelines for scalable applications.

MITAuto-check passedDevelopment

Install Feature Arch

skills CLI

$ npx skills add pproenca/dot-skills --skill feature-arch -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install pproenca/dot-skills feature-arch --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/feature-arch .claude/skills/feature-arch && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "feature-arch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.curated/feature-arch into .claude/skills/feature-arch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-arch", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.curated/feature-arch

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add pproenca/dot-skills --skill feature-arch -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install pproenca/dot-skills feature-arch --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/feature-arch .agents/skills/feature-arch && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "feature-arch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.curated/feature-arch into .agents/skills/feature-arch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-arch", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pproenca/dot-skills --skill feature-arch -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install pproenca/dot-skills feature-arch --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/feature-arch .cursor/skills/feature-arch && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "feature-arch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.curated/feature-arch into .cursor/skills/feature-arch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-arch", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.curated/feature-arch

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add pproenca/dot-skills --skill feature-arch -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install pproenca/dot-skills feature-arch --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/feature-arch .gemini/skills/feature-arch && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "feature-arch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.curated/feature-arch into .gemini/skills/feature-arch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-arch", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install pproenca/dot-skills feature-arch

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add pproenca/dot-skills --skill feature-arch -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/feature-arch .github/skills/feature-arch && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "feature-arch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.curated/feature-arch into .github/skills/feature-arch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-arch", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pproenca/dot-skills --skill feature-arch -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install pproenca/dot-skills feature-arch --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/feature-arch .opencode/skills/feature-arch && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "feature-arch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.curated/feature-arch into .opencode/skills/feature-arch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-arch", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: feature-arch
GitHub stars: 214
Token cost: ~2k tokens
SKILL.md length: 800 words
Files: 51 (incl. references, assets)
Skills in repo: 182
Repo updated: Aug 15, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

React feature-based architecture guidelines for scalable applications.

Works in 8 steps: Directory Structure (CRITICAL) → Import & Dependencies (CRITICAL) → Module Boundaries (HIGH) → …
Tasks involving project structure
SKILL.md covers Primary Output: The Target…, When to Apply, Rule Categories by Priority and Quick Reference, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Feature Arch is an agent skill from pproenca/dot-skills. 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…

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 53 other files, including reference files and assets (for example `AGENTS.md`, `README.md` and `assets/templates/_template.md`).

It sits in Development, covering React components and Refactoring. It works with React. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.

When your agent uses it

Tasks involving project structure
Feature organization
Module boundaries
Cross-feature imports

Example prompts

“/feature-arch”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Directory Structure (CRITICAL)
Import & Dependencies (CRITICAL)
Module Boundaries (HIGH)
Data Fetching (HIGH)
Component Organization (MEDIUM-HIGH)
State Management (MEDIUM)
Testing Strategy (MEDIUM)
Naming Conventions (LOW)

What it can do on your machine

Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Feature Arch loads about 2k tokens when it runs, and up to ~30k if it reads all its reference files. Until then it costs about 152 tokens; SKILL.md has 800 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~152
When it runs · the whole SKILL.md, loaded when a task matches: ~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~30k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 800 words, ~2,043 tokens.

Download SKILL.mdSave it as .claude/skills/feature-arch/SKILL.md (or your agent's skills folder). This skill also uses 50 other files; get the full folder from GitHub.

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:

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

Gather context (package.json, src/ tree, README, CLAUDE.md, openspec/).
Identify candidate features from routes, docs, and code clusters.
Confirm the feature list with the user via AskUserQuestion.
Record explicit decisions (layer model, comm mechanism, state/routing owner).
Fill in assets/templates/feature-arch-target.md.template — every {{placeholder}} replaced with a literal project value.
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

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-`

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

Show full SKILL.md (315 more words)Show less

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. Component Organization (MEDIUM-HIGH)

fcomp-single-responsibility - Apply single responsibility to components
fcomp-composition-over-props - Prefer composition over prop drilling
fcomp-container-presentational - Separate container and presentational concerns
fcomp-props-as-data-boundary - Use props as feature boundaries
fcomp-colocate-styles - Colocate styles with components
fcomp-error-boundaries - Use feature-level error boundaries

6. State Management (MEDIUM)

fstate-feature-scoped-stores - Scope state stores to features
fstate-server-state-separation - Separate server state from client state
fstate-lift-minimally - Lift state only as high as necessary
fstate-context-sparingly - Use context sparingly for feature state
fstate-reset-on-unmount - Reset feature state on unmount

7. Testing Strategy (MEDIUM)

test-colocate-with-feature - Colocate tests with features
test-feature-isolation - Test features in isolation
test-shared-utilities - Create feature-specific test utilities
test-integration-at-app-layer - Write integration tests at app layer

8. Naming Conventions (LOW)

name-feature-naming - Use domain-driven feature names
name-file-conventions - Use consistent file naming conventions
name-descriptive-exports - Use descriptive export names

How to Use

Read individual reference files for detailed explanations and code examples:

Blueprint process - How to derive a project-specific target architecture
Blueprint template - Template the agent fills in to produce the end-state document
Section definitions - Category structure and impact levels
Rule template - Template for adding new rules
Individual rules: references/{prefix}-{slug}.md

For feature planning, see feature-spec skill
For data fetching, see tanstack-query skill
For React component patterns, see react-19 skill

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

Files

SKILL.md and 50 other files (references, assets) in skills/.curated/feature-arch of pproenca/dot-skills.

SKILL.md
AGENTS.md
README.md
assets/templates/_template.md
assets/templates/feature-arch-target.md.template
metadata.json
references/_blueprint-process.md
references/_sections.md
references/bound-event-based-communication.md
references/bound-feature-isolation.md
references/bound-feature-scoped-routing.md
references/bound-feature-size.md
references/bound-interface-contracts.md
references/bound-minimize-shared-state.md
references/fcomp-colocate-styles.md
references/fcomp-composition-over-props.md
references/fcomp-container-presentational.md
references/fcomp-error-boundaries.md
… and 33 more

Open the folder on GitHubat commit cf93c57

Compare with similar skills

Feature Arch next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Feature Arch compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Feature Arch this skillpproenca/dot-skills	214	—	~2k	Automated safety check: Pass	MIT	1 mo ago
No Use Effectmattiacerutti/supernova	187	2 repos	~1.7k	Automated safety check: Pass	MIT	yesterday
React Best Practicesshapeshift/web	206	1 repos	~2k	Automated safety check: Pass	MIT	today
Migrate Componentasyncapi/generator	1.1k	—	~3k	Automated safety check: Pass	Apache-2.0	2 days ago
Project Form PatternsAkaraChen/aghub	272	—	~1.1k	Automated safety check: Pass	MIT	2 days ago
React Performanceaffaan-m/ECC	274k	1 repos	~4.5k	Automated safety check: Pass	MIT	2 days ago

Similar skills

No Use Effect
mattiacerutti/supernova
Enforce the no-useEffect rule when writing or reviewing React code.
187 GitHub starsUsed in 2 repos~1.7k tokens
DevelopmentAuto-check passed
React Best Practices
shapeshift/web
Comprehensive React and Next.js performance optimization guide with 40+ rules for eliminating waterfalls, optimizing bundles, and improving rendering.
206 GitHub starsUsed in 1 repo~2k tokens
DevelopmentAuto-check passed
Migrate Component
asyncapi/generator
Promote a duplicated React/JSX template-local component into the shared @asyncapi/generator-components package.
1.1k GitHub stars~3k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Project Form Patterns
AkaraChen/aghub
Form implementation guidance for the aghub desktop app. An agent skill from AkaraChen/aghub.
272 GitHub stars~1.1k tokensUpdated 2 days ago
DevelopmentAuto-check passed
React Performance
affaan-m/ECC
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills).
274k GitHub starsUsed in 1 repo~4.5k tokens
DevelopmentAuto-check passed
React Composition Patterns
vercel-labs/openreview
Official
Rules for structuring React components with composition instead of boolean props, covering compound components, lifted state, variants and React 19 changes.
1.7k GitHub starsUsed in 58 repos~721 tokens
Frontend & DesignAuto-check passed

Questions about Feature Arch

What does Feature Arch do?

React feature-based architecture guidelines for scalable applications. Feature Arch is an agent skill from pproenca/dot-skills. React feature-based architecture guidelines for scalable applications.

When should I use Feature Arch?

Feature Arch fits situations like: tasks involving project structure; feature organization; module boundaries; cross-feature imports.

How do I install Feature Arch in Claude Code?

Run `npx skills add pproenca/dot-skills --skill feature-arch -a claude-code`. Or copy the skill folder (skills/.curated/feature-arch in pproenca/dot-skills) into .claude/skills/feature-arch in your project. Claude Code loads it when a task matches its description.

How do I install Feature Arch in Codex?

Run `npx skills add pproenca/dot-skills --skill feature-arch -a codex`. Or copy the skill folder (skills/.curated/feature-arch in pproenca/dot-skills) into .agents/skills/feature-arch in your project. Codex loads it when a task matches its description.

Can I use Feature Arch in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill feature-arch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature-arch, .gemini/skills/feature-arch, .github/skills/feature-arch and .opencode/skills/feature-arch in your project.

What does Feature Arch need to run?

SKILL.md names no scripts, command-line tools or credentials: Feature Arch is instructions for the agent only.

Does Feature Arch access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Feature Arch safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Feature Arch use?

Feature Arch is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Feature Arch use?

About 2k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 28k tokens, read only when the agent opens those files.

What are the alternatives to Feature Arch?

Skills that share tags, products or a category with Feature Arch: No Use Effect (mattiacerutti/supernova, 187 stars), React Best Practices (shapeshift/web, 206 stars), Migrate Component (asyncapi/generator, 1.1k stars) and Project Form Patterns (AkaraChen/aghub, 272 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Feature Arch?

pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 214 GitHub stars. The repository holds 182 skills in this directory. The repository was last updated on August 15, 2026.

Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Feature Arch

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Feature-Based Architecture Best Practices

Primary Output: The Target Architecture Blueprint

How the agent generates the blueprint

When to Apply

Rule Categories by Priority

Quick Reference

1. Directory Structure (CRITICAL)

2. Import & Dependencies (CRITICAL)

3. Module Boundaries (HIGH)

4. Data Fetching (HIGH)

5. Component Organization (MEDIUM-HIGH)

6. State Management (MEDIUM)

7. Testing Strategy (MEDIUM)

8. Naming Conventions (LOW)

How to Use

Related Skills

Full Compiled Document

Files

Compare with similar skills

Similar skills

More from pproenca/dot-skills

Related

Questions about Feature Arch