demos

Author and build multi-page Asciidoctor documentation sets in the house style. Use this skill when the user wants to: - Bootstrap a new docs/ directory (Asciidoctor + asciidoctor-diagram + asciidoctor-revealjs, multi-page HTML output). - Add a new page to an existing wiki and have it follow the conventions (Diátaxis filename prefix, H1 per file, xref pattern, shared includes, docnav footer). - Add or restyle a mermaid / plantuml / state / Gantt diagram so it matches the project's mermaid.css palette. - Wire up between-page navigation (the `// docnav-start` / `// docnav-end` footer block) so xrefs feel like a book. - Build the wiki locally (mise + bundler + Make). Do NOT use this skill for general prose editing, README rewrites that do not touch the build/conventions, or non-Asciidoctor doc systems (Sphinx, MkDocs, Docusaurus, etc.).

Spin up a throwaway local Postgres cluster for DB-gated tests that skip without PG_TEST_DSN. Use when SQL/integration tests print "skipping" and you want to run them locally instead of leaving them skipped.

Use when a migration phase produces wrong results silently, a gate fires green when it should not, parity reports RED but the process exits 0, pgloader completes but data is missing, or any situation where the pipeline "succeeds" but the output is wrong. Covers the systematic approach to root-causing silent-failure bugs specific to this codebase.

Use when auditing the hand-authored AsciiDoc prose under docs/ for accuracy and staleness, verifying a doc claim against source of truth, or before a release/cutover when the docs must be trustworthy. The repo moved many facts into generated partials and a verify-doc-facts net, but hand-authored prose still drifts silently because nothing checks it. Covers the source-of-truth audit method, the recurring staleness patterns in these docs, and how to report and fix findings.

Use when reviewing or changing credential handling, SQL interpolation, Secrets Manager integration, pgloader configuration, connection string redaction, healthz probing, or any code that touches sensitive data in this migration pipeline. Covers the specific security surfaces this codebase exposes: f-string SQL injection, credential leaks in logs, trust of external tool exit codes, and non-interactive guards.

Use when implementing or fixing migration phase logic, SQL transforms, gate behavior, or parity checks in this repo. Applies TDD to the specific failure patterns this codebase has: silent exits on failure, gate bypasses, data quietly dropped, and exit-0-on-RED bugs. Required before writing any phase module change, SQL file, or fix commit.

Run ad-hoc, read-only analysis queries against a MySQL database using DuckDB's MySQL extension, without installing a Python MySQL driver and without exposing the password. Use when you need to explore/profile a source MySQL DB (counts, distributions, distinct values, free-text categorization) for a migration or investigation, especially when the project already depends on DuckDB but has no pymysql/mysqlclient/connector, or when you only have a connection URL in a .env file.