dotfiles

USE FOR: This dotfiles environment and its agent harness: machine setup (Ubuntu, WSL2, macOS, home-manager, nix-darwin), daily Nix operations and upgrade/recovery, missing CLI tools / command not found, operating concepts, clipboard (Vim, Neovim, tmux), Claude Code and Codex CLI config, hooks, MCP, skill installation, postman routing, orchestrator runbooks, tmux workspaces, issue/PR worktrees, pane operations, prompt/review contracts, resume handoff; Agent Skills authoring: add/edit/validate skills, Waza, publishing. DO NOT USE FOR: Nix package authoring (programming).

USE FOR: Clarify concepts before names harden by fixing concrete referents, roles, sequence, candidate terms, and first-use definitions. Use for terminology-heavy design docs, research synthesis, cause-isolation or mitigation plans, naming decisions, and reasoning-order summaries only when concept/referent ambiguity could distort the work. DO NOT USE FOR: ordinary terminology/glossary editing when referents are stable, simple editing, translation-only work, proofreading, generic summarization/research, implementation, or broad content generation.

USE FOR: Implementation plans and durable task tracking: reduce ambiguity, compare options, parallel investigation, multi-source synthesis, review gates, task artifacts, evidence logs, handoff/resume, and DONE/BLOCKED verification. DO NOT USE FOR: unrelated tasks, broad rewrites outside the request, or generated runtime outputs.

USE FOR: Verifying technical claims, comparing options, and investigating unfamiliar libraries/APIs/tools with cited, confidence-rated evidence. DO NOT USE FOR: implementation, opinion without evidence, or tasks better served by a narrower repo-specific skill (e.g. `data-platform`, `collaboration`).

USE FOR: Prose QA, Vale/Harper, terminology, English/Japanese edits, English-to-Japanese, stable glossaries, rhythm, AI-slop cleanup, publication QA. DO NOT USE FOR: AI detector/humanizer workflows, fresh generation, meaning-changing rewrites, replacing author judgment, publishing, model/cost/privacy, external sharing, or chunking.

USE FOR: Reference-only external provider packs and dormant source inventory: dbt, azure, databricks-official, obsidian, hashicorp-terraform-codegen, hashicorp-terraform-module, hashicorp-terraform-provider, google, aws, Databricks, Azure, Microsoft Foundry, Google Cloud, GCP, AWS, Terraform, HashiCorp, Obsidian, provider-pack lookup, and promotion questions. DO NOT USE FOR: repo-local guardrails, harness implementation, or making provider packs active without explicit promotion.

USE FOR: Repo-local BigQuery, Databricks, dbt, restricted BigQuery/dbt safety, and cloud auth workflows. DO NOT USE FOR: harness, diagrams, or generic code.

USE FOR: Programming/debugging: Bash, Python/Jupyter quality, Nix package workflow, Terraform with Checkov, Markdown, TDD/Tidy First, and root-cause isolation. DO NOT USE FOR: agent harness, data-platform, diagramming, or GitHub workflow work.

USE FOR: Read BEFORE any git or GitHub action (issue, branch, commit, push, PR create/review) — sets the issue-first, worktree-based default via issue-worktree-create. GitHub/Jira/Confluence: gh CLI, PR/commit/issue management, review style, public path hygiene; Atlassian Cloud when env vars are confirmed. DO NOT USE FOR: guessing credentials, unrelated tasks, broad rewrites, or generated runtime outputs.

USE FOR: `$create-review-comment`, ai-create-review-comment, or terse PR-review-comment requests. Infers the PR and routes postman substantive review through guardian/critic without exposing mechanics. DO NOT USE FOR: unrelated tasks, broad rewrites, generated outputs, or posting comments without explicit approval.

USE FOR: draw.io and Mermaid diagram authoring, preview, export, layout, color, and asset workflows in this repo. DO NOT USE FOR: data-platform or generic coding tasks.

USE FOR: Guardian/critic reviews: native multi-perspective reviewer waves, peer critic review evidence, guardian verdict aggregation, synthesis of blocking findings. DO NOT USE FOR: implementation, dispatcher fan-out, model/tier overrides, or public posting.