tcballard/build-omarchy-plugins

omarchy-qml-patterns

Apply shared hosted-QML patterns to Omarchy 4 Quattro plugin code, including theme tokens, layout, process execution and local state.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/tcballard/build-omarchy-plugins --skill omarchy-qml-patterns

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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 second ShellRoot or Quickshell process. Give late-injected host properties safe defaults rather than required declarations.
  • Use qs.Ui components and semantic tokens. Import qs.Commons as Commons and qualify Commons.Color.*: Qt 6.12 adds a conflicting Color type. Keep the unqualified import too when using Style, Util or Border.
  • Use host motion components; route custom durations through Style.duration(ms) and stop looping animations under Style.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.PlainText for 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.