Results for “jargon”

Extracts and formalizes domain terminology from a conversation into a consistent glossary saved to a local file.

Establish clear naming conventions for design assets, components, and tokens to make design systems predictable and maintainable.

Maintains a project's domain vocabulary and records architecturally-significant decisions as they're made — a CONTEXT.md glossary and gated ADRs, not passive documentation read once. Use when terminology conflicts or turns fuzzy, when making a decision that's hard to reverse/surprising/a real trade-off, or when a stated domain rule doesn't match what the code actually does.

Look up the precise term for a web animation or motion effect from a vague description, such as 'the bouncy thing when a popover opens' → 'Pop in'.