docs-validating-software-engineering-separationlisted

# Validating Software Engineering Documentation Separation This Skill provides comprehensive guidance for validating the separation between repository-specific style guides (`docs/explanation/software-engineering/`) and generic educational content (which belongs in external resources, not this repository), as defined in the [Programming Language Documentation Separation Convention](../../../repo-governance/conventions/structure/programming-language-docs-separation.md). ## Purpose Use this Skill when: - Implementing style guide separation validation in checker agents - Validating `docs/explanation/` content doesn't duplicate generic language tutorials - Ensuring prerequisite knowledge statements exist and link to external resources - Checking style guides focus on repository-specific conventions only - Understanding content separation patterns ## Validation Scope **Default scope**: All language directories under `docs/explanation/software-engineering/programming-languages/`. **When user specifies scope** (e.g., "check Go docs"): Validate only that language directory. ## Core Validation Principle **CRITICAL**: `docs/explanation/` content MUST NOT contain generic language tutorials or duplicate official language documentation. **Separation Pattern**: - **External resources** (official docs, standard guides) = Language education (syntax, fundamentals, generic patterns) - **`docs/explanation/`** = Style guides (platform naming conventions, framework choices, repository-