What problem does it solve? Developers working on the simulation_quality (SimQ) scoring subsystem need a precise protocol for adding new pillars, adding scoring rules to existing pillars, and diagnosing why a pillar's score came out wrong — without violating the subsystem's conflict-detection and weight-scoping contracts. ## Core Features & Use Cases - New Pillar Protocol: A 9-step procedure covering the PillarId enum, PILLAR_METADATA, scoring_weights.yaml, profile weights, scorer implementation, QualityHub registry, scenario registry, and unit tests. - Scoring Rule Addition: Steps for adding rule deltas to an existing pillar with pillar-scoped weight lookup via PillarWeightsView, plus conflict detection rules (dual-ownership, duplicate signals, delta polarity). - Score Debugging Map: Pointers to the exact test files (per-pillar scorer tests, pillar-binding regression tests, hub and kernel integration tests) for diagnosing wrong scores, including a known unresolved EconomyScorer divergence. - Use Case: A developer sees an unexpectedly high ECONOMY score and uses this Skill to trace it to the known paid_info_transaction double-scoring issue flagged in TCK-20260714-SIMQ-WEIGHTS-PILLAR-COLLISION. ## Quick Start Ask the AI to walk you through adding a new scoring rule to an existing SimQ pillar, or to help debug why a specific pillar's score is wrong.