fix: add German translation, changelog, metadata for Effective Go (#404)

Post-merge cleanup for PR #404:
- German translation (effective-go.de.adoc)
- Added related anchors (clean-code, conventional-commits)
- Changelog entry
- Regenerated metadata

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: raifdmueller

docs/all-anchors.adoc

@@ -127,6 +127,8 @@ include::anchors/conventional-commits.adoc[leveloffset=+2]
 
 include::anchors/definition-of-done.adoc[leveloffset=+2]
 
+include::anchors/effective-go.adoc[leveloffset=+2]
+
 include::anchors/github-flow.adoc[leveloffset=+2]
 
 include::anchors/mental-model-according-to-naur.adoc[leveloffset=+2]

docs/anchors/effective-go.adoc

@@ -1,6 +1,7 @@
 = Effective Go
 :categories: development-workflow
 :roles: software-developer, software-architect
+:related: clean-code, conventional-commits
 :proponents: The Go Authors
 :tags: go, golang, best-practices, idiomatic, style-guide
 :tier: 3

docs/anchors/effective-go.de.adoc

@@ -0,0 +1,46 @@
+= Effective Go
+:categories: development-workflow
+:roles: software-developer, software-architect
+:related: clean-code, conventional-commits
+:proponents: The Go Authors
+:tags: go, golang, best-practices, idiomatic, style-guide
+:tier: 3
+
+[%collapsible]
+====
+
+[discrete]
+== *Kernkonzepte*:
+
+Formatierung (gofmt):: Code wird automatisch formatiert; Stildiskussionen werden durch Tooling eliminiert
+
+Paketnamen:: Kurz, kleingeschrieben, keine Unterstriche; der Paketname ist Teil des qualifizierten Bezeichners
+
+Benannte Rückgabewerte:: Rückgabewerte können benannt und als Dokumentation verwendet werden
+
+Defer:: Verzögerte Funktionsaufrufe werden in LIFO-Reihenfolge ausgeführt, wenn die umgebende Funktion zurückkehrt; verwendet für Aufräumarbeiten (close, unlock)
+
+Goroutinen:: Leichtgewichtige, nebenläufig ausgeführte Funktionen; „Kommuniziere nicht durch gemeinsamen Speicher; teile Speicher durch Kommunikation"
+
+Channels:: Typisierte Kanäle für Goroutinen-Kommunikation; erstklassiges Synchronisierungsprimitiv
+
+Interfaces:: Implizite Erfüllung — ein Typ implementiert ein Interface, indem er einfach dessen Methoden implementiert; ermöglicht Duck Typing
+
+Fehlerbehandlung:: Fehler sind Werte; idiomatisches Muster ist `if err != nil` an jeder Aufrufstelle; keine Exceptions
+
+Blank Identifier (_):: Ungewollte Werte aus Multi-Value-Returns verwerfen, ohne Compilerfehler
+
+Embedding:: Komposition statt Vererbung; Typen können andere Typen einbetten, um deren Methoden zu erhalten
+
+Schlüsselvertreter:: The Go Authors (https://go.dev/doc/effective_go)
+
+[discrete]
+== *Wann zu verwenden*:
+
+* Einarbeitung neuer Go-Entwickler in idiomatischen Go-Stil
+* Code-Review-Diskussionen über Go-Konventionen
+* Etablierung teamweiter Go-Codierungsstandards
+* Erklärung von Go-Idiomen, die sich von anderen Sprachen unterscheiden (z.B. Fehlerbehandlung, Interfaces)
+* LLM-Prompting für idiomatischen, produktionsreifen Go-Code
+
+====

docs/changelog.adoc

@@ -2,6 +2,12 @@
 
 A chronological record of all semantic anchors added to the catalog. Community contributors are credited with thanks.
 
+== 2026-04-01
+
+*New anchors:*
+
+* *Effective Go* — The Go Authors' canonical guide to idiomatic Go
+
 == 2026-03-29
 
 *New category:* `Creative Writing & Storytelling`

website/public/data/anchors.json

@@ -451,7 +451,10 @@
       "software-developer",
       "software-architect"
     ],
-    "related": [],
+    "related": [
+      "clean-code",
+      "conventional-commits"
+    ],
     "proponents": [
       "The Go Authors"
     ],

website/public/data/metadata.json

@@ -1,15 +1,15 @@
 {
-  "generatedAt": "2026-03-29T19:29:34.681Z",
+  "generatedAt": "2026-04-01T08:18:02.208Z",
   "version": "1.0.0",
   "counts": {
-    "anchors": 121,
+    "anchors": 122,
     "categories": 14,
     "roles": 12
   },
   "statistics": {
-    "averageRolesPerAnchor": "3.15",
+    "averageRolesPerAnchor": "3.14",
     "averageCategoriesPerAnchor": "1.01",
-    "anchorsWithTags": 81,
-    "anchorsWithRelated": 52
+    "anchorsWithTags": 82,
+    "anchorsWithRelated": 53
   }
 }

website/public/data/roles.json

@@ -217,6 +217,7 @@
       "cynefin-framework",
       "devils-advocate",
       "domain-driven-design",
+      "effective-go",
       "event-driven-architecture",
       "fagan-inspection",
       "fowler-patterns",
@@ -291,6 +292,7 @@
       "definition-of-done",
       "docs-as-code",
       "domain-driven-design",
+      "effective-go",
       "event-driven-architecture",
       "fagan-inspection",
       "feynman-technique",

website/public/llms.txt

@@ -1,6 +1,6 @@
 # Semantic Anchors — Complete Reference
 
-> 122 well-defined terms, methodologies, and frameworks
+> 123 well-defined terms, methodologies, and frameworks
 > that serve as precision reference points when communicating with LLMs.
 > Source: https://github.com/LLM-Coding/Semantic-Anchors
 > Website: https://llm-coding.github.io/Semantic-Anchors/
@@ -1935,6 +1935,42 @@ A class should have only one reason to change. Each module or class should be re
 * User Story Mapping - Planning technique that identifies the scope Definition of Done must cover
 * MoSCoW - Prioritization method used to decide which DoD items are must-haves
 
+### Effective Go
+
+[discrete]
+## **Core Concepts**:
+
+***Formatting (gofmt)***: Code is auto-formatted; style debates are eliminated by tooling
+
+***Package names***: Short, lowercase, no underscores; package name is part of the qualified identifier
+
+***Named return values***: Return values can be named and used as documentation
+
+***Defer***: Deferred function calls run in LIFO order when the surrounding function returns; used for cleanup (close, unlock)
+
+***Goroutines***: Lightweight concurrently executing functions; "Don't communicate by sharing memory; share memory by communicating"
+
+***Channels***: Typed conduits for goroutine communication; first-class synchronization primitive
+
+***Interfaces***: Implicit satisfaction — a type implements an interface simply by implementing its methods; enables duck typing
+
+***Error handling***: Errors are values; idiomatic pattern is `if err != nil` at each call site; no exceptions
+
+***Blank identifier (_)***: Discard unwanted values from multi-value returns without compiler error
+
+***Embedding***: Composition over inheritance; types can embed other types to gain their methods
+
+***Key Proponent***: The Go Authors (https://go.dev/doc/effective_go)
+
+[discrete]
+## **When to Use**:
+
+* Onboarding new Go developers to idiomatic Go style
+* Code review discussions about Go conventions
+* Establishing team-wide Go coding standards
+* Explaining Go idioms that differ from other languages (e.g. error handling, interfaces)
+* Prompting an LLM to produce idiomatic, production-quality Go code
+
 ### GitHub Flow
 
 [discrete]
@@ -4947,7 +4983,8 @@ Select and download: https://llm-coding.github.io/Semantic-Anchors/#/contracts
 ## Specification
 
 When we talk about a "specification" or "spec", we mean:
-- Use Cases with Activity Diagrams (all paths, not just the happy path)
+- Use Cases with Trigger, Main Flow, Alternative Flows, Postconditions, and Business Rules (BR-IDs)
+- Activity Diagrams for all flows (not just the happy path)
 - Acceptance criteria in Gherkin format (Given/When/Then)
 
 *Referenced anchors: gherkin, bdd-given-when-then*
@@ -4998,6 +5035,7 @@ For each issue:
 - Select next issue from backlog (respect dependencies)
 - Analyze and document analysis as a comment on the issue
 - Implement using TDD (London or Chicago School as appropriate)
+- Each test references its Use Case ID for traceability
 - Commit with Conventional Commits, reference issue number
 - Check if spec or architecture docs need updating
 - When EPIC is complete, create a Pull Request