From fad070329450cc0a7067c2fea023041bf4ca96c6 Mon Sep 17 00:00:00 2001 From: Jarvis Jr Hermes Date: Fri, 4 Sep 2026 12:55:00 +0000 Subject: [PATCH] fix: update Corp v1 skill references --- SKILL.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/SKILL.md b/SKILL.md index fcfc930..714b4bd 100644 --- a/SKILL.md +++ b/SKILL.md @@ -7,7 +7,7 @@ license: MIT metadata: hermes: tags: [corp-v1, discord, channel, architecture, c4, adr, requirements] - related_skills: [corp-v1--main, home-v1-discord, diagrams-drawio, documentation-docusaurus, corp-v1--glossary] + related_skills: [corp-v1-main, home-v1-discord, diagrams-drawio, documentation-docusaurus, corp-v1-glossary] --- # Corp v1 Architecture Channel @@ -30,11 +30,11 @@ Load the global `documentation-docusaurus` skill before changing project documen 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. +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. ## Shared Corp v1 System Login -When an authorized task requires login to a Corp v1 system being built or operated, follow the shared policy in `corp-v1--main` and use only the Bitwarden-injected runtime secrets named: +When an authorized task requires login to a Corp v1 system being built or operated, follow the shared policy in `corp-v1-main` and use only the Bitwarden-injected runtime secrets named: ```text HL_V1_SSO_EMAIL