AutoCode

Use when creating competitive programming problems with AutoCode MCP tools. Enforces the plugin workflow for problem statements, std/brute solutions, validators, generators, stress tests, final data verification, and Polygon packaging.

Validate statement samples and sample files for competitive programming problems. Ensures the expected outputs in problem statements match the actual solution output.

Verify final tests with hard quality gates: integrity, consistency, validator, limit semantics, and wrong-solution kill.

Turn deterministic problem_audit difficulty signals into a CF-style rating with reasons and confidence.

Audit statement, tutorial, and samples for consistency and publication readiness before packaging.

Define and enforce project-wide quality standards for agent and skill documents. Use when creating, reviewing, or refactoring files under agents/ and skills/ to keep structure, terminology, and output contracts consistent.

Audit std/brute assumptions with MCP evidence, including worst/average complexity risk and stress readiness.

Build multi-profile stress tests from brute complexity and constraints, then execute with traceable evidence.

Use before coding to decide whether a problem idea is judgeable, implementable, and verifiable.