Architecture

Layered architecture organizes code into presentation, business logic, data access, and external services layers. It enforces separation of concerns and clear dependency direction, ensuring maintainable and scalable software systems during large refactors.

Structure feature-based modules by aligning components to architectural layers and outlining clear module boundaries. This approach manages state, dictates dependency direction, and ensures cohesive, maintainable code organization across features and services.

Yes, this skill guides evaluating multiple technical approaches and architectural trade-offs during large refactors. It helps teams assess patterns, dependency injection, and separation of concerns to choose the most maintainable architectural path.

Organize state management and dependency direction using feature-based organization and dependency injection best practices. This skill prescribes clear module boundaries and layering to maintain strict separation of concerns across your software architecture.

Apply separation of concerns whenever creating new modules, evaluating technical approaches, or performing large refactors. This skill enforces dependency direction and layering to keep presentation, business logic, and data access distinctly maintainable.