logical-architecture-design

To enforce single responsibility principle, validate each frontend and backend component using explicit one-verb descriptions under 100 characters, flagging conjunctions and vague verbs during architecture design reviews.

SRP violation signals include component descriptions containing conjunctions, multiple items, vague verbs, or exceeding the 100-character limit, indicating the component handles multiple responsibilities and requires refactoring.

Refactor component architecture by applying concrete split strategies provided during validation failure, dividing multiple responsibilities into focused frontend and backend components that each have exactly one clear, well-defined purpose.

SRP validation works for both frontend and backend component refactoring, requiring explicit single-responsibility descriptions during architecture planning and design reviews to ensure maintainability and predictable changes across the stack.

The best way to validate component responsibilities is checking for single, well-defined purposes using one-verb descriptions, disallowing conjunctions, and flagging vague verbs to ensure maintainability and testability during refactor efforts.