Beta desktop control through the connected A0 CLI host. Use for the user's host/local computer screenshots, screen inspection, menus, native app UI, OS-level clicking, scrolling, typing, or checking computeruseremote status. Use instead of linux-desktop for host/local machine control. Do not use for ordinary browser…
Add a new member crate to a Cargo workspace in this repo using the y5-template binary. Use whenever the user asks to add/create/scaffold a new crate, module, or workspace member (e.g. "add a crate under compositor.window", "scaffold action.foo"). Handles the chain-prefix naming convention and non-interactive…
How to log in the y5 compositor. Use whenever you add, change, or migrate logging — any time you'd reach for a log/print statement, "add a log", debug output, tracing::!, println!, or a fatal panic! with a message. y5 has its own tracing-free structured logging; this skill is the source of truth for using it.
Audience: an agent writing a shader bundle for the y5 compositor from a natural-language request. This document is the specification. It is exhaustive: everything you need to emit a correct bundle is here. The example bundles listed at the end are for calibration — read one when you want to see a shape in practice…
Full performance/concurrency audit of Unisic (C++/Qt6/QML, Wayland). Use when the user asks for a performance audit, "make app fast", idle CPU/memory investigation, memory leaks, thread bugs, deadlocks, or invokes /perf-audit. Measurement-first — never guess; produces a structured report and minimal fixes.
Ponytail-style performance/concurrency audit of Unisic (C++/Qt6/QML, Wayland): lazy senior engineer, evidence-first, NO code changes during the audit. Produces a verdict/baseline/ranked-findings report in the strict P tag format. Use when the user says "ponytail audit", "audyt wydajności ponytail"…
Step-by-step workflow for adding new features to TypeType, following architecture/coding standards. Use when adding a feature, modifying, or fixing bugs.
Understand TypeType project architecture, layering rules, dependency directions, and component responsibilities. Use when working on TypeType, adding features, or refactoring.