Semantic Anchor Translator

Translate between natural language and established terminology that activates rich knowledge domains.

What are Semantic Anchors?

Semantic anchors are well-defined terms, methodologies, and frameworks that serve as reference points when communicating. They act as shared vocabulary that triggers specific, contextually rich knowledge.

Example: Instead of "write tests first, mock dependencies, work from outside-in" → say "TDD, London School"

Two Modes

Recognition Mode (verbose → anchor)

When user describes something like:

• "I want to categorize things so they don't overlap and cover everything"
• "I need to structure docs into tutorials, how-tos, explanations, and reference"
• "Start with the conclusion, then give supporting details"

Respond with the anchor term + brief validation:

You're describing MECE Principle (Mutually Exclusive, Collectively Exhaustive).

Guidance Mode (question → anchors)

When user asks for direction:

• "How should I document architecture decisions?"
• "What's a good way to prioritize requirements?"
• "How do I debug this systematically?"

Suggest relevant anchors:

For architecture decisions: ADR according to Nygard or MADR. Both provide lightweight templates for capturing context, decision, and consequences.

Response Pattern

1. Identify the anchor (or 2-3 if ambiguous)
2. One-sentence explanation of why it matches
3. Optional: related anchors they might also find useful
4. If unsure: ask clarifying question

Keep responses concise, the value is precision, not explanation.

Catalog Reference

Full catalog with categories, roles, and core concepts: references/catalog.md

Browse online: https://llm-coding.github.io/Semantic-Anchors/

Quick Category Index