Understand UI/UX skill routing
Use this explanation to choose the skill that owns an AeroSim UI/UX decision or supplies the procedure needed to complete it. A skill is reusable guidance and tooling. It does not grant approval, change project scope, or replace the named human owner.
Skill tree
Browse all skills, meanings, and usage
| Skill | Meaning | Use it when |
|---|---|---|
corp-v1-main | Shared Corp v1 governance boundary. | Confirm project-wide authority, shared policy, or cross-channel escalation. |
corp-v1-channel-general-aerosim | AeroSim project ownership and coordination. | Resolve project-level direction or conflicts spanning UI/UX and another domain. |
corp-v1-channel-scope-aerosim | Approved user problems, outcomes, requirements, and Feature identity. | Establish what the experience must achieve before design begins. |
corp-v1-channel-architecture-aerosim | Approved interfaces, data, privacy, and system constraints. | Check that a proposed experience can be supported by the approved solution. |
corp-v1-channel-ui-ux-aerosim | Central AeroSim UI/UX governance and human-approval contract. | Perform any governed AeroSim journey, interaction, design-system, accessibility, Penpot, or implementation-handoff work. |
visual-asset-approval-governance | Separate technical, visual-direction, and runtime-acceptance gates. | Use generated aircraft, terrain, illustrations, backgrounds, or other visual assets requiring explicit human acceptance. |
kanban-worker | Durable task execution, evidence, blocker, and handoff procedure. | Run UI/UX work as a Hermes Board task without losing lifecycle state or duplicating follow-up work. |
design-md | Machine-readable and human-readable design-token specification. | Author or validate formal color, typography, spacing, shape, and component tokens. |
penpot-design-operations | Safe operations for editable Penpot design sources. | Discover, create, change, snapshot, and verify Penpot pages, frames, objects, components, and interactions. |
documentation-docusaurus-aerosim | AeroSim documentation structure, writing, validation, and publication. | Record design packages, decisions, approval evidence, and implementation handoffs in this portal. |
requirements-design-traceability | Bidirectional coverage between approved requirements and design evidence. | Prove every visible state has a requirement and every in-scope requirement has a designed state. |
corp-v1-channel-kanban-aerosim | Admission and dependency control for implementation tasks. | Convert an approved, traceable design package into executable work. |
diagrams-drawio | Editable diagrams with deterministic layout and validation. | Create relationship maps, flows, and other diagrams that must remain editable. |
corp-v1-glossary | One governed definition for reusable project terms. | Introduce or change terminology appearing across channels or documentation pages. |
corp-v1-channel-delivery-aerosim | Implementation and verification against approved project inputs. | Build the interface and return evidence or deviations to UI/UX. |
release-design-traceability | Comparison of delivered or released behavior with approved design evidence. | Audit implementation drift, approved exceptions, and release conformance. |
The editable reference source remains engineering/diagrams/skills-ui-ux-channel.drawio.
The interactive tree uses the same read-only React Flow pattern as the Scope roadmap. Solid arrows show the governed design path. Dashed arrows show conditional support that loads only when its capability is needed. Use the expand control for a full-screen view, or open the skill reference below the tree for the same content in a searchable semantic table.
Follow the tree
- Confirm authority and inputs.
corp-v1-mainestablishes the Corp v1 boundary. General, Scope, and Architecture provide project ownership, approved outcomes, and technical constraints. - Enter through the UI/UX channel skill.
corp-v1-channel-ui-ux-aerosimowns AeroSim design governance, Dovydas's approval gate, accessibility expectations, Penpot rules, and downstream handoff requirements. - Create editable design evidence.
penpot-design-operationsmanages project-owned Penpot files, snapshots, revisions, frames, components, interactions, and readback. Loaddesign-mdonly when formal design tokens are being authored or validated. - Verify the complete experience. Use the UI/UX channel's declared Penpot audit tier to inspect required rendered evidence, trace requirements in both directions, and apply a separate visual-approval gate when generated visual assets are involved.
- Record and hand off the approved package. Use the Docusaurus, Draw.io, and glossary skills for durable documentation. Kanban admits implementation work; Delivery implements against the exact approved design rather than substituting screenshots or remembered chat context.
Resolve overlapping guidance
Apply guidance in this order:
- The authorized UI/UX owner's current exact instruction and approval evidence.
- AeroSim project and channel skills.
- AeroSim specialist overlays.
- Reusable global design, documentation, and engineering skills.
The narrower AeroSim rule wins when reusable guidance conflicts with project ownership, approval, geometry, Penpot, accessibility, or handoff requirements. For example, penpot-design-operations explains safe object mutation, while corp-v1-channel-ui-ux-aerosim governs the status rules and evidence. Dovydas, or RootAtSkic acting as backup owner, supplies the approval decision.
Approval boundary
Dovydas is the primary AeroSim UI/UX owner. A Penpot link, completed task, structural validation, successful build, or agent statement does not approve a design package. Implementation handoff requires exact approval evidence for the package and revision being handed off.