dotfiles

Use when improving Codex steering, token/context cost, hooks, skills, plugins, MCPs, or dotty-managed config.

Generic Godspeed list and label discovery, inbox triage, and API-backed task organization for a mirrored GTD setup with work and personal folders. Use when Codex needs to inspect Godspeed lists, summarize inbox or active tasks, or apply explicit task updates through the Godspeed API without tracking personal taxonomy in the repo.

Use when TypeScript or TSX work needs guidance on API shape, function signatures, exported contracts, strict typing, lint-safe escape hatches, or lightweight off-the-shelf library choices for JS/TS tools.

Use when diagnosing terminal or TUI rendering problems: ANSI color/theme mismatches, truecolor vs xterm-256 vs terminal-palette behavior, Markdown/code renderer differences, pager output, tmux or fzf preview wrapping, or CLI UI screenshots that look different from expected.

Use when writing a new README from scratch, creating, auditing, or updating README/repo landing pages, setup docs, CLI docs, contributor notes, AGENTS/repo steering docs, or docs drift checks.

Use when React or frontend work needs guidance on cleanup and simplification, component boundaries, hooks, context, rendering, testing, or modern React defaults.

Use when drafting or editing Slack messages, PR descriptions, Jira comments, review comments, status updates, or other prose where the user's personal writing style matters.

Roll out releases of shared personal packages, config packages, lint/style configs, Raycast clients, Codex skills/config, or other reusable tooling to downstream local repositories. Use when Codex releases or updates a shared package and should find dependents, bump dependency versions, run lint/checks, apply required style or API fallout fixes, commit, and push the downstream updates.

Use when creating or editing Bash, shell, or zsh scripts, including `.sh`, `.bash`, `.zsh`, shell hooks, and CLI helper scripts.

Use when editing Nerd Font icons, Private Use Area glyphs, terminal prompts, tmux status bars, or CLI UI symbols.

Generic frontend styling and layout guidance for CSS, style objects, utility classes, and layout props. Use when working on spacing, sizing, positioning, overflow, stacking, responsive layout, or visual containment where the problem is not framework-specific.

Help incrementally grow or refine a personal Neovim config, especially when adding navigation, file picking, file browsing, search, keymaps, LSP, formatting, UI, or editor workflow improvements. Use when Codex should inspect the existing `vim.pack`-based setup, research modern Neovim best practices and plugin docs, compare one recommended approach plus one fallback, use trusted community dotfiles as inspiration, and then implement the chosen option with small teachable changes.

Use when Slack message wording is already drafted and the goal is to copy or paste it as Slack-preserved rich text from macOS, using the shared `slack-rich-text` helper instead of hand-fixing formatting after paste. Prefer authenticated Slack delivery tools when the user wants the message actually sent or delivered.