Qt UI Design
Design or audit UI for Qt/QML, Qt projects, web, or embedded MPU or MCU targets. Use when creating screens, layouts, navigation, or auditing UX.
Install
/plugin marketplace add TheQtCompanyRnD/agent-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add TheQtCompanyRnD/agent-skills --skill qt-ui-designgit clone --depth 1 https://github.com/TheQtCompanyRnD/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/qt-ui-design ~/.claude/skills/qt-ui-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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. 1. **Target platform** — Desktop, web browser, mobile, or specific hardware (MCU, Raspberry Pi, other embedded board)? - If a specific board: ask whether a board-specific skill exists for it and load it if so. 2. **Screen shape** — Rectangle (default), Square, or Circle? 3. **Resolution and DPI** — Do you know the screen resolution and DPI? (Approximate is fine.)
Details
- Skill name
qt-ui-design- Repository
- TheQtCompanyRnD/agent-skills
- Path
skills/qt-ui-design/SKILL.md- Repo updated
- 9 November 2026
FAQ
What does the Qt UI Design skill do?
Design or audit UI for Qt/QML, Qt projects, web, or embedded MPU or MCU targets. Use when creating screens, layouts, navigation, or auditing UX.
How do I install the Qt UI Design skill?
Claude Code plugin: /plugin marketplace add TheQtCompanyRnD/agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Qt UI Design popular?
It lives in TheQtCompanyRnD/agent-skills, which has 551 GitHub stars and 56 forks.
Related skills
Qt Canvas2d
551TheQtCompanyRnD/agent-skills
Applies Qt Canvas2D (QtCanvas2D / Qt Canvas Painter, Qt 6.12+) best practices when producing or working with Canvas2D QML source code. Use whenever Canvas2D, Canvas2DContext, path2d, boxshadow2d, boxgradient2d, gridpattern2d, conicalgradient2d or transform2d is the subject: writing, reviewing, fixing, optimizing, or porting Qt Quick Canvas / HTML5 canvas drawing code to Canvas2D. Also use for GPU-accelerated imperative 2D drawing in QML — gauges, dials, charts, waveforms, oscilloscopes, clocks, freehand drawing — including choosing between Canvas2D and Shape/ShapePath when the renderer has not
Qt Cmake Project
551TheQtCompanyRnD/agent-skills
Use to generate or update Qt 6 CMake projects or edit CMakeLists.txt, add sources/resources or define targets (executable, QML module, library).
Qt Cpp Docs
551TheQtCompanyRnD/agent-skills
Generates standalone Markdown reference documentation for any Qt/C++ source files — Qt Widgets classes, Qt Quick backends, Qt/C++ modules, plain C++ utilities, structs, free-function headers, and entry points like main.cpp. Use this skill to document any .h or .cpp file: Qt classes, plain C++ code, utility helpers, or application startup files. Triggers on: "document this class", "write docs for my C++", "document main.cpp", "C++ API docs", "document my Qt app", or whenever C++ or header files are provided and documentation is needed. Works with single files, pasted code, or entire project fol
Game UI Asset Pipeline
455guiguiyan930-source/game-ui-design-workflow
Packs semantically named transparent game UI PNG files into an atlas, preserves component states and reviewed 9-slice metadata, and exports deterministic JSON handoff manifests for Godot, Unity, Cocos, or generic consumers. Use after sprite-sheet splitting when users ask for atlas packing, nine-patch metadata, engine delivery, Unity sprites, Godot regions, Cocos frames, or a Game UI Factory production handoff.
Qt Qml Profiler
551TheQtCompanyRnD/agent-skills
Use when the user is investigating QML / Qt Quick performance — both vague complaints ("the UI feels laggy", "this is slow", "frames are dropping", "the app stutters") and explicit asks to profile, find hotspots, or optimize bindings, signals, or rendering. Runs qmlprofiler on a 2D QML application, parses the .qtd trace, and analyzes hotspots against the source with frame-time, memory, and pixmap-cache summaries. Does NOT cover Qt Quick 3D.
Game UI Component Breakdown
455guiguiyan930-source/game-ui-design-workflow
Breaks an approved game UI page or visual style into reusable, individually generated component assets with clean edges, transparent backgrounds where appropriate, stable naming, states, dimensions, prompts, and traceable manifest records. Use for UI slicing, transparent buttons, icons, cards, modals, navigation, characters, props, frames, labels, effects, or development handoff.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.