Design intuitive desktop interfaces following platform conventions with proper layouts, keyboard shortcuts, and native widgets
Scanned 2/12/2026
Install via CLI
openskills install majiayu000/claude-skill-registry---
name: "Desktop UI Design"
description: "Design intuitive desktop interfaces following platform conventions with proper layouts, keyboard shortcuts, and native widgets"
category: "ui-design"
required_tools: ["Read", "Write", "WebSearch"]
---
# Desktop UI Design
## Purpose
Design intuitive desktop application interfaces using native UI frameworks (Tkinter, Qt, WPF, etc.) following platform conventions and usability best practices.
## When to Use
- Creating desktop application interfaces
- Designing forms and dialogs
- Planning menu structures and navigation
- Organizing application windows
## Key Capabilities
1. **Layout Design** - Organize controls logically with proper spacing
2. **Platform Conventions** - Follow OS-specific design guidelines
3. **Usability Patterns** - Apply desktop UI best practices
## Approach
1. Understand user workflows and tasks
2. Group related controls together
3. Follow platform conventions (Windows, macOS, Linux)
4. Use familiar patterns (menus, toolbars, status bars)
5. Ensure keyboard accessibility
6. Provide visual feedback for actions
## Example
**Context**: Task management application main window
````
Menu Bar: File | Edit | View | Tools | Help
Toolbar: [New] [Open] [Save] [Refresh]
─────────────────────────────────────
Main Content Area:
┌─ Task List ─────────────────────┐
│ ☐ Task 1 High Pending │
│ ☑ Task 2 Normal Complete │
│ ☐ Task 3 Low Pending │
└─────────────────────────────────┘
Status Bar: 3 tasks | 1 active | Last refresh: 2:30 PM
````
**Design Principles**:
- Most important actions in toolbar
- Full functionality in menus
- Context menus for quick access
- Status bar for non-critical info
- Keyboard shortcuts for common actions
## Best Practices
- ✅ Use native widgets for platform consistency
- ✅ Provide keyboard shortcuts (Ctrl+N, F5, etc.)
- ✅ Show visual feedback (disabled states, progress indicators)
- ✅ Use standard dialog patterns (OK/Cancel, Yes/No)
- ❌ Avoid: Custom widgets that don't match platform look
- ❌ Avoid: Hiding important actions deep in menusNo comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...