api-response-optimization
Optimize API response times through caching, compression, and efficient payloads. Improve backend performance and reduce network traffic.
symfony:strategy-pattern
Implement the Strategy pattern with Symfony's tagged services for runtime algorithm selection and extensibility
symfony:cqrs-and-handlers
Implement CQRS pattern in Symfony with separate Command and Query handlers using Messenger component
symfony:interfaces-and-autowiring
Master Symfony's Dependency Injection with autowiring, interface binding, service decoration, and tagged services for flexible architecture
symfony:ports-and-adapters
Implement Hexagonal Architecture (Ports and Adapters) in Symfony; separate domain logic from infrastructure with clear boundaries
symfony:brainstorming
Structured brainstorming techniques for Symfony projects - explore requirements, identify components, and plan architecture collaboratively
symfony:controller-cleanup
Refactor fat controllers into lean controllers by extracting business logic to services, handlers, and dedicated classes
symfony:value-objects-and-dtos
Design Value Objects for domain concepts and DTOs for data transfer with proper immutability and validation
octave-mastery
Advanced semantic vocabulary and architectural patterns for the OCTAVE format. REQUIRES octave-literacy to be loaded first
mcaf-adr-writing
Create or update an ADR (Architecture Decision Record) under `docs/ADR/` using `docs/templates/ADR-Template.md`: context, decision, alternatives, consequences, rollout, and verification. Use when changing architecture, boundaries, dependencies, data model, or cross-cutting patterns; ensure it is self-contained, has a Mermaid diagram, and defines testable invariants.
mcaf-architecture-overview
Create or update `docs/Architecture/Overview.md` (architecture diagrams): maintain Mermaid diagrams for system/modules, interfaces/contracts, and key classes/types; document dependency rules; link to ADRs/features. Use when onboarding, refactoring, or adding modules/boundaries.
architecture-pattern-selector
Recommend architecture patterns (monolith, microservices, serverless, modular monolith) based on scale, team size, and constraints. Use when cto-architect needs to select the right architectural approach for a new system or migration.
scalability-advisor
Guidance for scaling systems from startup to enterprise scale. Use when planning for growth, diagnosing bottlenecks, or designing systems that need to handle 10x-1000x current load.
discover-distributed-systems
Automatically discover distributed systems skills when working with consensus, CRDTs, replication, partitioning, and distributed algorithms
dojo-model
Create Dojo models for storing game state with proper key definitions, trait derivations, and ECS patterns. Use when defining game entities, components, or state structures.
elixir-architect
Use when designing or architecting Elixir/Phoenix applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models with Ash Framework, structuring multi-app projects with path-based dependencies, or preparing handoff documentation for Director/Implementor AI collaboration
designing-apis
Designs REST and GraphQL APIs including endpoints, error handling, versioning, and documentation. Use when creating new APIs, designing endpoints, reviewing API contracts, or when asked about REST, GraphQL, or API patterns.
designing-architecture
Designs software architecture and selects appropriate patterns for projects. Use when designing systems, choosing architecture patterns, structuring projects, making technical decisions, or when asked about microservices, monoliths, or architectural approaches.
Page 13 of 14 · 249 results