AnamKwon

Use when organizing a large local skill library into category router skills, refreshing a compact skill inventory, or deciding which leaf skill bodies need to be read before agent classification.

Use first for ambiguous failures, messy project context, surprising results, repeated failures, postmortems, or contested product and architecture framing.

Use first for API boundaries, module ownership, domain modeling, contracts, architecture seams, and recurring design structures.

Use first for bounded code edits, refactors, implementation, simplification, control-flow cleanup, or maintainer clarity before choosing a more specific theory skill.

Use to organize a large skill library into category routers, route new skills, and propose new categories when existing routers are insufficient.

Use first when the user asks for tests, correctness, high reliability, static reasoning, proof, or safety evidence.

Use first for work shaped by users, tools, procedures, runtime evidence, operational artifacts, interfaces, or organizational workflows.

Use when writing, generating, modifying, debugging, reviewing, or refactoring code. Treat code work as rebuilding and preserving the program theory: how real-world affairs map into program behavior, why the current shape exists, which existing facility the new demand resembles, and what observable behavior proves the change belongs.