Quality

Figma Typings Audit diffs @figma/plugin-typings between installed and target versions, classifies breaking changes and new fields, and maps them to plugin, shared, and tool registry code. Use it when auditing or upgrading the package, including Renovate bumps.

MCP SDK Audit upgrades @modelcontextprotocol/server and checks whether the MCP wire contract changed. It is used when auditing SDK bumps by comparing protocol version, tool schemas, annotations, and prompts before and after the release.

Code Review reviews a Git diff against repository standards and the originating requirements. Use it for pull requests, branches, work-in-progress changes, or changes since a commit, tag, or merge-base.

Codebase Design helps you shape module interfaces using deep-module heuristics. Use it when choosing seams, reducing caller complexity, improving testability, or comparing alternative designs.

Diagnosing Bugs uses reproducible evidence, focused hypotheses, and targeted instrumentation to isolate hard bugs and performance regressions. Use it when something is broken, intermittent, or unexpectedly slow.

Test-Driven Development uses small red-green-refactor cycles to build or fix behavior test-first. Use it when you want integration tests, a failing-first loop, or a change guided by existing tests and repository conventions.

AC Criteria Validator checks implemented features against acceptance criteria and reports whether they pass. Use it to verify test results, code completeness, and other feature completion checks.

Acceptance Criteria generates testable Given/When/Then scenarios for a user story or feature slice. Use it when turning requirements into engineering handoff and QA sign-off criteria.

Edge Cases documents boundary conditions, error states, race conditions, and recovery paths for a feature. Use it during specification or QA planning to map what can go wrong and what should happen next.

Web App Testing uses Playwright to inspect and automate local web apps. Use it to verify frontend behavior, debug UI issues, capture screenshots, and read browser logs.

Java Coding Standards defines rules for writing, reviewing, and refactoring Java 17+ and Spring Boot code. Use it for layer design, API boundaries, persistence, transactions, logging, testing, and code review.

Acceptance Test Builder creates, updates, merges, retires, and runs scoped acceptance tests using project-native tooling. Use it when executable acceptance evidence must change, not for audits or product fixes.