dotfiles

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when executing implementation plans with independent tasks in the current session

Use when you have a spec or requirements for a multi-step task, before touching code

Fast, MVP-focused grilling session for plans, prototypes, designs, or feature ideas. Use when the user wants to stress-test direction, clarify assumptions, reduce scope, or get challenged without a long decision-tree interview.

Execute and orchestrate multiple AI agent CLIs (agy, Codex, Cursor, Claude Code, Pi) for getting alternative opinions, comparing approaches, or leveraging different AI models' strengths. Use when the user explicitly mentions agent names like "ask agy", "ask cursor", "ask codex", "ask pi", "use composer", "use pi", "try grok", or when needing diverse perspectives on complex problems, alternative implementation approaches, or multi-agent collaboration.

Summarize a video (URL or local path) by pulling captions first, falling back to audio-only transcription, and optionally extracting frames for visual summaries. Use when the user pastes a YouTube/Vimeo/X/etc URL, points at a local video file, or asks to summarize, watch, or extract takeaways from a video. Triggers on "summarize this video", "what's in this video", "watch this", URLs ending in /watch, /shorts, common video extensions (.mp4/.mov/.mkv/.webm).

Multi-provider web search fanout across Exa, Tavily, Brave, LangSearch, and Marginalia with parallel dispatch, dedupe, and AI summary. Use ONLY on explicit user intent for a named provider (Exa, Tavily, Brave, LangSearch, Marginalia), cross-provider fanout, semantic code/paper search, indie small-web search, or when native web search returned weak results. Do NOT auto-pick on generic search queries; native WebSearch is preferred for those.

Load before any Jira interaction or mcp__atlassian__* call. Holds required field values (team ID, sprint IDs, custom field mappings) unavailable elsewhere; skipping causes missing fields on created tickets. Triggers: Jira URLs, ticket keys (e.g. ABC-123), MCP tools mcp__atlassian__*, acli, or keywords create/read/edit/search/transition, ticket, Jira, issue, sprint, backlog, refinement, work item.

Simplify and reduce code while preserving behavior. Use when the user asks to simplify, clean up, refactor, audit, report on, or reduce recently changed code. Supports apply mode for edits and report mode for findings only.

Review current branch changes against a target branch. Use when the user asks to review a branch, review changed files, compare current work to main, origin HEAD, or master, or run a file-by-file code review with aggregated markdown results.

Simplify and reduce tests while preserving coverage. Use when the user asks to simplify, deduplicate, reduce, or clean up test files using techniques such as equivalence class partitioning, decision tables, or pairwise testing.

Personal Obsidian CLI mechanics and patterns not covered by the base `obsidian-cli` skill. Load when driving the Obsidian CLI for content creation, file operations, vault hygiene, or version history. Triggers on: "search my vault", "find notes about", "show orphan notes", "find broken links", "rename this note", "move this note", "show note history", "restore version", "list backlinks", "show outline", "heredoc obsidian", "obsidian fallback", "vault hygiene".

Durable repo-specific notes: project findings, investigations, decisions, coding lessons, failure analyses, and implementation findings. Distinct from the agent's native memory feature. Triggers: "save to project notes", "project notes", "save this to my notes", "note this for the project", "log this finding", "save project notes", "save this project finding", "log this investigation", "coding lesson", "project decision", "remember this for this repo", "document this bug investigation".

Second-brain long-term wiki notes and personal documentation. High-priority over generic Obsidian skills for vault content routing. Load this first when the user asks to search, read, create, update, move, or organize notes in their vault. Routes reusable knowledge and vault-wide personal docs. Triggers: "second brain", "my vault", "Obsidian", "my notes", "my wiki", "save to second brain", "what do I have on", "find notes about", "quick note", "daily note".

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Canonical rules for creating GitHub pull requests via `gh` - title, body format, visibility gate, and creation workflow. Load on any intent to open, create, or draft a pull request. Triggers include explicit asks ("open PR", "create PR", "gh pr create", "ship PR", "draft PR", "let's PR this") and implicit signals (user just finished a branch and is wrapping up, related slash command invoked).

Use when a `discussion_rNNN` URL anchor appears, when replying to a specific PR review comment (CodeRabbit, human reviewer), reading all reviews on a PR with their replies as a tree, or resolving review threads from the CLI. Triggers on "reply to coderabbit", "answer this review comment", "read all reviews on PR", "show review threads", "resolve this thread".

Interview the user about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Rules for git commits - format, staging, visibility gate, workflow. Load on intent to commit, stage, or compose a commit message. Triggers: "commit", "write a commit message", "stage this", "let's ship", "ready to push", conventional commit, selected file `.git/COMMIT_EDITMSG`, wrapping up work, related slash command.

Rules for creating new git branches - naming and workflow. Load on intent to start a branch. Triggers: "new branch", "create branch", "checkout -b", "switch -c", "start branch", "branch off", or Jira ticket as starting point.

Enforces strict CSS and CSS Modules policies for ALL CSS authoring, including stylesheet files (.css/.scss/.module.css) and CSS-in-JS (styled-components, Emotion, vanilla-extract, styled-jsx, Stitches, template literal styles embedded in TS/JS files). Use when creating, writing, or editing ANY CSS, styled component, or inline style block. Triggers include: component styles, global stylesheets, theme files, design tokens, animations, keyframes, utility classes, styled.X or styled() definitions, or any agent-authored CSS content.

Writes unit tests for JavaScript/TypeScript and frontend projects using Vitest or Jest. Use when writing or running tests.

Load before any Neovim help, documentation, or Lua API lookup. Defines how to read Neovim docs from disk or online. Reading docs via `nvim --headless` or any other `nvim` subprocess is FORBIDDEN; Triggers: "Neovim docs", `:help`, `:h <topic>`, `runtime/doc`, Neovim Lua API lookups, "how does Neovim do X" questions.

Writes React components and hooks using TypeScript. Use when creating or modifying React components, hooks, or JSX.

Enforces strict TypeScript and JavaScript style policies for ALL .ts/.tsx/.js/.jsx file operations. Use when creating, writing, or editing ANY TS/JS code. Triggers include: components, hooks, services, utilities, classes, interfaces, types, schemas, tests, scripts, configuration files, or any agent-authored TS/JS content.