Wonderschool: a corporate knowledge base and ops system

A consulting engagement with Wonderschool: one shared repository (“product docs”) that works as the company’s knowledge base, operations system, and AI development environment at once. Engineers, product managers, designers, salespeople and the data team interact with the same context about the product and the business, directly through Claude. It’s a working version of the ideas in collaborative specification.

What it is

• Shared context for every role. Architecture, components, design system, product catalog, business context, terminology, people, and initiative plans, organized by trust level (how things work today vs. forward-looking plans vs. cached external data), verified against the real source code, and loaded into every Claude session on your machine. A PM asking about billing gets answers drawn from the billing code, not just docs about it.
• Operational skills. ~40 repeated actions and best practices encoded as slash commands: weekly status updates, meeting prep, ticket management, data questions against the warehouse, PR review, planning docs, design and whiteboard context. The org’s know-how becomes runnable.
• Wired into the company’s tools. Enterprise search, Slack, Linear, Figma, Miro and the source repositories are all connected, so answers and actions go through the systems the company uses.
• A prototyping framework. A /prototype skill generates clickable demo apps in the company’s design system, on top of the business’s real data structures and connected context, published to the internal docs site on push. It fills the role of Lovable or Replit for feature review, with prototypes that look like the product and know the domain. 20+ live prototypes in about six months, built by designers and PMs as much as engineers.
• Training, including voice. Setup takes about 20 minutes for anyone, technical or not. Rollout came with training on driving Claude by voice: talk through the messy version out loud, let the agent structure it into the doc, ticket, or plan.

Adoption

In about six months: roughly 1,500 documents and 2,000+ commits from product managers, designers, engineers, a data team, automated agents, and the CEO. A prior wiki was migrated into it.

This is a system I can build for other companies: see working with me.