How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

design-qt-quick-ui - Prompt

Name: design-qt-quick-ui
Author: thecompez

Prompt file imported from thecompez/ai-for-modern-cpp (.claude/commands/design-qt-quick-ui.md). Copyright stays with the author.

Design Qt Quick UI

Always read AGENTS.md, docs/agent/EXECUTION_DISCIPLINE.md, docs/agent/QT_QUICK_UI.md, and docs/agent/TESTING_AND_VERIFICATION.md. Read START_PROJECT.md, PROJECT_CMAKE_BASELINE.md, ARCHITECTURE.md, NAMING.md, SYNTAX_AND_STYLE.md, API_DESIGN.md, ERRORS_AND_RESOURCES.md, or APP_ICONS_AND_BRANDING.md only when the actual UI task touches those concerns.

Inspect the current diff and owning screen/component before broader discovery. Work as one agent by default. A local QML visual/interaction fix is normally V1; presentation/domain C++ behavior is normally V2; QML registration, resource/CMake topology, public adapter boundaries, or cross-surface structural changes are V3; final/release verification is V4.

Define only the audience/flow/states, product-specific visual direction, layout contract, accessibility/localization, and C++/QML ownership decisions needed by the requested scope. Do not redesign unrelated screens or load every guide. Use Qt 6, Qt Quick, QML, Qt Quick Controls, qt_add_qml_module, modern C++ modules, and the repository's ui/ boundary. Preserve guarded QTP0004, target-local nested QML_ELEMENT includes, non-final QML-creatable QObjects, deterministic QT_RESOURCE_ALIAS, configured QT_QML_OUTPUT_DIRECTORY, target-local RUNTIME_OUTPUT_DIRECTORY, and the approved Controls style where those contracts are touched. Never edit generated *_qmltyperegistrations.cpp.

Implement the smallest coherent UI change. For V1, build the affected Qt target when applicable, run relevant strict qmllint, focused warning-fatal interaction smoke, and targeted rendered visual inspection. For V2, compile the affected production C++/Qt target and relevant tests. For V3, reconfigure when topology changes and cover every affected surface. For V4, use a clean full default build, all tests, strict lint, primary interaction, and the minimum/standard/wide visual acceptance matrix; record linked runtime plus qmldir and .qmltypes paths for generated Qt projects.

Reuse compatible build state for V1/V2; after a failure, rerun from the earliest invalidated stage. Report exact evidence and NOT VERIFIED layers, then stop.

Critical Qt invariants when those surfaces are touched: run aimcpp_reject_final_qml_creatable_types; a QML-creatable QObject must not be final; reject binding loops and a timer-only smoke flow; for a final polished claim inspect minimum, standard, and wide states and record accidental dead space as a visual defect when present.

Install design-qt-quick-ui and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Design Qt Quick UI Always read `AGENTS.md`, `docs/agent/EXECUTION_DISCIPLINE.md`, `docs/agent/QT_QUICK_UI.md`, and `docs/agent/TESTING_AND_VERIFICATION.md`. Read `START_PROJECT.md`, `PROJECT_CMAKE_BASELINE.md`, `ARCHITECTURE.md`, `NAMING.md`, `SYNTAX_AND_STYLE.md`, `API_DESIGN.md`, `ERRORS_AND_RESOURCES.md`, or `APP_ICONS_AND_BRANDING.md` only when the actual UI task touches those concerns. Inspect the current diff and owning screen/component before broader discovery. Work as one agent by default. A local QML visual/interaction fix is normally `V1`; presentation/domain C++ behavior is normally `V2`; QML registration, resource/CMake topology, public adapter boundaries, or cross-surface structural changes are `V3`; final/release verification is `V4`. Define only the audience/flow/states, product-specific visual direction, layout contract, accessibility/localization, and C++/QML ownership decisions needed by the requested scope. Do not redesign unrelated screens or load every guide. Use Qt 6, Qt Quick, QML, Qt Quick Controls, `qt_add_qml_module`, modern C++ modules, and the repository's `ui/` boundary. Preserve guarded QTP0004, target-local nested `QML_ELEMENT` includes, non-`final` QML-creatable QObjects, deterministic `QT_RESOURCE_ALIAS`, configured `QT_QML_OUTPUT_DIRECTORY`, target-local `RUNTIME_OUTPUT_DIRECTORY`, and the approved Controls style where those contracts are touched. Never edit generated `*_qmltyperegistrations.cpp`. Implement the smallest coherent UI change. For `V1`, build the affected Qt target when applicable, run relevant strict `qmllint`, focused warning-fatal interaction smoke, and targeted rendered visual inspection. For `V2`, compile the affected production C++/Qt target and relevant tests. For `V3`, reconfigure when topology changes and cover every affected surface. For `V4`, use a clean full default build, all tests, strict lint, primary interaction, and the minimum/standard/wide visual acceptance matrix; record linked runtime plus `qmldir` and `.qmltypes` paths for generated Qt projects. Reuse compatible build state for `V1`/`V2`; after a failure, rerun from the earliest invalidated stage. Report exact evidence and `NOT VERIFIED` layers, then stop. Critical Qt invariants when those surfaces are touched: run `aimcpp_reject_final_qml_creatable_types`; a QML-creatable QObject must not be `final`; reject binding loops and a timer-only smoke flow; for a final polished claim inspect minimum, standard, and wide states and record accidental dead space as a visual defect when present.

