domain
01Agent
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
25 tagged neovim, measured the same way as everything else here.
Browse within: dotfiles 19tmux 14zsh 11chezmoi 8nvim 8vim 8config 7nix 7nix-darwin 7
Agent
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
Agent
Issues and PRDs for this repo live as GitHub issues in Cannon07/code-preview. Use the gh CLI for all operations.
Agent
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
Agent
Use this agent for ALL browser automation (test pages, screenshots, console errors, health checks). Never use browser tools directly. Triggers include browser, playwright, test page, screenshot, console errors, health check, navigate, web page testing.
Agent
Next.js development specialist using Next.js DevTools MCP. Always use this agent to query the Next.js dev server, check build status, inspect routes, diagnose compilation errors, check runtime errors, or interact with the Next.js MCP endpoint. Returns focused diagnostics and recommendations.
Agent
Use this agent for ALL Notion API operations (create, search, fetch, update). Never use Notion MCP tools directly. Triggers include notion, writing database, create page, search workspace, fetch page, update page, query database.
Agent
An Agent to create PullRequests.
Agent
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
Agent
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
Agent
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
Agent
An issue-planning agent that examines a repository's actual code and creates an implementation plan. Other agents handle gathering decisions, updating the issue, and creating sub-issues.
Agent
An independent review agent for testing claims, assumptions, and conclusions in documents, code, plans, blogs, and other work. It receives an evaluation method and the material to review, without changing that material.
Agent
A guided technical-blog writing assistant that gathers the outline, sources, ideas, and publishing format before writing from repository files and reference materials.
Agent
Sweeps documentation, formatting, naming, and cross-project conventions for consistency: audits the current state, references the governing standard, and applies the same fix across every instance, returning a deviation table. Use when you need a consistency pass, documentation hygiene, no-em-dash cleanup…
Agent
Performs evidence-based root-cause analysis: quotes the actual error, reproduces it, bisects what changed, forms one testable hypothesis, fixes the cause (not the symptom), and confirms the failing case now passes. Use when something is broken, a test fails, a stack trace appears, or you need fast diagnosis of a…
Agent
Restructures multi-file documentation sets: organizes docs-site information architecture (getting-started / guides / reference / architecture / contributing), validates content against actual code, removes legacy material with migration notes, enforces no-em-dash prose, and decides what to auto-generate versus…