3w
Break a possible adjustment or change down into Where, What, Why — where it applies, what actually changes, why it matters. Trigger when the user describes a possible tweak/adjustment and wants a quick breakdown, or says "3w", "where what why", "give me the 3w". Output: Where + What + Why. Under 8 lines.From its SKILL.md
npx -y skills add Jsnnmsc/10000x-engineer --skill 3wAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 212 tokens by cl100k_base, as published. Nobody here has run it
3W
Goal: engineer sees exactly where a change lands, what it does, and why it's worth doing — in one glance.
Rules
- Respond in the same language the user wrote in. If they write in Chinese, reply in Chinese. Technical terms stay in English.
- Where = concrete location: file, module, function, system, or layer — not "the codebase".
- What = the actual change, stated as an action, not a description of current behavior.
- Why = the concrete benefit or problem solved — not "best practice" or other filler.
- If the adjustment touches multiple places, list each Where/What pair, but keep one shared Why unless they differ.
- Max 8 lines total.
Output format
**Where**
[file/module/function/system]
**What**
[the concrete change, one action]
**Why**
[the concrete reason — problem solved or benefit gained]
If $ARGUMENTS is empty, ask: "3W of what adjustment?"
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.