corp-v1-3darch-skills-code-agent/corp-v1-channel-architecture-3darch
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: reference Corp v1 glossary governance

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-20 13:35:49 +00:00
parent db35632570
commit 40649b2eaa
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+4 -2
View File
@@ -1,13 +1,13 @@
--- ---
name: corp-v1-channel-architecture name: corp-v1-channel-architecture
description: "Use when operating or synchronizing a Corp v1 project's architecture channel. Maintains C4-based architecture documentation, Draw.io diagrams, architecture decisions, and requirements while correlating verified activity across the project's six channels." description: "Use when operating or synchronizing a Corp v1 project's architecture channel. Maintains C4-based architecture documentation, Draw.io diagrams, architecture decisions, and requirements while correlating verified activity across the project's six channels."
version: 1.5.0 version: 1.6.0
author: Hermes Agent author: Hermes Agent
license: MIT license: MIT
metadata: metadata:
hermes: hermes:
tags: [corp-v1, discord, channel, architecture, c4, adr, requirements] tags: [corp-v1, discord, channel, architecture, c4, adr, requirements]
related_skills: [corp-v1--main, home-v1-discord, drawio-main, documentation-docusaurus] related_skills: [corp-v1--main, home-v1-discord, drawio-main, documentation-docusaurus, corp-v1--glossary]
--- ---
# Corp v1 Architecture Channel # Corp v1 Architecture Channel
@@ -30,6 +30,8 @@ Load the global `documentation-docusaurus` skill before changing project documen
https://gitea.lego-cloud.eu/home-v1-skills-code-agent/documentation-docusaurus https://gitea.lego-cloud.eu/home-v1-skills-code-agent/documentation-docusaurus
``` ```
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: