simq-dev

Guides adding pillars, scoring rules, and debugging scores in the simulation_quality subsystem.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill simq-dev-ttnhan18062000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simq-dev
Source: https://github.com/ttnhan18062000/rpg-based-simulation/tree/main/.agents/skills/simq-dev
Command: npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill simq-dev-ttnhan18062000

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about simq-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new pillar to the simulation_quality scoring system?

Follow the 9-step protocol: add the PillarId enum entry, PILLAR_METADATA, a scoring_weights.yaml section, a default profile weight, a PillarScorer subclass, QualityHub registry entry, scenario registry rows, and unit tests. Never use numeric literals in scorer code — always read self.weights rule keys.

How do I add a scoring rule to an existing SimQ pillar?

First check the scenario registry for conflicts, then add the rule's delta key to scoring_weights.yaml under that pillar and reference it via self.weights in the scorer. Add the tag documentation, a scenario row if new, and a unit test with an injected ScoringWeights fixture.

Why is a SimQ pillar score unexpectedly high or wrong?

Start with that pillar's scorer test file under tests/simulation_quality/, then check test_scorer_pillar_binding.py for weight-lookup issues. A known unresolved bug makes EconomyScorer double-score paid_info_transaction, inflating ECONOMY raw_score.

Can the same event type score in two SimQ pillars?

Only when it maps to two scenarios with different primary pillars, such as paid_info_transaction scoring in INFORMATION with a documentary-only secondary in ECONOMY. ScoringWeights.for_pillar ensures each pillar reads its own declared delta for shared rule keys.

What is the difference between simq-dev and simq-audit?

simq-dev covers development and debugging: adding pillars, adding scoring rules, and diagnosing wrong scores. simq-audit covers the governance workflow — recalibration, drift classification, and grade-anchor audits. They address different lifecycle phases without overlap.