القائمة
Use first for bounded code edits, refactors, implementation, simplification, control-flow cleanup, or maintainer clarity before choosing a more specific theory skill.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
| name | code-change-core |
| description | Use first for bounded code edits, refactors, implementation, simplification, control-flow cleanup, or maintainer clarity before choosing a more specific theory skill. |
Use first for bounded code edits, refactors, implementation, simplification, control-flow cleanup, or maintainer clarity before choosing a more specific theory skill. This is a router skill: use it to select the smallest relevant leaf skill, then read that leaf skill before doing the work.
Classify the code-change force first. Read exactly one primary leaf skill unless the task clearly spans two forces.
SKILL.md before implementing, reviewing, or advising.| Leaf Skill | Use When |
|---|---|
programming-as-theory-building | Default for non-trivial code changes where domain rules must map to code behavior. |
essential-complexity | Use when simplification is requested and the risk is erasing real domain complexity. |
structured-programming | Use when the main problem is tangled branching, loops, exits, callbacks, or mutable control state. |
stepwise-refinement | Use when implementing a feature or algorithm from a high-level specification in small refinements. |
literate-programming | Use when the main problem is maintainer understanding, examples, comments, or explanatory order. |
Before loading a leaf, answer briefly:
Then load the chosen leaf skill and follow its workflow. Do not blend every nearby theory into the task; route narrowly and let evidence pull in more context only when needed.
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 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.