What problem does it solve? In FutureFin, every KPI shown to users has a prose description in apps/web/src/lib/helpTexts.ts explaining what it measures, its basis, and its window. When code changes silently alter a metric's meaning (its base, window, denominator, or exclusions), the help text drifts and users see contradictory numbers. This Skill enforces a merge gate so metric semantics and their catalog entries never diverge. ## Core Features & Use Cases - Merge gate for metric semantics: Any change to a metric's base, window, denominator, exclusions, mode dependency, or naming must end in an updated catalog entry, an added/removed entry, or a reasoned n/a in the commit body. - Entry authoring rules: Defines the <view>.<metric> id format, title and body length constraints, plain-Spanish style without implementation jargon, and the requirement to state what a metric is NOT when it resembles another. - Coverage test guidance: Explains the bidirectional test in helpTexts.test.ts that catches icons pointing to missing texts and orphaned texts without consumers. - Use Case: You change the savings card in Movements to use income_avg - expense_avg instead of summing savings-kind transactions. This Skill tells you to update expenses.savings, retire the old entries, and verify with the coverage test. ## Quick Start Ask the AI to review your metric change against the helpTexts catalog and update the affected entries before merging.
