SKILL.md

@@ -1,7 +1,7 @@
 ---
 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."
-version: 1.6.0
+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 seven channels."
+version: 1.6.1
 author: Hermes Agent
 license: MIT
 metadata:
@@ -14,7 +14,7 @@ metadata:
 
 ## Overview
 
-This skill owns the solution phase and architecture coherence for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases` channels, transforms human-approved Features into requirements and solution artifacts, breaks them into dependency-aware implementation tasks, assigns approved Features to versions, and maintains the Architecture section of the project documentation.
+This skill owns the solution phase and architecture coherence for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, and `releases` channels, transforms human-approved Features into requirements and solution artifacts, breaks them into dependency-aware implementation tasks, assigns approved Features to versions, and maintains the Architecture section of the project documentation.
 
 The default architecture model is C4. Architecture diagrams must be authored and validated using the global `drawio-main` skill from:
 
@@ -64,12 +64,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
 ```
 
-Use mapped-channel history to avoid duplicate work and new relevant activity from the other five channels. Never inspect another project's channels.
+Use mapped-channel history to avoid duplicate work and new relevant activity from the other six channels. Never inspect another project's channels.
 
 ## Architecture Documentation Contract
 
@@ -208,6 +209,10 @@ After human Feature implementation approval, Architecture sends dependency-ready
 
 Every architecture iteration must add or materially improve a useful project-documentation artifact for an eligible human-approved Feature: FR/NFR traceability, C4/ADR content, task decomposition, dependency mapping, risk analysis, version proposal, or review package. Prefer improving existing artifacts over creating duplicates. If no Feature is approved for solution, document the exact waiting gate or actionable clarification instead of advancing unapproved work.
 
+## UI/UX Coordination
+
+Architecture supplies UI/UX with system boundaries, interfaces, data availability, security/privacy constraints, and affected containers/components. UI/UX owns the frontend experience, Penpot design source, design-system decisions, accessibility evidence, and implementation handoff. Neither channel silently changes the other channel’s approved constraints.
+
 ## Synchronization Workflow
 
 1. Read new same-project activity and enough architecture history to avoid duplicates.
@@ -261,7 +266,7 @@ Requires team approval for:
 
 ## Verification Checklist
 
-- [ ] Only the six same-project channels were inspected.
+- [ ] Only the seven same-project channels were inspected.
 - [ ] Architecture documentation reflects verified status.
 - [ ] C4 scope and level are appropriate.
 - [ ] `drawio-main` governed every diagram change.