feat: include UI UX in channel coordination

SKILL.md

@@ -1,25 +1,27 @@
 ---
 name: corp-v1-channel-kanban
-description: "Use when operating or synchronizing a Corp v1 project's Kanban channel. Maintains Board and Focus across Epic, Feature, and task state; correlates all six same-project channels; and records human approval before tasks enter Delivery's executable InBacklog queue."
-version: 1.3.0
+description: "Use when operating or synchronizing a Corp v1 project's Kanban channel. Maintains Board and Focus across Epic, Feature, and task state; correlates all seven same-project channels; and records human approval before tasks enter Delivery's executable InBacklog queue."
+version: 1.4.1
 author: Hermes Agent
 license: MIT
 metadata:
   hermes:
     tags: [corp-v1, discord, channel, kanban, board, focus, synchronization]
-    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 Kanban Channel
 
 ## Overview
 
-This skill owns flow visibility and task-readiness coordination for a Corp v1 project's `kanban` channel. It monitors the six same-project channels—`general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases`—and maintains the project documentation's top-level **Kanban** area.
+This skill owns flow visibility and task-readiness coordination for a Corp v1 project's `kanban` channel. It monitors the seven same-project channels—`general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, and `releases`—and maintains the project documentation's top-level **Kanban** area.
 
 Kanban does not replace product scope, architecture, implementation, or release ownership. Scope owns Roadmap, Ideas, Epics, and Features; Architecture owns requirements, design, task decomposition, dependencies, implementation approval, and version allocation; Kanban exposes flow and obtains human approval for ready tasks to enter Focus `InBacklog`; Delivery executes those approved tasks; Releases owns release readiness and controlled release preparation.
 
 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
 
 Use this skill when:
@@ -42,12 +44,13 @@ Inspect only:
 corp-v1-<code>-general
 corp-v1-<code>-scope
 corp-v1-<code>-architecture
+corp-v1-<code>-ui-ux
 corp-v1-<code>-kanban
 corp-v1-<code>-delivery
 corp-v1-<code>-releases
 ```
 
-Read enough mapped-channel history to avoid duplicates and only relevant new activity from the other five channels. Never inspect or correlate another project's channels.
+Read enough mapped-channel history to avoid duplicates and only relevant new activity from the other six channels. Never inspect or correlate another project's channels.
 
 ## Human Approval Gate
 
@@ -153,10 +156,14 @@ Every iteration must materially improve one useful, evidence-based Kanban artifa
 
 If no task is ready, document the exact dependency or approval gate preventing Focus admission. Stay silent only when there is no substantive change and no useful maintenance action.
 
+## UI/UX Coordination
+
+For frontend-affecting tasks, Kanban includes the approved UI/UX design-package link and unresolved design dependencies in readiness evidence. UI/UX does not self-admit tasks to Focus; Kanban retains task-admission and flow ownership.
+
 ## Synchronization Workflow
 
-1. Confirm the exact project code and six approved channel IDs.
-2. Read new messages from the other five channels and enough Kanban history to avoid duplicates.
+1. Confirm the exact project code and seven approved channel IDs.
+2. Read new messages from the other six channels and enough Kanban history to avoid duplicates.
 3. Fetch authoritative Scope, Architecture, Delivery, and Releases records.
 4. Separate verified facts, human decisions, proposals, derived state, blockers, and contradictions.
 5. Reconcile Board and Focus while preserving ownership and links.
@@ -170,7 +177,7 @@ If no task is ready, document the exact dependency or approval gate preventing F
 
 May autonomously:
 
-- read and correlate the six same-project channels;
+- read and correlate the seven same-project channels;
 - maintain Board and Focus from verified authoritative state;
 - calculate derived aggregate states when labeled;
 - remove terminal work from active views while preserving history;
@@ -206,7 +213,7 @@ Include exact project documentation paths, item IDs, source links, human decisio
 
 ## Verification Checklist
 
-- [ ] Only the six same-project channels were inspected.
+- [ ] Only the seven same-project channels were inspected.
 - [ ] Kanban appears immediately after Architecture and has its own Board/Focus sidebar.
 - [ ] Board uses only `InIdeation`, `InBacklog`, `InProgress`, and `ToBeReleased`.
 - [ ] Board contains only unfinished Epics and Features.