config

REQUIRED for end-user customization of Linux desktop, window manager, or system config. Use when editing ~/.config/hypr/, ~/.config/waybar/, ~/.config/walker/, ~/.config/alacritty/, ~/.config/kitty/, ~/.config/ghostty/, ~/.config/mako/, or ~/.config/omarchy/. Triggers: Hyprland, window rules, animations, keybindings, monitors, gaps, borders, blur, opacity, waybar, walker, terminal config, themes, wallpaper, night light, idle, lock screen, screenshots, layer rules, workspace settings, display config, and user-facing omarchy commands. Excludes Omarchy source development in ~/.local/share/omarchy/ and omarchy-dev-* workflows.

REQUIRED when the user explicitly says "buddy", "task-buddy", or "verify-buddy" (or plurals "buddies", "task-buddies", "verify-buddies", and close variants like "use buddy", "run a task-buddy", "do a verify-buddy", "run 4 verify-buddies"). Do not trigger on generic phrases like "second opinion", "external review", "another model", or "GPT" -- only on the literal terms buddy / task-buddy / verify-buddy (and their plurals).

Conventions for creating or modifying personal scripts in ~/workspace/conf/bin. Trigger when adding, editing, or discussing scripts in the bin directory.

Create, refine, review, merge, and archive project plan files. Use when the task is about planning work, naming plan files, creating new plan documents under ./plan, or archiving completed plans into ./plan-archive.

Prompt template for exploring open-source code (extracted from paint/note). User will refine later.

Prompt template for exploring open-source code (extracted from paint/note). User will refine later.

Prompt template for exploring open-source code (extracted from paint/note). User will refine later.

Prompt template for exploring open-source code (extracted from paint/note). User will refine later.

Use this skill whenever you need the project root path from the current directory. It applies when the user asks for a repo root, workspace root, top-level project path, or when commands should be anchored at the nearest ancestor containing .jj or .git. If no repository markers exist, use the current working directory.

Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.

REQUIRED for all version control work. Uses the v* scripts in ~/bin to handle jj and git transparently. Trigger on status, diff, log, commit, push, pull, describe, or any VCS request. If .jj/ exists, the scripts use jj. Otherwise git.

Use for git workflows when a repository is git-only. If .jj/ exists, defer to the jujutsu skill and do not run git commands. Trigger on status, diff, log, commit, branch, merge, rebase, push, pull, and PR requests.

REQUIRED for version control work in repositories containing .jj/. If .jj/ exists, use jj only and never git. Trigger on commit, status, diff, show, log, history, or any VCS request.