michaelwjohnson
- 3 skills
- 0 followers
- 9 hours ago last updated
- ▌ Check Claims · michaelwjohnsonUse before sending, submitting, or publishing anything containing factual claims — a proposal, report, spec, README, analysis, review, or answer to a question. Catches statements that are fluent and wrong: numbers whose source nobody can name, thresholds attached to the wrong metric, facts that are true of a neighbouring concept, and figures that lost their referent when something was edited. Triggered by: finishing a document, "is this right", stating a baseline or floor or threshold, quoting a number, explaining a metric, any claim a reader would take on trust.
- ▌ Occams Razor · michaelwjohnsonUse when designing, scoping, or reviewing anything with parts — a system design, experiment, spec, plan, document, or API — and especially when adding a component, comparison, model, metric, section, or option. Catches elements added for symmetry, completeness, or elegance rather than because a question requires them. Triggered by: "should I also add", a design that has grown since it was proposed, plans with multiple arms or comparisons, scope review, anything that feels thorough.
- ▌ Writing Review · michaelwjohnsonUse before sending prose that has to persuade, explain, or be acted on — a report, proposal, email, summary, design doc, or manuscript section. Checks whether the argument holds and whether the sentences carry it: an unstated point, sections in an order nobody can follow, generalizations with no evidence under them, abstraction where a concrete noun belongs, and clutter that survived the first draft. Triggered by: finishing a draft, "does this read well", "can you review this writing", sending something to a reader who can stop reading.