Cycles
Design · c12

Projects as Modular Units

archivedcreated 2026-09-11· last activity 2026-09-11

Why

The Qpoint ecosystem has 8+ specialized projects, each with deep domain knowledge encoded in CLAUDE.md files, agents, and skills. But there's no formal way for one project to discover and use another's specialty. Cross-project collaboration requires manual knowledge of what exists where. This makes it harder to compose workflows like "build a wireframe that uses real customer pain points."

Objective

Formalize cross-project collaboration by documenting each project's API surface — what it offers, when to use it, and where to find the data — so Claude can naturally delegate between domains.

Scope

  • Add ## Sister Projects section to 4 core CLAUDE.md files (design, market-analyst, bob-wire, q-nuxt-layer)
  • Each section lists only the neighbors that project would actually call
  • Consistent format: When to use, Key data (file paths), Agents/Skills available
  • Documentation as API — no new infrastructure, MCP servers, or parent config files

Key Changes

  • design/CLAUDE.md — added Sister Projects: market-analyst, bob-wire, q-nuxt-layer
  • market-analyst/CLAUDE.md — added Sister Projects: design, bob-wire
  • bob-wire/CLAUDE.md — added Sister Projects: market-analyst, design, q-nuxt-layer
  • q-nuxt-layer/CLAUDE.md — added Sister Projects: design, bob-wire

Outcome

Claude Code sessions in any of the 4 core projects can now discover and use sister project data without manual guidance. The example use case — "build a wireframe with ICP quotes" from bob-wire — works by reading market-analyst's all-calls.json directly, guided by the Sister Projects documentation.

Design Decisions

  • Documentation as API, not MCP. MCP servers are justified for external agent access (like the existing qpoint-brand server). For internal Claude Code cross-project work, file reads via additionalDirectories are simpler and sufficient.
  • No parent CLAUDE.md. Each project stays self-contained. Projects only reference the neighbors they actually need, not the entire ecosystem.
  • Peer-to-peer, not hub-and-spoke. Every project declares its own capabilities and knows about its own neighbors. No central orchestrator.

Artifacts

  • initial-prompt.md
  • initial-prompt.md

Qpoint Brand Style Guide