urmzd/dotfiles / dot_agents/skills/manage-theme
manage-theme
VerifiedSwitch, create, or debug the color theme of a machine set up by urmzd/dotfiles: one theme colors Ghostty, Neovim (colorscheme and lualine), tmux (catppuccin flavour and colors), and the dotfiles' own output. Covers `dotfiles theme` / `dotfiles theme set`, writing a themes/<name>.toml or a pack's theme.toml, and per-shell output overrides (DOTFILES_UI_*). Use when the user says "switch to tokyonight", "change my terminal colors", "make a theme for our team", "my nvim colors did not change", or "use ASCII output in CI". Do NOT use for a project's brand identity, fonts, or demo capture (use style-brand), for installing apps or other machine upkeep (use manage-machine), or for editing unrelated chezmoi templates (use dotfiles).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.8 KB |
| evals/eval_queries.json | config | 1.6 KB |
evals/eval_queries.json
View on GitHub{
"skill": "manage-theme",
"description": "Routing evals: does the query ask to switch, create, or debug the dotfiles machine theme (Ghostty, Neovim, tmux, dotfiles output)? Near-misses route to style-brand (project brand identity), manage-machine (installs and upkeep), and dotfiles (repo template edits).",
"queries": [
{ "query": "switch my terminal and nvim to tokyonight", "should_trigger": true, "note": "dotfiles theme set tokyonight." },
{ "query": "what themes do I have", "should_trigger": true, "note": "dotfiles theme." },
{ "query": "make a theme with our company colors for everyone on the team", "should_trigger": true, "note": "theme.toml in the team pack." },
{ "query": "my neovim colors didn't change after switching themes", "should_trigger": true, "note": "Debug: restart, check theme.lua." },
{ "query": "use plain ASCII output for dotfiles in CI", "should_trigger": true, "note": "DOTFILES_UI_THEME=plain." },
{ "query": "change the tmux status bar colors", "should_trigger": true, "note": "[tmux.colors] in a theme." },
{ "query": "set up the brand font and demo GIF style for my project README", "should_trigger": false, "note": "Project identity; use style-brand." },
{ "query": "install ghostty and raycast", "should_trigger": false, "note": "Installs; use manage-machine." },
{ "query": "add a new nvim plugin for git blame", "should_trigger": false, "note": "Editing nvim config; use dotfiles." },
{ "query": "add a run_onchange script for zig", "should_trigger": false, "note": "Repo authoring; use dotfiles." }
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |