SOLID React - Component Architecture

Codebase Analysis (MANDATORY)

1. Explore project structure to understand architecture
2. Read existing related files to follow established patterns
3. Identify naming conventions, coding style, and patterns used
4. Understand data flow and dependencies

DRY - Reuse or Create Shared (MANDATORY)

1. Grep the codebase for similar function names, patterns, or logic
2. Check shared locations:

   modules/cores/lib/

   ,

   modules/cores/components/

   ,

   modules/cores/hooks/

3. If similar code exists → extend/reuse instead of duplicate
4. If code will be used by 2+ features → create it in

   modules/cores/

   directly
5. Extract repeated logic (3+ occurrences) into shared helpers
6. Run

   npx jscpd ./src --threshold 3

   after creating new files

Agent Workflow (MANDATORY)

TeamCreate

1. fuse-ai-pilot:explore-codebase - Analyze project structure and existing patterns
2. fuse-ai-pilot:research-expert - Verify latest docs for all stack technologies
3. mcp__context7__query-docs - Check integration compatibility

Absolute Rules (MANDATORY)

1. Files < 100 lines

• Split at 90 lines - Never exceed 100
• Components < 50 lines (use composition)
• Hooks < 30 lines each
• Services < 40 lines each

2. Modular Architecture

references/architecture-patterns.md

3. JSDoc Mandatory

/**
 * Fetch user by ID from API.
 *
 * @param id - User unique identifier
 * @returns User object or null if not found
 */
export async function getUserById(id: string): Promise<User | null>

4. Interfaces Separated

modules/[feature]/src/interfaces/
├── user.interface.ts
├── post.interface.ts
└── api.interface.ts

SOLID Principles (Detailed Guides)

1. references/single-responsibility.md

   - One function = one reason to change
   • File splitting at 90 lines (components < 50, hooks < 30)
   • Component composition patterns
   • Split strategy

2. references/open-closed.md

   - Extend via composition, not modification
   • Plugin architecture patterns
   • Render props and slots
   • Strategy patterns

3. references/liskov-substitution.md

   - Contract compliance & behavioral subtyping
   • Interface contracts
   • Swappable implementations
   • Testing compliance

4. references/interface-segregation.md

   - Many focused interfaces beat one fat interface
   • Role-based interfaces
   • Props segregation
   • Context splitting

5. references/dependency-inversion.md

   - Depend on abstractions, not implementations
   • Constructor injection patterns
   • Factory patterns
   • Context for DI

references/solid-principles.md

Code Templates

references/templates/

component.md

hook.md

service.md

store.md

interface.md

validator.md

factory.md

adapter.md

error.md

test.md

Response Guidelines

1. Research first - MANDATORY: Search Context7 + Exa before ANY code
2. Show complete code - Working examples, not snippets
3. Explain decisions - Why this pattern over alternatives
4. Include tests - Always suggest test cases
5. Handle errors - Never ignore, use error boundaries
6. Type everything - Full TypeScript, no

   any

7. Document code - JSDoc for complex functions

Forbidden

• Coding without researching docs first (ALWAYS research)
• Using outdated APIs without checking current year docs
• Files > 100 lines
• Interfaces in component files
• Business logic in components
• Class components
• Missing JSDoc on exports

• any

  type
• Barrel exports (index.ts re-exports)

• useEffect

  for data fetching (use TanStack Query or Router loaders)
• Module importing another module (except cores)
• Duplicating existing utility/helper without Grep search first
• Copy-pasting logic blocks instead of extracting shared function