From hyprland-config
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hyprland-config:dotfiles [action, e.g. 'set up a bare repo and push to github'][action, e.g. 'set up a bare repo and push to github']This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Put the user's Hyprland/desktop configs under git so the whole rice is reproducible and backed
Put the user's Hyprland/desktop configs under git so the whole rice is reproducible and backed
up, and commit after each verified change. Supports three standard methods — ask which to use
(default bare repo). Treat $ARGUMENTS as the request.
Read references/dotfiles.md for the methods, the bare-repo alias, secrets handling, and
new-machine restore. All operations go through the helper:
${CLAUDE_PLUGIN_ROOT}/scripts/dotfiles.sh.
~/.dotfiles) tracking files in place in $HOME, no symlinks.
Best fit: it versions the live config exactly where the plugin writes it. Recommended default.~/dotfiles. Organized, but restructures files into the
repo and symlinks them back (requires stow).chezmoi).If the chosen tool isn't installed (stow/chezmoi), ask once whether to install it (stow/chezmoi
via pacman); if the user declines, fall back to bare.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/dotfiles.sh" init <bare|stow|chezmoi> [[email protected]:USER/dotfiles.git]
Pass the remote URL if the user has one (or add it later). For bare it sets
status.showUntrackedFiles=no so unrelated $HOME files never show up accidentally.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/dotfiles.sh" add-defaults
Tracks the common desktop config paths that exist (~/.config/hypr, hypr-rice, waybar,
kitty, rofi, wofi, mako, dunst, gtk-3.0/4.0, qt5ct/6ct, swaync, wlogout,
fastfetch, starship.toml). Add more with dotfiles.sh add <path>…. Shell rc files
(~/.bashrc/~/.zshrc) are opt-in — add them explicitly only if the user wants, and warn about
secrets (tokens/keys) first.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/dotfiles.sh" commit "describe the change"
bash "${CLAUDE_PLUGIN_ROOT}/scripts/dotfiles.sh" push # if a remote is set
This is the point of the skill: after any verified config change — a rice generate/theme, an
edit-config edit, a rice apply, a profile switch — run
dotfiles.sh commit "<what changed>" (and push). Suggest doing this automatically as part of
those flows so history stays granular and the remote is current.
Summarize: method, repo location, what's tracked, commit hash, push result, and the remote URL (or
how to add one). For a new machine, give the restore command from dotfiles.md.
showUntrackedFiles=no already prevents accidental $HOME adds. Warn before adding shell rc.stow/chezmoi only after one confirmation if the user picks that method; otherwise fall
back to bare.references/dotfiles.md — the three methods, bare-repo alias, secrets, .gitignore,
new-machine restore, recommended tracked paths.${CLAUDE_PLUGIN_ROOT}/scripts/dotfiles.sh — init / add / add-defaults / commit / push / status.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub nschatz/hyprland-config --plugin hyprland-config