name: nuguland-ui
description: "Use when creating, changing, debugging, or reviewing Nuguland UI: bars, popups, controls, focus, input, or desktop interactions."
Nuguland UI
Read RULES for isolation, gates, evidence and diagnostics; Zen of Nugu for surface language.
Define primary action, observable result, state/geometry owners, feedback, focus entry/return and dismissal.
Include applicable empty, unavailable, disabled, selected and long-content states; use target output geometry.
Layout work loads qml and quickshell; palette work loads nugu.
For visual direction changes, compare up to four mockups using existing semantic roles; iterate until accepted.
Approval covers direction, not QML geometry or compositor behavior.
Unchanged-layout logic fixes need no new design review.
Reuse theme/shared controls; bind state down, route intent up; complete one interaction before adding another.
Check shared-control callers, not only a demo.
Run affected feature and shared nested suites through just ui-test; then full gate.
Add coverage when changed behavior is uncovered.
Current selections and tooling: harness overview.
Inspect complete logs and actual screenshots; use a short recording when stills cannot establish transient behavior.
Report static, load, interaction and visual proof separately; evidence retention follows RULES, not this skill.
---
name: nuguland-ui
description: "Use when creating, changing, debugging, or reviewing Nuguland UI: bars, popups, controls, focus, input, or desktop interactions."
---
# Nuguland UI
- Read [RULES](../../../.system/RULES.md) for isolation, gates, evidence and diagnostics; [Zen of Nugu](../../../.system/specs/NL-SPEC-VQXGUHYK-zen-of-nugu/index.md) for surface language.
- Define primary action, observable result, state/geometry owners, feedback, focus entry/return and dismissal.
Include applicable empty, unavailable, disabled, selected and long-content states; use target output geometry.
- Layout work loads `qml` and `quickshell`; palette work loads `nugu`.
- For visual direction changes, compare up to four mockups using existing semantic roles; iterate until accepted.
Approval covers direction, not QML geometry or compositor behavior.
Unchanged-layout logic fixes need no new design review.
- Reuse theme/shared controls; bind state down, route intent up; complete one interaction before adding another.
Check shared-control callers, not only a demo.
- Run affected feature and shared nested suites through `just ui-test`; then full gate.
Add coverage when changed behavior is uncovered.
Current selections and tooling: [harness overview](../../../test-fixtures/ui/README.md).
- Inspect complete logs and actual screenshots; use a short recording when stills cannot establish transient behavior.
Report static, load, interaction and visual proof separately; evidence retention follows RULES, not this skill.