Evanflow Glossary

Community

evanklem

evanflow-glossary

Extract canonical domain terms into CONTEXT.md. Flag ambiguities (same word, different meanings) and synonyms (different words, same meaning). Re-invoking updates the file in place. Use when authoring or updating CONTEXT.md, or when a new domain term emerges in conversation.

Overview

Publisher	evanklem
Repository	`evanflow`
Skill name	`evanflow-glossary`
Stars	418
Forks	18
Bundled files	Instructions only
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by evanklem on GitHub. Read the source before you install it.

Installation

Install the Evanflow Glossary AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/evanklem/evanflow/tree/main/skills/evanflow-glossary
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/evanklem/evanflow.git /tmp/evanflow
mkdir -p .claude/skills
cp -r /tmp/evanflow/skills/evanflow-glossary .claude/skills/evanflow-glossary

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Evanflow Glossary in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Evanflow Glossary on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Evanflow Glossary is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

EvanFlow: Ubiquitous Language

Vocabulary

See evanflow meta-skill.

When to Use

Authoring CONTEXT.md for the first time (Phase B of EvanFlow rollout)
A new domain term emerged in conversation and should be added
Auditing existing terminology for ambiguity (same word, multiple meanings) or synonyms (different words, same meaning)
Before any architectural conversation that depends on shared language

The Flow

1. Read Current State

If CONTEXT.md exists: read it. Identify clusters and gaps.
Read recent code in the relevant area: router file, service file, schema, page. Names in code are the de facto terminology.
Read recent ADRs in docs/adr/ for terms decided there.

2. Extract Terms

Walk the conversation + relevant code. Pull out:

Nouns — entities and value objects in your domain
Verbs — domain operations (e.g., negotiate, queue, withdraw, settle, escalate)
Status enums — explicit lifecycle states (e.g., OrderStatus, MessageStatus)
Relationships — cardinalities between entities (one-to-many, many-to-many)

3. Flag Conflicts

Two questions to ask the user for each conflict:

Ambiguity: "The word X is used for both A and B. Which canonical meaning, and what should the other one be renamed to?"
Synonyms: "The codebase uses both User and Account for the same concept. Which is canonical? The other becomes a deprecated alias."

Propose recommended answers. Don't just dump the conflicts on the user.

4. Write CONTEXT.md

Default location: /CONTEXT.md at repo root. (Mattpocock convention.)

Format:

markdown
# <Project> Domain Language

## <Cluster Name> (e.g., "Identity & Accounts")

| Term | Definition (one sentence) | Aliases to avoid |
|---|---|---|
| **User** | Canonical noun for an authenticated account. | Account (legacy), Customer (billing-layer only) |
| **Category** | A primary classification used for matching/filtering. | Type, Tag, Vertical |

## <Next Cluster>

...

## Relationships

- **EntityA** → **EntityB**: many-to-many via a join table.
- **EntityA** → **EntityC**: one-to-many; EntityCs are managed by an automated process.

5. Re-invoke Behavior

If CONTEXT.md already exists:

Read it
Add new terms in their existing cluster (or create a new cluster)
Update evolved definitions
Refresh the example dialogue if present
Don't duplicate; merge

Hard Rules

One sentence per definition. If you need a paragraph, the term is too vague — split it.
Domain terms only. Skip generic programming concepts (function, class, etc.).
Be prescriptive. Pick canonical synonyms; don't list every variant as equally valid.
Cardinality in bold. "User has many Orders."
Never auto-commit. Append CONTEXT.md changes to a stage; ask before commit.

Hand-offs

New ADR needed (decision behind a term) → write under docs/adr/
Terms reveal architectural friction → evanflow-improve-architecture

Frequently asked questions

What does the Evanflow Glossary AI skill do?

Why use Evanflow Glossary on TypingMind?

Because you install it once and use it with any model. Evanflow Glossary is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Evanflow Glossary in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/evanklem/evanflow/tree/main/skills/evanflow-glossary. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Evanflow Glossary?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Evanflow Glossary?

As many as you like. As long as a model supports skills, you can use Evanflow Glossary with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Evanflow Glossary AI skill free?

It is published on GitHub by evanklem. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Solid

openclaw

OrganizationPopular

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Auto Qa

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

EvanFlow: Ubiquitous Language

Vocabulary

When to Use

The Flow

1. Read Current State

2. Extract Terms

3. Flag Conflicts

4. Write CONTEXT.md

5. Re-invoke Behavior

Hard Rules

Hand-offs

Frequently asked questions

Related AI Skills

Set up your own AI workspace now