Feature Development
Outlines engineering standards and directory structures for consistent, scalable feature development in React applications.
Install
mkdir -p .claude/skills/feature-development && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9854" && unzip -o skill.zip -d .claude/skills/feature-development && rm skill.zipInstalls to .claude/skills/feature-development
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Guidelines and best practices for creating new features in the application.Key capabilities
- →Feature directory structure
- →Component colocation
- →Lazy loading routing
- →Clean code standards
How it works
It provides a standardized directory structure and checklist for developing features using clean code and SOLID principles.
Inputs & outputs
When to use Feature Development
- →Developing a new feature
- →Organizing project folders
- →Refactoring existing features
- →Applying clean code standards
About this skill
Feature Development Skill
This skill outlines the standards and practices for adding new features to the application.
Core Principles (Senior Engineer Standards)
- Clean Code:
- DRY (Don't Repeat Yourself): Extract usage patterns into reusable hooks or components.
- SOLID: Components should have a single responsibility.
- Meaningful Naming: Variables and functions should clearly describe their intent (e.g.,
isModalOpenvsopen).
- Component Structure:
- Small & Focused: Break down large views into smaller sub-components.
- Colocation: Keep related styles, tests, and types close to the component.
- Modern React:
- Use Functional Components and Hooks.
- Avoid
useEffectfor derived state; useuseMemoor simple derivation during render.
Feature Structure
When creating a new feature, follow this directory structure:
src/features/<FeatureName>/
├── index.js # Public API export
├── <FeatureName>.jsx # Main Feature Component
├── components/ # Sub-components specific to this feature
└── hooks/ # Custom hooks specific to this feature
Routing
- All new page-level features must be registered in the main router (typically
src/App.jsxor a dedicatedroutesfile). - Use lazy loading for page components to optimize bundle size:
const NewFeature = lazy(() => import('./features/NewFeature'));
Implementation Checklist (New Feature)
- Create feature directory.
- Implement main component.
- Add sub-components as needed.
- Export from
src/features/index.js. - Register route and navigation in
src/App.jsx(MENU_GROUPS+FEATURE_COMPONENTS). - Verify responsiveness and styling (Tailwind CSS).
- Update
README.mdto include the new feature in the features list.
Update/Rename Checklist
When updating or renaming an existing feature, ensure all of the following are updated:
- Rename/update the component file (
src/features/<FeatureName>.jsxorsrc/features/<FeatureName>/). - Update component name and
export defaultinside the file. - Update export in
src/features/index.js. - Update
src/App.jsx:- Import statement.
-
MENU_GROUPS— updateid(route) andlabel(display name). -
FEATURE_COMPONENTS— update key and component reference.
- Update
README.md— feature name and description in the features table.
When not to use it
- →Non-React projects
- →Monolithic component structures
Limitations
- →Requires adherence to directory structure
How it compares
It enforces a strict architectural pattern for feature development rather than ad-hoc organization.
Compared to similar skills
Feature Development side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| Feature Development (this skill) | 0 | 5mo | No flags | Intermediate |
| technology-stack | 3 | 3mo | No flags | Intermediate |
| accessibility-compliance | 45 | 2mo | No flags | Intermediate |
| typescript | 28 | 2mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
technology-stack
ag-grid
Technology choices and architectural constraints for AG Grid. Use when choosing technologies, adding dependencies, or understanding zero-dependency requirements.
accessibility-compliance
wshobson
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
typescript
lobehub
TypeScript code style and optimization guidelines. Use when writing TypeScript code (.ts, .tsx, .mts files), reviewing code quality, or implementing type-safe patterns. Triggers on TypeScript development, type safety questions, or code style discussions.
nextjs-best-practices
davila7
Next.js App Router principles. Server Components, data fetching, routing patterns.
frontend-code-review
langgenius
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
react-best-practices
redpanda-data
Client-side React performance optimization patterns.