skills-from-the-artificerlisted

# Skills from the Artificer — Law Dispatcher This is a **router**, not a law itself. The collection ships 24 laws-of-software reference skills. Rather than recall each one, invoke this skill with a change or decision in hand; it classifies the work and points you at the specific law skill(s) worth applying. ## How to use 1. **Gather the subject.** Identify what you're evaluating: a code diff, a proposed fix, an architecture decision, a plan/estimate, a metric, an API change. If a diff is in play, look at the actual changed lines (`git diff`), not just the description. 2. **Classify it** against the signal table below. A single change usually hits 1–4 laws — not all 24. Resist the urge to dump the whole catalogue. 3. **Invoke each matched law skill** by its name (e.g. run the `hyrums-law` skill, or read `<law>/SKILL.md`). Apply its "Key questions" section to the change. 4. **Report** which laws fired, what each surfaced, and any action items. If nothing matches, say so — a no-op is a valid result. ## Signal → law mapping | If the change involves… | Apply | |---|---| | A public API, interface, or widely-used contract; backward compatibility; deprecation; "is this breaking?" | `hyrums-law` | | Input validation, parsing, protocol/format handling, strict-vs-lenient acceptance | `postels-law` | | Security, auth, encryption, or relying on a hidden algorithm/design for safety | `kerckhoffs-principle` | | Performance work, optimization, "make it faster", complex structures for sp