docs: reference Corp v1 glossary governance

This commit is contained in:
2026-08-20 13:35:50 +00:00
parent b201a502ce
commit e822da66b8
+4 -2
View File
@@ -1,13 +1,13 @@
--- ---
name: corp-v1-channel-delivery name: corp-v1-channel-delivery
description: "Use when operating or synchronizing a Corp v1 project's delivery channel. Drives coding, unit testing, build and continuous-integration health, attempts safe evidence-based fixes, escalates requirement or architecture contradictions, and maintains Ways of Working and Engineering documentation." description: "Use when operating or synchronizing a Corp v1 project's delivery channel. Drives coding, unit testing, build and continuous-integration health, attempts safe evidence-based fixes, escalates requirement or architecture contradictions, and maintains Ways of Working and Engineering documentation."
version: 1.4.0 version: 1.5.0
author: Hermes Agent author: Hermes Agent
license: MIT license: MIT
metadata: metadata:
hermes: hermes:
tags: [corp-v1, discord, channel, delivery, coding, testing, ci] tags: [corp-v1, discord, channel, delivery, coding, testing, ci]
related_skills: [corp-v1--main, home-v1-discord, documentation-docusaurus] related_skills: [corp-v1--main, home-v1-discord, documentation-docusaurus, corp-v1--glossary]
--- ---
# Corp v1 Delivery Channel # Corp v1 Delivery Channel
@@ -20,6 +20,8 @@ Its scope includes coding, unit testing, builds, continuous integration, review
Load the global `documentation-docusaurus` skill from `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/documentation-docusaurus` before changing documentation structure, navigation, Markdown/MDX, Docusaurus configuration, or builds. Load the global `documentation-docusaurus` skill from `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/documentation-docusaurus` before changing documentation structure, navigation, Markdown/MDX, Docusaurus configuration, or builds.
Load the global `corp-v1--glossary` skill from `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--glossary` whenever project documentation needs to define or explain a reusable term. Maintain one canonical definition in the project's final top-level **Glossary** area and link to it from the owning domain page; do not duplicate glossary-style explanations across channel documentation.
## When to Use ## When to Use
Use this skill when: Use this skill when: