Quality

Test Writer generates comprehensive tests for existing code. Use it to read a codebase, match its test framework, and write coverage for happy paths, edge cases, errors, and integration behavior.

Verification Strategy helps you confirm a task is complete by checking requirements, file outputs, commands, and test expectations before marking work done. Use it when you need to validate code or generated artifacts against exact instructions.

Biomedical Paper Evidence Audit reviews life science or biomedical papers, figures, captions, and screenshots to identify the main claim and inspect the evidence chain. It is used to analyze mechanisms, causality, rescue experiments, method limits, and missing controls when source material is available.

Figure Duplicate Audit reviews scientific figures for duplicated, reused, transformed, or uninformative panels. Use it on PDFs or manuscript image directories when checking figure reuse, page selections, or panel-level integrity.

Figure Style checks publication figures for correctness and legibility before plotting. It provides a Matplotlib styling helper plus render-and-inspect QA for labels, layout, colours, and multi-panel crops.

App Store Review Preparation audits submission readiness and rejection risk for iOS apps. Use it to check privacy manifests, ATT, StoreKit, entitlements, metadata, widgets, and Live Activities before submitting or after a rejection.

API Design Safety helps you design REST API responses and generated outputs with consistent field semantics, null handling, and status codes. It also checks required fields before exporting files or sending downstream payloads to avoid silent failures.

Code Quality Principles provides a checklist for modular design, refactoring, and code review. Use it to assess module size, call depth, fan-in/fan-out, boundaries, scope cohesion, and predictability.

External System Debugging helps debug code that depends on browsers, editors, CDNs/WAFs, IM platforms, clipboards, or third-party SaaS. It requires collecting real environment data first, then using that evidence to diagnose paste, rendering, API, and cross-platform issues.

Field Mapping Safety prevents mistakes when refactoring table columns, enum maps, and type conversions. It is used to verify real field names and complete mappings before changing code.

Field Mapping Safety helps prevent incorrect field-name guesses when refactoring table columns, enum mappings, and data transforms. Use it when similar fields or incomplete mappings could cause runtime blanks or Invalid Date issues.

Go Development Standards describes naming, error handling, concurrency, testing, and performance practices for Go code. Use it when writing or reviewing Go services and libraries.