feature-specific-business-logic

Structure domain-specific feature logic under src/features with modular components and custom hooks.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/wonkpentink/agent-skills-fe --skill feature-specific-business-logic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-specific-business-logic
Source: https://github.com/wonkpentink/agent-skills-fe/tree/main/skills/feature-specific-business-logic
Command: npx skills add https://github.com/wonkpentink/agent-skills-fe --skill feature-specific-business-logic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams to design and implement domain-specific feature logic inside src/features, ensuring clean separation between UI and business logic and enabling scalable modularity across complex workflows like contacts, assignments, and bulk operations.

Core Features & Use Cases

  • Defines clear feature-domain boundaries within src/features and encourages reusable patterns across multiple features.
  • Demonstrates how to compose components, integrate custom hooks, manage API mutations, and structure multi-step forms.
  • Provides best-practices examples and real-world patterns from the codebase to accelerate feature development.

Quick Start

Analyze requirements for a new domain feature, create the feature folder under src/features, scaffold a main component plus necessary sub-components, and apply the recommended patterns.

Frequently Asked Questions about feature-specific-business-logic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure domain feature logic in React to separate business logic from UI components?

Structure domain feature logic by organizing code under src/features with sub-folders for modular components, custom hooks, and type definitions. This enforces clean separation between UI and business logic, enabling scalable modularity across complex workflows like contacts and assignments.

What is the best way to scaffold multi-step forms and API mutations in a TypeScript feature folder?

Scaffold multi-step forms and API mutations within src/features by composing sub-components and integrating custom hooks. This approach provides reusable patterns that manage complex workflows while maintaining strict TypeScript typing and domain boundaries.

When should I use a feature-folder architecture for React hooks and domain logic?

Use a feature-folder architecture when building domain-specific features like filters or bulk operations that require clear boundaries. It keeps code organized and maintainable by isolating components, custom hooks, and type definitions within src/features.

Does this domain feature pattern require any specific project dependencies or existing component libraries?

No specific external dependencies are required. The pattern requires a feature-folder structure under src/features and uses TypeScript for type definitions, relying on standard React custom hooks and modular components for implementation.

How do I organize reusable patterns and type definitions for complex feature workflows?

Organize reusable patterns and type definitions by creating dedicated sub-folders within src/features. This modular structure accelerates feature development by providing best-practice examples for custom hooks, API mutations, and multi-step forms across multiple domain features.