Build / compile / verify the y5_compositor binary. Use whenever you need to build the compositor, do a release build, install/deploy it, or confirm the whole tree still compiles. ALWAYS prefer the environment/ scripts over raw `cargo build` — the scripts share ONE target dir (disk-optimized); per-workspace `cargo build` scatters multi-GB target/ dirs across the tree.
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 invocation.
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.