Review and improve Qt6 C++ and QML code with deterministic linting and agentic deep analysis, generate Markdown documentation from source files, build CMake projects, write QML unit tests, profile QML application performance, and extract Figma design tokens into production-ready QML controls.
Extract design tokens, text styles, and variables from a Figma design system and produce a design-tokens.json plus ready-to-use QML singletons. Use this skill whenever someone wants to pull their design system out of Figma — whether they say "export tokens from Figma", "get design tokens", "set up my design system", "read our Figma design system", "get Figma variables into QML", "pull our color palette from Figma", "import design tokens", "extract colors/typography/spacing from Figma", or similar. Trigger this skill at the start of any design-system workflow that involves a Figma source.
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 folders. DO NOT use if the user asks for QDoc format output.
Invoke when the user asks to review, check, audit, or look over Qt6 C++ code — or suggest before committing. Runs deterministic linting (60+ rules) then six parallel deep- analysis agents covering model contracts, ownership, threading, API correctness, error handling, and performance. Reports only high-confidence issues (>80/100) with structured mitigations. Read-only — never modifies code.
Extract component metadata from a Figma design system and generate production-ready QML controls. Use this skill whenever someone wants to turn Figma components into QML files — whether they say "generate components from Figma", "create QML controls based on a design system", "convert Figma components to QML", "build the component library", "extract button/input/checkbox from Figma", or anything similar. Requires design-tokens.json and QML design system singletons to already exist (from the token extraction skill). Uses Figma MCP to inspect components one at a time and maps variants, states, sizing, and token usage to idiomatic Qt Quick Controls 2 patterns. Trigger this skill at the component generation step of any QML design-system workflow.
Use to generate or update Qt 6 CMake projects or edit CMakeLists.txt, add sources/resources or define targets (executable, QML module, library).
External network access
Connects to servers outside your machine
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Official agentic skills for Qt software development and quality assurance, designed for use with AI coding tools such as Claude Code, Codex CLI, Gemini CLI, and GitHub Copilot.
Skills have been tested with frontier LLMs from the Claude, Gemini, and GPT model families.
There is no settled industry standard for AI skill packaging.
Each platform has its own conventions. Our canonical format
uses SKILL.md with YAML frontmatter in a directory-based
structure — this works natively on Claude Code, Codex CLI,
and GitHub Copilot, and can be adapted to other platforms
through condensed variants. See CONTRIBUTING.md
for the full cross-platform story.
These agentic development skills use AI and can make mistakes. Always double-check the output carefully.
Before using the skills under Qt commercial licensing, make sure you have understood and agree to the Qt AI Services Terms & Conditions. By using the skills or MCP tools, you accept these terms & conditions and that you have the right to do so on behalf of your employer.
| Skill | Type | Description |
|---|---|---|
qt-cpp-review | Review | Deterministic linting + 6 parallel deep-analysis agents for Qt C++ code. Covers model rule compliance, memory ownership, thread safety, correctness, error handling, and performance. |
qt-qml-review | Review | Deterministic QML linting (47+ rules) + parallel deep-analysis agents for bindings, layout, loaders, delegates, states, and performance. |
qt-qml | Conceptual | QML best practices for writing, reviewing, fixing, and refactoring. Corrects systematic LLM pre-training biases around bindings, scoping, modules, JS interop, and types. |
qt-ui-design | Conceptual | UI design and audit for Qt/QML, web, and embedded (MPU/MCU) targets. Covers screen layout, navigation, and UX review with platform-aware defaults for geometry, viewing distance, input, and locale. |
qt-qml-docs | Process | Generates Markdown reference documentation for QML components and applications from .qml source files. |
qt-cpp-docs | Process | Generates Markdown reference documentation for Qt/C++ source files — classes, modules, utilities, headers, and entry points. |
qt-qml-profiler | Tool | Runs qmlprofiler on a 2D QML / Qt Quick application, parses the .qtd trace, and analyzes hotspots against the source code with frame-time, memory, and pixmap-cache summaries. Does not cover Qt Quick 3D. |
qt-qml-test | Process | Generates Qt Quick Test cases (tst_*.qml) for QML components using TestCase, SignalSpy, and tryCompare. Handles single files and batches. Does not cover CMake or runner setup. |
qt-qml-test-run | Tool | Builds and runs Qt Quick Test (qmltestrunner) tests for a CMake project, parses the JUnit XML, and writes a Markdown report. Opt-in CMake test-infrastructure wiring with --wire-up. Companion to qt-qml-test. |
qt-figma-token-extraction | Process | Extracts design tokens, text styles, and variables from a Figma design system and produces a design-tokens.json plus ready-to-use QML singletons. |
qt-figma-component-generation | Process | Extracts component metadata from a Figma design system and generates production-ready QML controls mapped to Qt Quick Controls 2 patterns. Requires tokens from qt-figma-token-extraction. |
qt-project | Conceptual | Sets up and manages Qt 6 projects built with CMake — fresh projects, executables, libraries, QML modules, plugins, folder layout, and static resources. Corrects systematic LLM biases around qmake-isms and the legacy qt5_* macros. |
| Tool | Description |
|---|---|
qt-documentation-mcp | Hosted MCP server for Qt API documentation lookup across the latest release and active LTS branches. Bundled with the qt-development-skills plugin; also available standalone via the official MCP registry as io.qt/qt-documentation-mcp. |
See mcp/qt-documentation-mcp/README.md
for endpoint and manual setup instructions for AI clients other than
Claude Code.
npx claudepluginhub theqtcompanyrnd/agent-skills --plugin qt-development-skillsCompose and Compose Multiplatform expert skill — state, animations, navigation, performance, design-to-code, PR review mode, M3 motion.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Shared Claude Code plugin for frontend teams, including frontend skills, subagents, hooks, and MCP integration for Figma/Sketch/MasterGo/Pixso/墨刀/摹客. All reports auto-saved as Markdown files.
Design System compliance harness for Claude + Figma. Enforces library-first components, token binding, and automated QA — so AI-generated designs stay on-spec.
Validation and quality enforcement for gluestack-ui projects with component patterns, accessibility, and theming skills. Includes MCP server for component discovery and source code retrieval.
Desktop App Dev subagent