Naming clusters
When names collide
Six museum exhibits for the worst naming collisions — where different frameworks independently chose the same name. Plus three additional prefix clusters where the collision is subtler: same prefix, different purposes.
Museum exhibits
Identical names · unrelated projects · full exhibit pages
Ten independent frameworks sharing the Conductor name — CDD plugins, YAML workflow engine, GitHub swarm orchestrator, macOS desktop app.
View exhibit →Eight repos — split between multi-agent orchestration frameworks and terminal status-line customizers.
View exhibit →Five implementations of the Geoffrey Huntley XML completion contract pattern.
View exhibit →Two unrelated projects: a planning copilot and a ~75% token-reduction framework.
View exhibit →Six architecturally incompatible boilerplate starters.
View exhibit →Three independent methodology documents under the same generic title.
View exhibit →Prefix clusters
Same prefix · different layers · no exhibit pages
37 repos prefixed with "claude-" — spans frameworks, tools, methodology docs, dashboards, and CLIs. The prefix is used for everything from the official claude-conductor framework to claude-mem (memory tool) to claude-overlay (standalone CLI).
17 repos starting with "spec-" — mostly spec-driven development frameworks but also the Kiro-derived spec-driven-kiro-project (IDE experiment) and spec-gen (OpenLore epistemic decay model).
13 repos containing "memory" — spanning everything from the ccmemory seed framework to claude-supermemory (memory tool) to cccmemory-mcp (MCP bridge). Different levels of the stack using the same vocabulary.