VilnaCRM-Org

Systematically retrieve and address PR code review comments using make pr-comments. Use when handling code review feedback or addressing PR comments.

Codex entrypoint for post-implementation BMAD FR/NFR review gates. Use after a PR, feature, or bugfix has BMAD specs and must be checked against every functional requirement, non-functional requirement, expanded quality dimension, Wikipedia system quality attribute, generated positive/negative/ edge test case, automated test and CI coverage expectation, flaky-test risk, whole-codebase impact surface, manual-test expectation, GitHub review comments and requested-changes state, and CI check before completion.

Run a BMAD spec-driven post-implementation review gate. Use after implementing a GitHub PR, feature, bugfix, or task with BMAD specs to verify every FR/NFR, pinned NonFunctionals.com NFR category, expanded quality dimension, Wikipedia system quality attribute, positive/negative/edge test case, automated test and CI coverage expectation, flaky-test risk, whole-codebase impact surface, manual test expectation, QA best practice, GitHub review comments and requested-changes state, and CI check before completion.

Design LLM-powered modules with Clean Architecture boundaries, SOLID, DRY, KISS, and provider-agnostic ports/adapters. Use when adding prompt workflows, model/provider clients, tool orchestration, AI review automation, agent skills, or other LLM-backed capabilities.

advanced elicitation. Use when the user asks about advanced elicitation.

adversarial review. Use when the user asks about adversarial review.

Research, briefs, discovery. Use when the user asks about analyst.

Technical design, architecture. Use when the user asks about architect.

Run comprehensive CI checks before committing changes. Use when the user asks to run CI, run quality checks, validate code quality, or before finishing any task that involves code changes.

Ensure proper code organization with class names, directories, namespaces, and naming consistency following the principle "Directory X contains ONLY class type X".

Design and implement DDD patterns (entities, value objects, aggregates, CQRS). Use when creating new domain objects, implementing bounded contexts, designing repository interfaces, or learning proper layer separation. For fixing existing Deptrac violations, use the deptrac-fixer skill instead.

Implement production-grade caching with cache keys/TTLs/consistency classes per query, SWR (stale-while-revalidate), layered explicit invalidation, and comprehensive testing for stale reads and cache warmup. Use when adding caching to queries, implementing cache invalidation, or ensuring cache consistency and performance.

Systematically retrieve and address PR code review comments using make pr-comments. Enforces DDD architecture, code organization principles, and quality standards. Use when handling code review feedback, refactoring based on reviewer suggestions, or addressing PR comments.

Guide for contributing to the OpenAPI layer using processor pattern, complexity management, and functional programming. Use when adding endpoint factories, processors, parameter descriptions, reducing cyclomatic complexity, or fixing OpenAPI validation errors. Covers architecture patterns from user-service repository.

Portable autonomous BMALPH planning for Codex. Use when the user wants specs from a short task description and expects the current AI session to orchestrate BMALPH subagents without human interaction.

BMAD master agent — navigate phases. Use when the user asks about bmalph.

Use BEFORE building or changing any UI — components, layout, color, spacing, typography, interaction states, or visual styling — to verify the planned change matches the Figma design via the Figma MCP. Run this gate before writing or editing UI code.

Use when placing features, repositories, hooks, or fixing dependency-cruiser errors.

Use when validating frontend changes before commit, push, or PR.

Use when placing, moving, naming, or splitting frontend files.

Use when retrieving or addressing PR review comments.

Use when frontend files, components, hooks, or helpers exceed complexity gates.

Use when creating new repository documentation or agent guides.

Use when code, commands, tools, or workflows change documentation obligations.

Add or extend API Platform resources in php-service-template using DDD and CQRS-friendly patterns.

Run the current php-service-template verification stack and fix failures without lowering quality thresholds.

Preserve PHPInsights quality standards for php-service-template without lowering thresholds.

Fix architectural boundary violations without editing deptrac.yaml.

Keep template-facing documentation and generated artifacts aligned with code changes.

Create or update K6-based load tests in php-service-template.

Maintain exported OpenAPI and GraphQL snapshots for php-service-template.

Reference the current protected quality gates for php-service-template.