Results for “architecture-fitness”

Estructura aplicaciones Flutter en módulos independientes y reutilizables con flutter_modular, incluyendo diseño de paquetes, dependencias y configuración de Melos.

Organizes Flutter code into domain, data, and presentation layers with unidirectional dependencies, using BLoC, use cases, and repository patterns for testable, maintainable enterprise applications.

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

Organizes Flutter code by business features instead of technical layers, with self-contained folders for UI, logic, and data, plus a recommended project structure and dependencies.

Applies SOLID principles, clean architecture layers, dependency injection, and patterns like CQRS and event sourcing to design scalable, maintainable systems.

Guides module boundaries, dependency direction, and domain structure. Do not use for local edits that leave architecture unchanged.

Guides structuring backend services with hexagonal architecture, separating domain, application, and infrastructure layers with ports and adapters.

Structure software around the Dependency Rule so that source code dependencies point inward from frameworks to use cases to entities, keeping business rules independent of databases, UI, and external agencies.

Designs application architecture, selects patterns, structures code modules, and manages dependencies for new projects.

Enforces system design, project structure, dependency management, error handling, testing, and documentation standards at principal-engineer level.

Three shapes get argued about as if one were correct.

Compare tradeoffs and recommend architectural patterns — dependency injection, service-oriented architecture, repository, domain events, circuit breaker, and anti-corruption layer. Use when choosing between design patterns, planning microservices boundaries, evaluating system design alternatives, or asking 'which pattern should I use' for a specific coupling or resilience problem.

Log workouts, plan routines, track progress, and get intelligent coaching for any fitness level.

Eng manager-mode plan review. (gstack)

Implements offline-first architecture in Flutter apps with local caching, bidirectional sync, connectivity detection, and conflict resolution.

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".