What problem does it solve? Research projects drift when the same concept gets different names in code identifiers, contract fields, paper prose, and result keys. This Skill sharpens or changes ambiguous TDA (topological data analysis) terminology so one precise vocabulary holds across code, contracts, vault notes, papers, and agent prompts. ## Core Features & Use Cases - Term Resolution Procedure: States the conflicting term and every place it appears, checks existing usage in CONVENTIONS.md, notation files, and contracts, then proposes one canonical term with rejected alternatives recorded. - Canonical Term Guards: Protects fixed vocabulary such as Markov order k, W2 (Wasserstein-2), persistence landscape L2, pvalue_null_draws vs effect_null_pairs, and frozen vs re-fit PCA loadings. - Edge-Case Stress Testing: Validates proposed terms against 2-4 concrete cases before locking them at the right documentation level (code comment, glossary, paper notation, or contract term). - Use Case: A result field names a quantity unclearly and a code identifier conflicts with project vocabulary; use this Skill to pick one canonical term, test it against edge cases, and update the right documentation file. ## Quick Start Resolve the ambiguous term in my draft by checking existing usage across code, contracts, and papers, then propose one canonical term and update the appropriate documentation.
