StrongAI

Use when implementing any feature or bugfix, auditing an implementation against its plan, or resolving a bug. This is the top-level programming skill that routes to the correct workflow. Triggers on any programming task that isn't purely reading or researching code.

Use when optimizing code performance, reducing resource usage, or improving efficiency. Triggers on "optimize", "make it faster", "performance", "speed up", "reduce memory", "reduce latency", "dispatch optimizers", "efficiency", "latency", "throughput", "slow", "p99", "bottleneck", "too many queries", "bundle size", "cold start", "GC pressure", "allocation", "cache miss", "N+1", or when the user wants independent agents to find optimization opportunities in the same code. NOT for finding bugs (use /dispatch-auditors) or auditing against a plan (use /audit-code).

Internal skill invoked by /programming chain. Use when implementing a single task from a plan. Defines the TDD implementation loop — write tests, implement, validate tests, audit code, repeat if necessary. Each dispatched subagent follows this workflow. Triggers on task execution within a dispatch-programmers context.

Use when creating, editing, or improving Claude Code skills (SKILL.md files). Also use when a skill isn't triggering reliably or needs restructuring.

Internal skill invoked by /programming chain. Use when you have an implementation plan to execute, dispatching subagents per task - triggers on plan execution, task dispatch, subagent workflow

Use when auditing an implementation against its plan. A clean agent follows behind a worker, verifying every decision, obligation, and detail. Triggers on "audit", "verify implementation", "check against plan", "review what was built", or when an implementation phase completes and needs validation before merging.

Use when converting PDF files to markdown for reading, indexing, or processing. Triggers on "convert this PDF", "extract text from PDF", "PDF to markdown", "read this PDF as markdown", "parse PDF", or any task requiring structured text extraction from PDF documents. Uses opendataloader-pdf which requires Java 11+.

Use when you have a spec or requirements for a multi-step task, before touching code

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior

Use when reverse-engineering binaries, executables, shared libraries, GPU shaders, or any compiled artifact. Use when the user wants to understand what compiled code does, extract algorithms from binaries, or analyze shader behavior. Trigger keywords: decompile, disassemble, reverse engineer, binary analysis, Hopper, Ghidra, IDA, Mach-O, ELF, dylib, metallib, shader, objdump, hex dump, assembly, vtable, AIR, LLVM IR. Also triggers on /decompile command. DO NOT trigger on source code review or debugging of code the user wrote.

Use when generating systematic, multi-perspective test coverage for code. Dispatches multiple independent agents with different test-design lenses to produce a comprehensive test suite — covering input boundaries, contracts, error paths, properties, state machines, integration seams, concurrency, regressions, and security. Triggers on "dispatch test designers", "generate tests", "systematic testing", "multi-lens tests", "test coverage", "add test coverage", or after implementation when comprehensive tests are needed. NOT for writing tests during TDD implementation (use /implement). NOT for running existing tests (just run them).

Use when creating or updating a pull request description for an external repository. Use when about to run `gh pr create`, when the user says "write the PR", "create a PR", "update the PR description", or when preparing changes for upstream submission. Also triggers when reviewing existing PRs for description quality. Do NOT trigger for internal branch merges or local-only commits.

Transform technical source material into polished non-technical conceptual writing for non-expert audiences. Use when asked to write a presentation, overview, explainer, or narrative about a technical product or system for potential users, stakeholders, investors, or the general public. Triggers on: "write a presentation about", "non-technical overview", "explain what this does for users", "product narrative", "conceptual overview", "write this for a non-technical audience", "turn this into something readable", or any request to produce reader-facing prose from technical documentation. Also triggers when transforming developer docs, reference specs, or architecture documents into editorial-style writing. Do NOT trigger for technical documentation, API docs, or developer guides -- those need technical precision, not conceptual prose.