From sophie
Use when presenting a governing equation or key relationship in a reading or lesson — enforces unpacking every symbol with BOTH meaning AND units, an explicit dimensional check, connecting the equation to an observable, and reading its structure (exponents/scaling); decides <KeyEquation> registry vs inline math and defers mechanics to the component reference.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sophie:equation-authoringThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
An equation is a **claim about how observables relate**, not a result to
An equation is a claim about how observables relate, not a result to plug into. Present it so the student can read it. The most common unaided failure: unpacking each symbol's meaning but skipping its units and the dimensional check — which leaves the equation abstract and unverifiable.
<KeyEquation refId="…">
registry (one canonical statement, cross-referenceable).$…$.docs/website/reference/chapter-components.md.Show units always and check dimensions always — but which system (CGS, SI, solar) is a course decision. Follow the course's voice/math-grammar; don't impose a unit system from here.
<KeyEquation>.See also figure-authoring (visualizing an equation) and the course's voice/math-grammar for the unit convention.
npx claudepluginhub drannarosen/sophie --plugin sophieProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.