From semantic-anchors
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 120+ terms across testing, architecture, design principles, problem-solving, requirements, documentation, communication, development workflow, statistical methods, strategic planning, and creative writing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/semantic-anchors:semantic-anchor-translatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Translate between natural language and established terminology that activates rich knowledge domains.
Translate between natural language and established terminology that activates rich knowledge domains.
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"
When user describes something like:
Respond with the anchor term + brief validation:
You're describing MECE Principle (Mutually Exclusive, Collectively Exhaustive).
When user asks for direction:
Suggest relevant anchors:
For architecture decisions: ADR according to Nygard or MADR. Both provide lightweight templates for capturing context, decision, and consequences.
Keep responses concise — the value is precision, not explanation.
Full catalog with categories, roles, and core concepts: references/catalog.md
Browse online: https://llm-coding.github.io/Semantic-Anchors/
| Category | Key Anchors |
|---|---|
| Testing & Quality | TDD Chicago/London, BDD, Gherkin, Test Double (Meszaros + 5 subtypes), Testing Pyramid, Mutation Testing, Property-Based Testing, Fagan Inspection, STRIDE, LINDDUN, LLM-Evaluations |
| Software Architecture | Clean Architecture, Hexagonal, DDD, EDA, CQRS, VSA, arc42, C4, ADR, MADR, ATAM, LASR, ISO 25010, OWASP Top 10 |
| Design Principles | SOLID (+ 5 individual), GRASP, CRC-Cards, GoF Patterns (23 patterns), Fowler PEAA, DRY, KISS, SPOT, SSOT, YAGNI |
| Problem-Solving | Five Whys, Feynman Technique, Rubber Duck, Devil's Advocate, Morphological Box, Chain of Thought, Cynefin |
| Requirements | INVEST, PRD, MoSCoW, EARS, User Story Mapping, JTBD, Impact Mapping, Problem Space NVC |
| Communication | BLUF, Pyramid Principle, MECE, Gutes Deutsch, Plain English, Chatham House Rule, Socratic Method, MBTI |
| Documentation | P.A.R.A., Diátaxis, Docs-as-Code |
| Development Workflow | GTD, Definition of Done, GitHub Flow, Conventional Commits, Effective Go, SemVer, BEM, Mikado Method, Hemingway Bridge |
| Statistical Methods | SPC, Control Chart, Nelson Rules |
| Strategic Planning | Wardley Mapping, Pugh Matrix, SWOT, PERT |
| Creative Writing | Three-Act Structure, Hero's Journey, Save the Cat!, Fichtean Curve, Freytag's Pyramid, Story Circle, Kishōtenketsu |
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
3plugins reuse this skill
First indexed Jul 18, 2026
npx claudepluginhub jensgrote/semantic-anchors --plugin semantic-anchors