qt-entity-creator

Generate Qt UI scaffolding for new domain entities in Ore Studio.

25|5|Updated Jun 15, 2024
One-click install
npx skills add https://github.com/OreStudio/OreStudio --skill qt-entity-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qt-entity-creator
Source: https://github.com/OreStudio/OreStudio/tree/main/.claude/skills/qt-entity-creator
Command: npx skills add https://github.com/OreStudio/OreStudio --skill qt-entity-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a unified scaffold for Qt UI components tied to domain entities, ensuring consistent architecture across model, list view, dialogs, and a controller.

Core Features & Use Cases

  • Scaffold a full Qt UI stack for a new domain entity, including ClientModel, MDI window, detail dialog, and history support.
  • Apply established patterns for data loading, editing, version history, and controller integration.
  • Use Case: Add a new domain entity to Ore Studio's UI and generate all necessary components with a single workflow.

Quick Start

Use the qt-entity-creator skill to generate all required Qt UI components for a domain entity.

Frequently Asked Questions about qt-entity-creator

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

FAQPage Schema
How do I generate Qt UI scaffolding for a new domain entity?

The scaffolder generates a complete Qt UI stack for a new domain entity, including ClientModel, MDI window, detail dialog, and history support. It applies established patterns for data loading, editing, version history, and controller integration.

What do I need to set up before scaffolding Qt UI components for domain entities?

Before scaffolding Qt UI components, you need a valid domain type and a configured project build setup. These prerequisites ensure the generated model, list view, and dialogs integrate correctly into the established architecture.

What is the best way to ensure consistent architecture when adding Qt UI components?

The best way to ensure consistent architecture is to use an automated scaffolding workflow that generates the model, list view, dialogs, and controller together. This enforces standard data loading and version history patterns across the Qt UI layer.

Can I use this Qt scaffolding to generate both detail and history dialogs?

Yes, the Qt scaffolding can generate both detail and history dialogs for domain entities. It creates the necessary UI components for viewing and editing entity data, along with version history support.

When should I avoid automated Qt UI code generation for domain entities?

You should avoid automated Qt UI code generation if your domain type is invalid or the project build setup is incomplete. The scaffolder requires these to correctly apply the established Qt/C++ patterns for the model and controller integration.