hyprland-config

Reset ~/.config/hypr to a minimal bare-bones Hyprland config (full backup + live-test + auto-rollback)

Use this agent to author the functional config for ONE desktop surface (waybar, launcher, notification daemon, terminal emulator, lock screen, or a Hyprland topic file) given the interview answers + the rice palette. The rice skill (Mode A3b) spawns several of these in parallel — one per surface — so the per-component writing doesn't serialize on the main loop. Each agent reads the relevant recipe file, fills the template against the answers, validates the output, and returns the staged file path(s). Do NOT use this for theming an EXISTING file in place — that's the edit-config flow.

Use this agent when a Hyprland config has just been generated or edited and needs checking before it goes live, or when the user asks to "validate my hyprland config", "check hyprland.conf for errors", "lint my Hyprland setup", or "is my hyprland config correct". Typical triggers include the rice skill finishing a write (Mode A5 step 1), the edit-config skill finishing a non-trivial edit (step 5 — invoke routinely, not just on demand), a user pointing at a hyprland.conf or ~/.config/hypr directory and asking whether it is valid, and a user reporting that Hyprland failed to load a config. See "When to invoke" in the agent body for worked scenarios.

Use this agent to run the rice from-scratch interview (28-38 AskUserQuestion calls across 23 groups) and persist every answer to a structured answers.json file. Invoked by the rice skill (Mode A1). Owns the entire interview so the main rice loop never has to hold 28+ Q/A rounds in context — it returns just the path to answers.json + a tight summary. Includes a final "review your picks" pass where the user can approve or fix specific groups. Do NOT invoke for one-off questions, theming-only flows (Mode B/C/D), or anything that isn't a full from-scratch build.

Use this agent to install the packages a rice config needs — typically invoked by the rice skill (Mode A5) with the generated install.sh, or by edit-config when an edit needs a tool that isn't installed. Pass the install.sh path (and optionally a smaller package list for ad-hoc installs). The agent handles pacman/AUR-helper routing, AUR-helper bootstrap (paru/yay), retries transient failures, and returns a structured verdict. Do NOT invoke for searches, version checks, or anything that doesn't actually install.

This skill should be used when the user runs "/hyprland-config:dotfiles" or asks to version-control, back up to git, or sync their config/dotfiles — e.g. "put my hyprland config in git", "version control my dotfiles", "set up a dotfiles repo", "commit my config", "push my dotfiles", "track my config in git", or "back up my rice to github". Initializes a dotfiles git repo (bare-repo, GNU Stow, or chezmoi), tracks the Hyprland/desktop configs, and commits/pushes — committing after each verified change.

This skill should be used when the user runs "/hyprland-config:edit-config" or asks to change, fix, inspect, or test an EXISTING desktop config — Hyprland (`~/.config/hypr/*.conf`), the desktop-shell pieces around it (waybar, wofi/rofi/fuzzel, mako/dunst/swaync), the terminal shell (bash/zsh/fish — prompt, aliases, fetch), or any companion daemon's config (hyprlock/hypridle/hyprpaper). Examples: "add a keybind", "change my gaps", "add a window rule", "add a module to my waybar", "swap my launcher to rofi", "make my notifications stay longer", "add a starship prompt", "set up zsh aliases", "read my hyprland config", "test my config". Reads the current files, makes the change in the right place, and **verifies after every edit** with automatic rollback (Hyprland: `hyprctl reload` + `configerrors`; bar: JSON parse + `SIGUSR2`; shell rc: parse-only — never sourced). To build a config from scratch, use rice instead.

This skill should be used when the user asks about Hyprland configuration syntax, "hyprland.conf", how to configure monitors, input, decoration, animations, keybinds/keybindings, dispatchers, submaps, window rules, layer rules, workspace rules, gestures, or environment variables in Hyprland, what a Hyprland config option or hyprctl keyword does, whether a Hyprland option is deprecated or renamed, to review/audit an existing hyprland.conf for outdated syntax, or about the Hyprland ecosystem and companion packages (hyprlock, hypridle, hyprpaper, hyprpicker, hyprsunset, hyprpolkitagent, waybar, status bars, launchers like wofi/rofi/fuzzel, notification daemons, clipboard managers, screenshot tools, portals/screen sharing) and how to wire them in. Also covers how to make the desktop look visually appealing — styling guides for waybar, launchers, notifications, terminals, hyprlock, GTK/Qt apps, btop/cava/fastfetch/starship, and the Hyprland decoration/animation look, plus cross-cutting design principles (palette coherence, accent, spacing, transparency, fonts) drawn from how the community rices these. Provides authoritative reference material for the Hyprland (Wayland compositor) config language, ecosystem, and visual styling.

This skill should be used when the user runs "/hyprland-config:rice" or asks to build, theme, or restyle their Hyprland desktop — i.e. (1) GENERATE a config from scratch ("generate/create my hyprland.conf", "set up Hyprland from scratch", "make me a new config", "build a hyprland config"); (2) THEME/recolor/set fonts ("theme my desktop", "apply Catppuccin/Gruvbox/Nord/Tokyo Night/Dracula/Everforest/Kanagawa/Solarized/Rosé Pine", "change my color scheme/accent", "match my colors to my wallpaper", "set up matugen/wallust", "change my font"); (3) manage named theme PROFILES / "rices" ("save my theme as X", "switch to nord", "list my themes", "load my <name> rice", "pin my accent"); or (4) set/change/cycle the WALLPAPER ("set my wallpaper", "random wallpaper", "make my theme match my wallpaper"). It runs one interactive interview, generates a modular version-matched config, and drives a self-contained rice engine (~/.config/hypr-rice/ — one palette.conf + templates + a `rice` CLI + profiles + a user-override cascade) that themes Hyprland, hyprlock, waybar, notifications, launcher, terminal, GTK/Qt/cursor/icons/fonts and the wallpaper consistently — backing up, live-testing, and reloading after every change.