Qt Ui Design

Before you start throwing together Qt layouts, this skill runs you through a short checklist: target platform, screen geometry, design system, viewing distance, locale, and input methods. It's less about code generation and more about making you think through the constraints first. Once that's done, it applies a solid set of UX principles (Jakob's Law, Hick's Law, progressive disclosure) and gives you specific guidance on typography scales, animation timing budgets, and responsive behavior. The embedded and MCU section is genuinely useful if you're targeting fixed panels or resource-constrained hardware. Think of it as a design systems consultant that keeps you from reinventing spatial hierarchies or picking arbitrary font sizes.

skills.sh installs: 1.2K
GitHub stars: 534
last updated: Jun 10, 2026

View on GitHub

Install

$ npx -y skills add theqtcompanyrnd/agent-skills --skill qt-ui-design --agent claude-code

Installs into .claude/skills of the current project.

Files

Qt UI Design

Before producing UI output, confirm you know: target platform, screen geometry, design system, content priority, viewing distance, locale, and input methods. Run the seven items below as a check against the conversation and the project state; ask only the items that are genuinely missing. When the user cannot answer an item, choose a sensible Qt default and name it in your response so the user can correct it.

Small edits to an existing design — for example "move the OK button to the right", "change this label", "make this red" — do not trigger the checklist. Apply section 1 silently and verify section 2 (contrast, hit-target) where relevant.

0. Context check (before designing)

Use the seven items below to decide what is already known and what to ask. If the conversation or repository has already answered an item, do not re-ask.

SKILL.md on GitHub