tcballard/build-omarchy-plugins

Build or refactor an Omarchy Quattro bar-widget implementation, including settings, orientation, popouts, instances and shared services. Use for widget QML or behaviour; global bar styling belongs to theme skills, and replacing the entire bar is outside this skill.

Build or refactor Omarchy Quattro panel, overlay, or menu entry points. Use for summon/hide lifecycle, payloads, layer-shell windows, focus, dismissal, positioning, keyboard navigation, or multi-monitor presentation.

Diagnose an Omarchy Quattro plugin that is not discovered, validated, enabled, loaded, reloaded, summoned, or behaving correctly. Use for local environment, manifest, shell config, QML runtime, IPC, process, and recovery failures.

Create or verify a deterministic Omarchy plugin demo and marketplace screenshot using fictional data. Use for fixture CLIs, isolated state, reversible shell setup, screenshot capture, and demo evidence; never use real credentials or live personal data.

Design an Omarchy 4 Quattro shell plugin before implementation. Use when choosing plugin kinds, architecture, dependencies, state ownership, IPC, security boundaries, or evidence. Do not treat legacy package installers as shell plugins; route those through migration.

Migrate an older installer-style Omarchy integration or standalone Quickshell surface to Omarchy 4 Quattro. Use to separate machine setup, daemon, credentials, and shell UI while preserving safe install, upgrade, and removal behavior.

Prepare or submit an Omarchy plugin marketplace issue, and respond to listing review or updates. Use for current form, category, tags, exact issue body, owner attestations and reviewed SHA; use release for versioned assets and test for validation evidence.

Preflight and prepare a versioned Omarchy plugin release from a public Git repository. Use for readiness, version and tag alignment, CI, install/update/removal evidence, preview, dependencies, checksums and assets; marketplace issue creation belongs to the publish skill.

Create a new Omarchy 4 Quattro shell-plugin repository or add its initial supported entry points. Use for manifest, QML, tests, CI, demo, license, and README scaffolding; not for overwriting an established plugin.

Validate changed Omarchy 4 Quattro plugin behavior with manifest, path, advisory security, QML, fixture and live-shell checks. Use for development regression evidence; use release for version and asset readiness or publish for marketplace responses. Static checks do not certify security.

Apply shared hosted-QML patterns to Omarchy 4 Quattro plugin code, including theme tokens, layout, process execution and local state. Use alongside the relevant bar, panel or service skill for implementation; use theme skills for shared palette or shell.toml styling.

Build or review a process-wide Omarchy Quattro QML service and IPC contract. Use when state, polling or command execution must survive a panel closing or be shared across widgets; use QML patterns for shared implementation details, not for generic systemd services.