mtschoen/skills-working-method

using-a-debugger

Use for ANY debugger or memory-forensics work in C#/C++ (and similar native/managed runtimes) - not just bug hunts: verifying runtime behavior, inspecting a healthy process, heap/GC analysis (SOS, dumpheap, gcroot, "who holds a reference to this object"), and…

원문 언어: 영어

effective-refactor

Use when changing code shape without changing behavior - renaming or deleting symbols, changing signatures, extracting methods or modules, moving code, or converting a data shape - especially when the change must touch many call sites. Triggers: about to…

원문 언어: 영어

fast-tests

Use when the agent observes slow test runs in this session (multi-minute wall clock, repeated re-runs blocking iteration, tests dominating the inner loop, thousands of subprocess spawns, coverage/instrumentation overhead) OR when adding tests likely to slow…

원문 언어: 영어

pushback

Use on EVERY user request that proposes work, changes direction, or makes a technical claim - code changes, new features, refactors, pivots, "while you're in there" asks, choice of approach, statements about how the code works. The agent often has code and…

원문 언어: 영어

running-spikes

Use when about to do extended Read/Grep/thinking on a question whose answer is observable behavior of an external system, library, framework, or runtime - prefer learning from running code in a scratch dir over inferring from docs. Suppressed when the…

원문 언어: 영어

research-first

Use before designing, planning, writing custom code, refactoring/extracting code, choosing a tool/library/protocol, or debugging an unfamiliar error. Steers toward running a WebSearch (or Read/Grep for codebase-only questions) BEFORE acting on a decision,…

원문 언어: 영어