{ "prompt": "# Design Qt Quick UI\n\nAlways read `AGENTS.md`, `docs/agent/EXECUTION_DISCIPLINE.md`,\n`docs/agent/QT_QUICK_UI.md`, and `docs/agent/TESTING_AND_VERIFICATION.md`.\nRead `START_PROJECT.md`, `PROJECT_CMAKE_BASELINE.md`, `ARCHITECTURE.md`,\n`NAMING.md`, `SYNTAX_AND_STYLE.md`, `API_DESIGN.md`,\n`ERRORS_AND_RESOURCES.md`, or `APP_ICONS_AND_BRANDING.md` only when the actual\nUI task touches those concerns.\n\nInspect the current diff and owning screen/component before broader discovery.\nWork as one agent by default. A local QML visual/interaction fix is normally\n`V1`; presentation/domain C++ behavior is normally `V2`; QML registration,\nresource/CMake topology, public adapter boundaries, or cross-surface structural\nchanges are `V3`; final/release verification is `V4`.\n\nDefine only the audience/flow/states, product-specific visual direction, layout\ncontract, accessibility/localization, and C++/QML ownership decisions needed by\nthe requested scope. Do not redesign unrelated screens or load every guide.\nUse Qt 6, Qt Quick, QML, Qt Quick Controls, `qt_add_qml_module`, modern C++\nmodules, and the repository's `ui/` boundary. Preserve guarded QTP0004,\ntarget-local nested `QML_ELEMENT` includes, non-`final` QML-creatable QObjects,\ndeterministic `QT_RESOURCE_ALIAS`, configured `QT_QML_OUTPUT_DIRECTORY`,\ntarget-local `RUNTIME_OUTPUT_DIRECTORY`, and the approved Controls style where\nthose contracts are touched. Never edit generated `*_qmltyperegistrations.cpp`.\n\nImplement the smallest coherent UI change. For `V1`, build the affected Qt\ntarget when applicable, run relevant strict `qmllint`, focused warning-fatal\ninteraction smoke, and targeted rendered visual inspection. For `V2`, compile\nthe affected production C++/Qt target and relevant tests. For `V3`, reconfigure\nwhen topology changes and cover every affected surface. For `V4`, use a clean\nfull default build, all tests, strict lint, primary interaction, and the\nminimum/standard/wide visual acceptance matrix; record linked runtime plus\n`qmldir` and `.qmltypes` paths for generated Qt projects.\n\nReuse compatible build state for `V1`/`V2`; after a failure, rerun from the\nearliest invalidated stage. Report exact evidence and `NOT VERIFIED` layers,\nthen stop.\n\nCritical Qt invariants when those surfaces are touched: run\n`aimcpp_reject_final_qml_creatable_types`; a QML-creatable QObject must not be `final`; reject binding loops and a timer-only smoke flow; for a final polished\nclaim inspect minimum, standard, and wide states and record accidental dead space\nas a visual defect when present.", "variables": [], "notes": "Always read `AGENTS.md`, `docs/agent/EXECUTION_DISCIPLINE.md`, `docs/agent/QT_QUICK_UI.md`, and `docs/agent/TESTING_AND_VERIFICATION.md`. Read `START_PROJECT.md`, `PROJECT_CMAKE_BASELINE.md`, `ARCHITECTURE.md`, `NAMING.md`, `SYNTAX_AND_STYLE.md`, `API_DESIGN.md`, `ERRORS_AND_RESOURCES.md`, or `APP_ICONS_AND_BRANDING.md` only when the actual UI task touches those concerns.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/thecompez/ai-for-modern-cpp", "path": ".claude/commands/design-qt-quick-ui.md", "ref": "8c00c16a8315a2368720ec684611e6223d106ede", "url": "https://github.com/thecompez/ai-for-modern-cpp/blob/8c00c16a8315a2368720ec684611e6223d106ede/.claude/commands/design-qt-quick-ui.md", "key": "thecompez/ai-for-modern-cpp/.claude/commands/design-qt-quick-ui.md" } } }

design-qt-quick-ui

About

Design Qt Quick UI

Install design-qt-quick-ui and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews