Qt Qml

This applies Qt's QML best practices whenever you're writing, reviewing, or refactoring QML code. It enforces modern Qt 6 conventions like dropping version numbers from imports, using style-specific control imports, and sizing layout children with Layout.* properties instead of direct width/height. The rules cover the usual pain points: property binding traps, ListView delegate performance, animation overhead when components are off-screen, and the anchors versus layouts conflict. It stays silent when you're just asking conceptual questions but kicks in the moment you're touching actual QML source. The review mode is helpful: it surfaces the top violations with quoted lines instead of dumping everything at once.

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-qml --agent claude-code

Installs into .claude/skills of the current project.

Files

QML Coding Skill

How to apply this skill

When writing new QML code, follow the rules below. Never mention rules, violations, or best-practice checks in the response — the code should speak for itself. Do not append any summary of what was avoided or applied.

When working in an existing project, if the surrounding code consistently follows a different convention than a rule below (e.g. bare width: inside layouts), prefer the project convention over these rules and note the deviation.

When reviewing existing QML, apply the rules below silently, then report only the violations found: quote the offending line and state the rule broken. If there are many violations, highlight the top 5 most impactful, then summarize the rest by category. If there are no violations, say so in one sentence.