skills.rest
EvgeniiFenita
EvgeniiFenitaCOMMUNITY
Explore all skills by this author →
GitHub

qt-qml

Implement a Qt/QML Librova shell with one-process architecture and UI-backend separation.

Updated Aug 27, 2026
Search Tags:#testing#design-system#qt#qml#librova#one-process#context-properties
One-click install
npx skills add https://github.com/EvgeniiFenita/Librova --skill qt-qml-evgeniifenita
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qt-qml
Source: https://github.com/EvgeniiFenita/Librova/tree/main/.agents/skills/qt-qml
Command: npx skills add https://github.com/EvgeniiFenita/Librova --skill qt-qml-evgeniifenita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides structured guidance for making Qt/QML changes in Librova, ensuring a one-process shell, clear separation between UI and backend, and alignment with the design system and testing strategy.

Core Features & Use Cases

  • Architectural guidance for the Librova Qt/QML shell, including module ownership across App, Controllers, Adapters, Models, qml/shell, qml/sections, qml/library, and theme tokens.
  • Rules to preserve the C++/QML boundary, ensuring UI state remains in QML and backend logic stays in controllers/adapters.
  • Use cases include adding or updating Qt views, wiring new context properties, updating theme tokens, and extending tests to cover new UI behavior.

Quick Start

Follow the Qt/QML workflow guidelines to modify apps/Librova.Qt while preserving one-process shell architecture and test patterns.

Frequently Asked Questions about qt-qml

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain a one-process architecture when modifying Qt/QML views?▼

To maintain a one-process architecture in Qt/QML, enforce a strict separation where UI state remains in QML and backend logic stays in C++ controllers and adapters. Follow module ownership rules to ensure structural consistency.

What is the correct way to wire new context properties in a Qt/QML shell?▼

Wiring new context properties requires following established module ownership rules across App, Controllers, Adapters, and Models directories. This preserves the C++/QML boundary and keeps backend logic correctly exposed to the QML UI.

How do I update design system tokens in a QML application?▼

Updating design system tokens involves modifying the theme tokens within the qml directory structure. Always reference canonical design system documentation when editing the Qt layer to ensure UI consistency and architectural alignment.

Can I extend Qt tests to cover new QML UI behavior without breaking the shell?▼

Yes, you can extend tests to cover new QML UI behavior. Apply the established testing strategy and test patterns when modifying the Qt shell to ensure new UI behavior is validated without breaking the one-process architecture.

When should I not put backend logic directly in QML files?▼

You should avoid putting backend logic in QML when preserving the C++/QML boundary. Keep UI state in QML and backend logic in controllers and adapters to maintain clean separation and architectural consistency.

Related Skills

Explore More Software Engineering Skills→
tkerseytkersey
66

select

Plan swarm-ready tasks from source files into a canonical OrchPlan.

Community
Advanced
RsultCodingRsultCoding

validate-ui

Validate Archon Web UI end-to-end behavior across dashboard, chat, workflows, and SSE.

Community
Advanced
gvellutgvellut

automate-pyside6-and-screenshots

Automate PySide6 desktop apps and capture screenshots via a Python server/client.

Community
Advanced
StrayDragonStrayDragon
2

Slint GUI Expert

Develop Slint GUI applications with Rust integration and cross-platform deployment guidance.

Community
Advanced