Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.
WHAT YOU GET
Files, tags and the three-step install
Tip: Read the documentation and the code before first use, so you know what it does and which permissions it needs.
NEXT SCRIPTS
Recommended based on tags and category
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Use when designing or reviewing REST endpoints, resource names, status codes, pagination, or versioning.
A built-in API automation authoring skill for the test-automation project, located at `.claude/skills/api-test-E10/`. It is used to add, maintain, backfill, and migrate API test methods and pytest cases under `\test-automation\E10自动化\接口自动化测试`, covering scenarios such as adding new methods or cases, backfilling uncovered APIs based on Java Controller source or Jacoco reports, maintaining existing methods and cases, completing parameterization, fixing assertions, inserting code at specified locations, finding duplicate implementations by URL, handling UTF-8 Chinese encoding, and running pytest with iterative real-error fixing until pass. Runtime artifacts are placed in the project root under `api_test_dwp_temp/`.