What problem does it solve? Maintainers of the Optimization Compass knowledge base need a controlled, validated way to add or revise comparison entries (Compare definitions) without inventing new traces, renderer contracts, or breaking the published schema. ## Core Features & Use Cases - Guided editing workflow: Copies the closest existing comparison entry in data/seeds/site_comparisons.json by mode and rewrites it, keeping the validated schema intact. - Reuse enforcement: Requires reusing existing traces, visualization scenarios, problem definitions, benchmark contexts, and method IDs; stops if new renderer contracts are needed. - Validation gates: Runs optimization-compass validate comparison, with tier-b as the PR gate and tier-c (including E2E) when routes or interactions change. - Use Case: A contributor wants to add a new method comparison for an existing problem archetype; the skill walks them through copying a matching entry, editing fields, validating, and documenting ranking_eligible reasoning in the PR. ## Quick Start Add a new comparison entry to site_comparisons.json for the existing gradient descent versus Newton method scenario and validate it with the comparison validator.
