donaldfilimon

Synchronize ABI Markdown and docs claims with executable behavior. Use before editing README, AGENTS.md, CLAUDE.md, GEMINI.md, docs/**/*.mdx, walkthroughs, changelogs, or any old ABI Markdown that mentions WDBX, MCP, GPU, clustering, compression, FHE, agents, or benchmarks.

Validate ABI docs and external collateral against repo evidence and docs/contracts/external-claims-audit.mdx. Use when auditing claims, scanning docs for unsupported QPS/sharding/FHE/AES language, checking one claim before publish, or re-confirming the external-claims audit. Agent procedure only — not a CLI or slash command. Pair with abi-doc-claims-sync when editing docs.

Plan and execute ABI repo work from the TODO board, roadmap/spec docs, Zig 0.17 constraints, and validation gates. Use when the user asks to find ABI todos/roadmaps, organize a large implementation from tasks/todo.md, or decide the next safe work slice. Distinct from the goals skill — that skill owns the persistent ledger tasks/goals.md; this skill plans from the active board and north-star specs.

TUI/dashboard superpower. Launch interactive agent REPL, diagnostics dashboard panes, and slash commands via real abi CLI paths. Use when working on abi tui / dashboard / agent tui. There is no /abi-superpower-tui binary.

Build the abi CLI and non-interactively smoke the diagnostics dashboard — render `abi dashboard` one-shot (stdin from /dev/null forces the non-interactive fallback), assert exit 0 and all 5 panels (System, Plugins, WDBX Storage, Scheduler, Memory). Use to smoke-test `abi dashboard`/`abi tui`/`abi --tui` in CI or headless without hanging in the interactive TUI. Complements run-tui (which drives the interactive path via tmux).

Capture, track, and execute goals for the abi Zig project. Use when the user wants to record a goal, see outstanding goals, update goal status, or break a goal into a verified work slice. Distinct from abi-goal-orchestrator (which plans from the TODO board) — this skill owns a persistent goal ledger and drives goal-to-slice execution.

TUI/dashboard OpenCode plugin. Launch interactive agent REPL, diagnostics dashboard panes, and slash commands via real abi CLI paths. There is no /abi-superpower-tui binary.

Set up and operate abi through opencode — how opencode discovers abi skills, slash-commands, and MCP servers. Use when the user asks about opencode config, why an abi skill is not loading in opencode, or how to add a skill to the opencode allowlist.

Use when auditing the ABI Zig codebase, reviewing feature parity, checking stale docs, finding safety risks, or preparing code review findings for GPU, WDBX, MCP, CLI, AI routing, connectors, scheduler, memory, or plugin changes.

Use when defining ABI framework goals, roadmap, task lists, modernization plans, verification plans, or cross-cutting work across GPU, WDBX, AI model completion/training, MCP, TUI, CLI, and docs.

Use when configuring zls, OpenCode LSP, Zig diagnostics, abi-lsp workflows, editor integration, or troubleshooting Zig 0.17 language-server/build issues in the ABI repo.

Use when redesigning or refactoring the ABI Zig framework, planning module boundaries, splitting features, simplifying APIs, or changing GPU, WDBX, MCP, CLI, AI, scheduler, memory, plugin, or connector architecture.

Use when cleaning, syncing, or configuring hidden AI-tool directories such as .claude, .config/opencode, .opencode, .gemini, .agents, .codex, .copilot, or plugin and skill stores.

Use when writing, reviewing, migrating, or debugging Swift 6.3 code, especially strict concurrency, Sendable, actors, SwiftPM, Swift Testing, macros, and Apple-platform builds.

Use when writing, reviewing, migrating, or debugging Zig 0.17 code, especially build.zig, std.Io, std.process.Init, allocator, import, POSIX, and Darwin linker failures.