Come usare
- Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
- Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
- Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/tcballard/build-omarchy-plugins --skill omarchy-qml-patternsPrima di iniziare
- L’installazione non include abbonamenti, quote API o accesso ai file.
- Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.
Write hosted Omarchy QML
Inspect the installed host and closest working component. Use its contract rather than assuming the pinned examples fit every version.
- Use hosted
Item/UI entry points, never a secondShellRootor Quickshell process. Give late-injected host properties safe defaults rather thanrequireddeclarations. - Use
qs.Uicomponents and semantic tokens. Importqs.Commons as Commonsand qualifyCommons.Color.*: Qt 6.12 adds a conflictingColortype. Keep the unqualified import too when usingStyle,UtilorBorder. - Use host motion components; route custom durations through
Style.duration(ms)and stop looping animations underStyle.reduceMotion. Inspect host support before using these newer tokens. - Keep hover/selection/open state per visual instance; share polling and remote state through a service where needed.
- Set
Text.PlainTextfor external text at every sink, including tooltips and nested delegates. Bound external data before displaying or saving it. - Launch commands with argument arrays. If a shell is necessary, quote external values with
Util.shellQuote. Keep secrets out of display properties, logs and environment dumps. - Keep repeated network/process/storage policy in a narrow adapter with explicit errors and tests for its actual production path.
Load only relevant references: host injection and facades, theme/orientation/monitors, plugin translations, motion and reduced motion, process and state, or external-data review boundaries.
For a theme problem, fix the consumer or shared theme source that owns it. Verify affected behavior with fixtures and required repository checks; report Qt imports and live lifecycle as unrun unless observed on the target host.