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…

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",…

Use when transforming text into a specific literary style, analyzing the style of a text sample to extract its characteristics, blending or combining multiple styles with weights, writing in a particular genre voice, or creating a style profile from example…

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.…

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…

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…

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:…

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…

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…