Cómo usar
- Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
- Consulta las herramientas, credenciales y entornos necesarios en el documento original.
- Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/tcballard/build-omarchy-plugins --skill omarchy-qml-patternsAntes de empezar
- La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
- Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.
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.