bim-ba

creating-drift-logs

Use when you notice a divergence between actual session behavior and codified instructions (one of the 8 drift triggers) — captures it as an immutable drift-log entry under .claude/drift-log/open/ so good conventions can be promoted later.

Data & Documents Listed

documenting-meetings

Use when documenting a meeting from an SRT audio transcript — produces structured meeting notes with decisions, action items, and discussion summary

Data & Documents Listed

handling-secrets-safely

Use when inspecting, probing, or reporting on any credential-bearing file (.mcp.json, .env, *.pem, ~/.git-credentials, ~/.netrc, a secret store) or when clearing a "no secrets" / security-sweep verdict - the mechanics that keep a well-intentioned command from leaking a value through tool output, a diff echo, a query error, or a shallow history scan. The high-level policy (where secrets live, rotation) is assumed; this is the HOW.

researching-rigorously

Use for any research, validation, or fact-check task -- before answering a load-bearing question or committing to an approach. Orients via local sources and knowledge tools, fans out parallel subagents per source, cross-validates via MCP servers and web research, and cites sources.

reviewing-agent-instructions

Use when the user wants to review AI-agent instruction files (CLAUDE.md, skills, drift-log, hooks) for pollution, duplication, dead references, contradictions, or architectural debt. Manual on-demand only. Outputs a committed markdown report; does no auto-fix. Always run together with /claude-md-improver for full coverage.

Code & Development Listed

reviewing-drift-logs

Use when triaging the drift-log — promoting open entries to applied, checking staleness, compacting applied entries, or turning an applied insight into a codified rule.

setup

Use when bootstrapping a new (or existing) project to reuse the shared ai conventions — scaffolds drift-log, a thin CLAUDE.md, and wires the requested ai plugins (`core` always) into `.claude/settings.json`. Idempotent.

thinning-agent-instructions

Use when a project CLAUDE.md is bloated, predates the canonical skeleton, or duplicates the shared home layers (the ai/core behaviour-protocol and the personal ~/.claude/CLAUDE.md) - thins it to the 10-section skeleton by removing content the home layers already provide while preserving every project-specific fact. The FIX companion to reviewing-agent-instructions (which only audits). Do NOT use it to change project rules or to edit a CLAUDE.md that is already thin and conformant.

Testing & QA Listed

using-playwright

Use when driving any web UI through the Playwright MCP -- logging into SSO-gated portals, filling Monaco or textarea editors, extracting page content, or operating internal tools via browser automation. Covers session/login handling, reliable text input, snapshot-vs-screenshot, and token-efficient extraction.

Data & Documents Listed

clickhouse-query-best-practices

Use when writing or reviewing ad-hoc research SQL in a dbt-ClickHouse project, or running federated queries via `postgresql()` from ClickHouse for data-quality investigations — covers CTE-wrapping of federation, dedup via `limit 1 by`, flow analysis with `groupUniqArray + arraySort`, runtime-computed boundary dates, hybrid PG/CH source selection, source-of-truth citation, and style.