← ClaudeAtlas

sweep-design-spacelisted

Find a real MECHANISM for a problem — sweep the design space across type systems, formal verification, functional programming, capabilities, specification-by-example, data integrity, authoring UX, other professions (aviation/law/audit), and historical ancestors in SE — instead of circling the same two or three obvious options. Use when the deliverable needs a solution rather than a measurement, when the last few proposals all rhymed with each other, or when the user says "your options are stale / you're thinking narrowly / think fresh". Encodes the hard filters that kill most candidates (does it re-require the thing already measured as unworkable? is it occupied? who writes the formalization? does it demand a new format? unrepresentable or merely detectable?) and the ladder pattern for when one mechanism can't cover the range. Distinct from research-ideate (validates ONE idea you already have), map-prior-work (finds competitors for a claim), and analyze-sibling-paper (deep-reads one rival) — this one GENERATE
zernie/paperlint · ★ 7 · Web & Frontend · score 74
Install: claude install-skill zernie/paperlint
<!-- vigiles:sha256:1822c8c01e352f42 compiled from skills/sweep-design-space/SKILL.md.spec.ts --> # sweep-design-space — stop circling, sweep ## Run me 🔴 FIRST, before any other step: ``` node .claude/skills/paper-pipeline/scripts/announce.mjs sweep-design-space <dir> ``` An advisory pass cannot be observed failing — silence is both its error state and its normal state — so starting is an event, and events get written down. The `<dir>` argument is **optional in spirit**: this skill can run before a paper directory exists, so pass whichever directory the work lives in, or `.`. The ledger row is written either way, and a plain dot is more honest than an invented path. A model asked for "a solution" returns the three designs nearest its training prior, then variations of those, then variations of the variations. The user experiences this as *"you are thinking very narrowly"* — and they are right. The fix is not to think harder in place; it is to **sweep named source domains on purpose** and filter hard. Grounding lesson (2026-07-29, `the reference paper`): four consecutive proposals were reformulations of one idea ("check the prose"), and two of them turned out to be **already shipped in production** by other people. The design space was never actually swept; it was sampled from memory. ## When it fires - The task needs a **mechanism**, not a measurement, and the mechanism isn't obvious. - Your last two or three proposals rhyme with each other. - The user pushes back