Cross-platform dotfiles managed by Chezmoi with Homebrew/apt and per-language version managers. One-command bootstrap for macOS and Linux with Neovim, Tmux, Zsh, and AI agent skills.
Designs interface-first system architecture: decomposes modules, enumerates 2-3 approaches with tradeoff tables, recommends a path on Easy-to-Change grounds, and stages phased delivery plans with per-phase verification. Use when you need a design doc, module boundaries, an API contract, or a phased rollout plan before…
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…
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…
Watches ONE tmux pane in an orchestrated fleet read-only: polls state, and on transition captures the smallest evidence slice and emits a single contract line, pinging only on needs-permission, error, done, or stuck. Never approves prompts, never edits code, never speculates. Use when the orchestrate-agents skill…
Generates and ranks divergent feature and UX concepts before constraining: expands a prompt into multiple variations, describes how each feels to use, and returns ranked concepts with effort and risk noted. Use when brainstorming features, exploring UX possibilities, or wanting options before committing to one.…
Executes write-capable multi-repo sweeps and batch operations: enumerates every target, dry-runs on one, presents a diff for approval, then applies across the full set with progress tracking and coverage verification. High blast radius (edits and runs scoped git/gh across many repos), so it gates on approval and halts…
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…
Authors concise, outcome-focused technical documentation for a single file: structures frontmatter and sections, leads with the action, uses tables over prose, avoids em dashes, verifies claims against source, and treats examples and gotchas as mandatory. Use for writing or rewriting one README, skill file, or API doc…