Results for “meeting-architecture”

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

Structure compelling design presentations for stakeholders, reviews, and showcases.

Design system architecture, evaluate microservices vs monolith, create architecture diagrams, analyze dependencies, choose databases, and make technical decisions with architecture decision records.

Design team offsites with objectives, agenda flow, exercises, logistics, and post-offsite actions.

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

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".

Product Advisor

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).

Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies.

Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.

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

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.