# Semantic Anchor Translator

Bi-directional translator between verbose descriptions and established terminology...

- Repository: https://github.com/LLM-Coding/Semantic-Anchors (530 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add LLM-Coding/Semantic-Anchors --skill semantic-anchor-translator -g -a claude-code -y`
Codex: `npx skills add LLM-Coding/Semantic-Anchors --skill semantic-anchor-translator -g -a codex -y`
Cursor: `npx skills add LLM-Coding/Semantic-Anchors --skill semantic-anchor-translator -g -a cursor -y`
Gemini CLI: `npx skills add LLM-Coding/Semantic-Anchors --skill semantic-anchor-translator -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add LLM-Coding/Semantic-Anchors`

## Description

Bi-directional translator between verbose descriptions and established terminology (semantic anchors). Use when (1) user describes a concept verbosely and you want to identify the precise term, or (2) user asks for methodology/approach and you want to suggest relevant anchors. Covers 200+ terms across testing, architecture, design principles, problem-solving, requirements, documentation, communication, development workflow, statistical methods, strategic planning, and creative writing.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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](references/catalog.md)

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

## Quick Category Index

The rest: https://github.com/LLM-Coding/Semantic-Anchors/blob/HEAD/plugins/semantic-anchors/skills/semantic-anchor-translator/SKILL.md