Skip to content
/

Museum

The Naming Collision Museum

Six exhibits showing how the same name conceals wildly different things. The confusion is real: when the corpus has ten things called "Conductor", eight things called "oh-my-something", and two things called "Blueprint" with zero shared lineage — readers understandably give up trying to understand the field. These exhibits name the collisions explicitly.

The Conductor Wing ×10

Ten different things, one name.

A CC documentation plugin, a deterministic YAML workflow engine, a decentralized GitHub-Issues swarm, a consulting marketplace plugin, a macOS desktop app, and more — each called 'Conductor' with no awareness of the others.

View exhibit →
The oh-my-* Hall ×8

Eight repos, two completely different purposes.

Half are orchestration frameworks routing parallel agents across multiple tools. The other half are terminal status-line customizers (like oh-my-zsh). Same naming convention, opposite engineering subjects.

View exhibit →
The Ralph Twins ×5

Same pattern, opposite engineering philosophies.

ralph-snarktank (19.6k★): 200 lines of bash, widely copied. ralph-claude-code (9.2k★): 566 tests, multi-module production system. Both implement the Geoffrey Huntley XML completion contract. Neither references the other.

View exhibit →
The Blueprint Pair ×2

Two unrelated projects, one name.

blueprint-imbue is a planning copilot with a review loop. blueprint-juliusbrussee (cavekit) achieves ~75% token reduction via caveman notation and 6-step backpropagation. No shared lineage.

View exhibit →
The *-starter Corridor ×6

Six boilerplates, architecturally incompatible.

alexeykrol, cloudnative, zbruhnke, wyndomb, codex-starter-acthouse, codex-second-brain — each named 'something-starter', each setting up a completely different Claude Code methodology.

View exhibit →
The Playbook Triple ×3

Three independent works of the same title.

claude-code-playbook-toy-crane, -riya, and -avinash. Independent authors, each publishing their own methodology document under the same generic title. No coordination, no cross-references.

View exhibit →

All frameworks and tools in these exhibits have their own detail pages at /frameworks/[slug]. The museum's purpose is to make the naming collision visible, not to diminish any individual project.