break-dogmalisted

Use when an inherited assumption is steering a decision and nobody has checked whether it still holds HERE — "that's how vLLM/SGLang/everyone does it", "you need X to do Y", "this is compute-bound / physics-capped / can't beat Z", "we always do it this way", "best practice is". Triggers on any borrowed runtime/algorithm/protocol adopted by default, any asserted wall or limit, any "must have" that was never measured in our regime, and any "break all dogma / challenge the assumption / why do we even do this" request. The move: name the dogma, mine where it came from and why (competitor issues/PRs/RFCs + searxng + repomix + deepwiki), test whether the constraint is actually load-bearing in OUR regime or cargo-culted from a different one, and if it is not necessary, break it and route to invention. Reach for it by default before adopting any borrowed component or accepting any asserted limit; skip only when the practice is a genuine leaf you are reusing on purpose (KISS).
88plug/break-dogma · ★ 0 · AI & Automation · score 60

Install: claude install-skill 88plug/break-dogma

# Break Dogma A dogma is an assumption adopted because *someone else does it* or *someone asserted it* — never because it was measured true **here, in this regime.** Most inherited "you must / you can't" survives on authority, not evidence. This skill is the discipline that separates a real constraint from a cargo-culted one, so we break the ones blocking the faster/atomic path and keep the ones that are actually load-bearing. **Breaking dogma is not contrarianism.** Some inherited practice is correct, and reinventing a leaf that isn't the moat is its own dogma (build-don't-reuse). The goal is calibrated: challenge every assumption, but let the honest ones survive the test. A dogma broken without a measured reason is just a different dogma. This skill is the **upstream ideation move.** What it surfaces feeds: - `world-first` — a broken dogma is often the incumbent's removed-constraint (the wall to invent past). - `scientific-method` — an asserted limit is a falsifiable hypothesis; the probe kills or confirms it. - `herlihy` — once you break a serialization/lock dogma, atomicize what it forbade. ## The four kinds of dogma Name which one you are looking at — the test differs. 1. **Borrowed-runtime dogma** — "we need the vLLM/SGLang scheduler / their KV layout / their launcher." Adopted to save effort. Test: is the borrowed component the *moat*, or a leaf? If it is the moat, owning it is the point — break it. If it is a leaf, reusing it is fine (don't reinvent