aether

Use when the user wants to drive Aether from the command line — generating themes from wallpapers, applying or managing blueprints, importing Base16 or colors.toml schemes, inspecting the running editor, or scripting palette/ color operations. Covers both the standalone CLI (works without the GUI) and the IPC remote-control commands (require the GUI to be running). Invoke when the user mentions `aether --generate`, `aether status`, `aether apply`, blueprints from the shell, shell/JSON scripting against Aether, or asks "how do I do X from the CLI".

Use when working in the Aether codebase and you need detailed project documentation — architecture decisions, design rationale, flow diagrams, feature specs, ADRs, historical context, WIP drafts. Detailed docs live OUTSIDE the repo at ~/Documents/bjarne/projects/Aether. Read that folder before making non-trivial changes, and write new detailed docs there (never into the git repo's docs/ folder, which is for user-facing docs only — CLI, installation, custom apps, templates).