cubetiq/desktop-ui-design
workflows/workflows/agent-environment-setup/platforms/antigravity/skills/desktop-ui-design/SKILL.md
Design desktop-first interfaces with multi-pane structure, keyboard-first productivity, high-information-density clarity, and implementation-aware handoff for desktop-grade app surfaces.
$ install --global
skillsauthnpx skillsauth add cubetiq/cubis-foundry desktop-ui-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 9:56 AM33.0s2 files scanned
SKILL.md
- name:
- desktop-ui-design
- description:
- Design desktop-first interfaces with multi-pane structure,
Desktop UI Design
Purpose
Provide the desktop-first execution surface for design work. Use it when the task needs a concrete desktop workspace, dense operational surface, or expert-oriented app shell that should not be flattened into a mobile or generic web layout.
Desktop UI should reward expertise. It should expose more context, faster actions, and more comparison power than the same product would on mobile or narrow web surfaces.
Instructions
- Start from the canonical direction chosen in
../design/SKILL.md, then restate the desktop job to be done before proposing structure. - Use
../design/references/foundation.mdto define the persistent context, information model, and task cadence before composing the screen. - Use
../design/references/responsive-adaptive-systems.mdwhen the same product spans mobile, web, and desktop so the desktop surface gains real context and speed instead of just larger cards. - Prefer desktop-native structures. Use
../design/references/desktop-app-ui-design.mdwhen pane models, inspector layouts, dense data behavior, or expert throughput need a sharper desktop-specific frame. - Design for pointer and keyboard first. Make shortcuts, multi-select, drag/drop, inline edit, and dense-but-readable data presentation explicit when relevant.
- Specify desktop state behavior clearly: empty, loading, background sync, error, destructive confirmation, multi-selection state, and panel persistence. Use
../design/references/polish-accessibility-motion.mdwhen density, focus behavior, motion, or interaction polish needs a final pass. - End with a desktop-ready handoff using
../design/references/output-template.md: workspace structure, pane rules, productivity affordances, state model, and implementation notes.
Desktop Direction Rules
- desktop is not a blown-up mobile app
- persistent context should be introduced when it reduces navigation cost
- dense views must be aligned and legible, not cluttered
- keyboard, batch actions, and comparison views should be considered by default
- use panes, inspectors, and tables where they improve throughput
Anti-patterns
- Do not route or critique the task from this surface; those belong in
../design/SKILL.md. - Do not stack every region into mobile-style cards on desktop.
- Do not hide frequent expert actions behind too many drawers, hovers, or menus.
- Do not use oversized whitespace that reduces scan speed on dense work surfaces.
- Do not treat desktop as responsive web only when the task clearly benefits from adaptive multi-pane structure.
Output Format
Return:
- Desktop job and visual thesis
- Workspace structure and pane model
- Navigation, shortcuts, and productivity rules
- States, density, and comparison behavior
- Implementation-ready handoff notes
References
../design/SKILL.md../design/references/desktop-app-ui-design.md../design/references/foundation.md../design/references/responsive-adaptive-systems.md../design/references/output-template.md../design/references/polish-accessibility-motion.md../design/references/visual-direction.md../design/references/design-tokens.md
Related Skills
cubetiq/deep-research
tools
VerifiedTrustedCommunity
Use when investigating latest vendor behavior, comparing tools or platforms, verifying claims beyond the repo, or gathering external evidence before implementation.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/database-design
documentation
VerifiedTrustedCommunity
Use when designing database schemas, normalization strategies, indexing plans, query optimization, and migration workflows for relational, document, or hybrid data stores.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/csharp-best-practices
development
VerifiedTrustedCommunity
Use when writing, reviewing, or refactoring modern C#/.NET code, including minimal APIs, records, async streams, pattern matching, DI lifetimes, and memory-efficient performance tuning.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/code-review
development
VerifiedTrustedCommunity
Use when conducting code reviews, building review checklists, calibrating review depth, providing structured feedback, or establishing team review practices. Covers review methodology, feedback patterns, automated checks, and batch review strategies.
1SKILL.mdUpdated Apr 4, 2026