Quality

Java Development Standards defines naming, exception handling, null handling, concurrency, testing, and Spring Boot practices for Java code. Use it when writing or reviewing Java services and data access code.

Multi-Tenant Safety covers checks for tenant isolation in multi-tenant systems. Use it when code touches TenantContext, tenantId, tenant headers, filters, or repository access to prevent cross-tenant data leaks.

Python Dev provides Python coding standards for style, type hints, error handling, logging, testing, and project structure. Use it when writing or reviewing Python code that should follow consistent conventions.

Redis Safety provides security and performance rules for Redis usage across languages. Use it when working with go-redis, Jedis, redis-py, or ioredis to avoid blocking commands, large keys, and missing TTLs.

Refactor Safety provides a checklist for code refactors so you can preserve original structure, branches, and data while changing implementation. Use it when extracting components, merging logic, renaming fields, or simplifying conditionals.

Size Check reviews changed code for reuse, quality, and efficiency, then flags issues to fix. It also scans project files for line-count limit violations and CSS extraction needs.

EMC Pre-Compliance analyzes KiCad PCB designs for EMC and EMI risk before fabrication. It flags likely emissions and immunity issues, ranks severity, and generates a pre-compliance test plan.

KiCad Analyzer reviews KiCad projects and PDF schematics to trace nets, check DRC/ERC, extract BOM data, and compare schematic, PCB, and fabrication files. Use it when reviewing a board before fab or debugging a hardware design.

SPICE Simulation generates and runs SPICE testbenches for KiCad subcircuits detected by schematic analysis. Use it to verify filter cutoffs, divider ratios, op-amp gain, LC resonance, and similar analog behavior.

Prepare AAAI artifact packages (code, data, appendices) for reproducibility while maintaining double-blind submission rules. Avoid common mistakes that lead to summary rejection.

Audit an AAAI paper's reproducibility checklist, experimental traceability, seed/hyperparameter reporting, compute disclosure, dataset licensing, and code readiness to survive AAAI's Phase-1 rigor review.

Audit an AAAI conference submission for compliance with OpenReview requirements, double-blind anonymity, page limits, reproducibility checklist, author limits, and AI-use policies to prevent desk rejection.