Loading...
Loading...
Found 5 Skills
Enforce separation of concerns by separating the view from the application logic.
Use when designing modules, APIs, and system architecture requiring independent, non-overlapping components where changes in one don't affect others.
Relentlessly critiques code against classic software engineering principles (SOLID, separation of concerns) to prevent "clever process shenanigans" and spaghetti code. Use before finalizing a feature or opening a PR.
Teaches the container/presentational pattern for Vue components. Use when you want to separate data fetching and business logic from presentation for better testability and reuse.
Apply factory function patterns to compose clients and services with proper separation of concerns. Use when creating functions that depend on external clients, wrapping resources with domain-specific methods, or refactoring code that mixes client/service/method options together.