evanflow-glossary

Extract canonical domain terms from conversations and code into CONTEXT.md.

417|18|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/evanklem/evanflow --skill evanflow-glossary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evanflow-glossary
Source: https://github.com/evanklem/evanflow/tree/main/skills/evanflow-glossary
Command: npx skills add https://github.com/evanklem/evanflow --skill evanflow-glossary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It extracts canonical domain terms and flags ambiguities (same word, different meanings) and synonyms (different words, same meaning), enabling a consistent CONTEXT.md as terminology evolves.

Core Features & Use Cases

  • Extract nouns, verbs, and relationships from conversations and code to populate CONTEXT.md.
  • Flag conflicts where a term has multiple canonical meanings and identify synonyms to streamline terminology.
  • Re-invoke updates to refresh CONTEXT.md with the latest domain terms as new terms emerge in dialogue or code.

Quick Start

Update CONTEXT.md by extracting current domain terms from ongoing discussions and code and merge them into the existing glossary.

Frequently Asked Questions about evanflow-glossary

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

FAQPage Schema
How do I unify domain terminology and manage synonyms in my project?

To unify domain terminology, extract canonical terms from conversations and code to consolidate them into CONTEXT.md. This flags synonyms and ambiguities, ensuring consistent project language as terminology evolves over time.

What is the best way to audit CONTEXT.md for domain language ambiguities?

Auditing CONTEXT.md for ambiguities involves scanning canonical terms to flag conflicts where a single word has multiple meanings. It also identifies synonyms where different words share the same meaning to streamline terminology.

How do I extract canonical domain terms from ongoing discussions and code?

Extracting canonical domain terms involves analyzing nouns, verbs, and relationships from current conversations and code. This populates CONTEXT.md by merging newly identified terms into the existing glossary.

Does updating CONTEXT.md preserve existing canonical terms when merging new vocabulary?

Updating CONTEXT.md preserves existing canonical terms during the merge process. It flags conflicts from newly extracted terms and consolidates terminology across invocations to maintain a consistent glossary.

When do I need to re-invoke terminology extraction to refresh my project glossary?

You need to refresh your project glossary when new domain terms emerge in dialogue or code. Re-invoking the extraction process updates CONTEXT.md by merging the latest terminology while flagging any new conflicts.