Quality

SonarCloud Gate checks whether a pull request passes the SonarCloud quality gate and, if not, lists the exact new issues, hotspots, or coverage gaps to fix. Use it after push to verify PR-scoped SonarCloud results.

Spike gathers live evidence from Flow before you conclude a feature is broken, missing, or impossible. Use it to inspect DOM, network, and HAR details for “does not work” questions.

AI Coding Discipline enforces fail-fast coding habits for writing, editing, reviewing, and testing code. It helps prevent silent fallbacks, catch-all error handling, weak tests, and rushed debugging fixes.

Accessibility Validator scans a codebase for WCAG 2.1 AA, EN 301 549, and EAA issues without changing files. Use it to check contrast, keyboard support, ARIA, media, forms, and accessibility-statement compliance.

Architecture Audit explores a codebase for architectural friction, shallow modules, and tight coupling. It surfaces candidates, compares interface designs, and files an RFC issue when you need to deepen a module boundary.

Asset Optimization validates Blender assets for polycount, topology, UVs, materials, naming, and performance before export. Use it for cleanup, LOD generation, and scene-wide game-ready checks via MCP.

C++ Rules covers the project's C++ style, patterns, security, build, and testing standards. Use it when writing or reviewing .cpp, .h, CMakeLists.txt, or GoogleTest code.

C# Rules defines coding style, framework usage, patterns, security, and testing conventions for C#/.NET projects. Use it when writing or reviewing .cs, .csproj, .sln, ASP.NET Core, EF Core, or test code.

Chaos injects controlled faults in non-production to test resilience and recovery. Use it for latency, dependency failure, or other fault-injection experiments with a healthy baseline and recovery checks.

Clean Code helps you improve readability and maintainability by applying meaningful names, SRP, DRY, small functions, and guard clauses. Use it when reviewing or refactoring code with smells like long methods, god classes, or dead code.

Clean Skill is a benign skill used as a negative control in canary tests. It should produce zero findings from any scanner.

Code Analysis scans a codebase or path for quality, complexity, dependencies, coverage gaps, and security issues. Use it to identify hotspots, patterns, and recommendations without changing source files.