A Turborepo monorepo that shows exactly how to consume and compose CC API Framework packages in a real multi-service product. Shared Zod contracts, a public user API, an internal order service, and testing utilities — all wired together and ready to run.
The CC APIs Monorepo is a reference implementation of CC API Framework in a real product context. It bridges the gap between "framework documentation" and "actual production code" by showing how all the pieces fit together across multiple services sharing common types, contracts, and test helpers.
Shared Zod schemas in @acme/shared-contracts serve as the single source of truth for every request and response shape. Both services consume them, eliminating drift between the public API contract and the internal implementation. A shared JWT factory in @acme/shared-testing keeps test setup consistent and fast across every service.
@acme/shared-contracts — Zod schemas are the single source of truth for all request and response shapes. Both services import from one place, keeping types in sync automatically.
JWT auth, CORS, IP-based rate limiting, OpenAPI 3.1 docs at /docs, and proxied order lookups from the order service — all wired up and ready on port 3001.
Service-token auth only — no public JWT, no CORS. Handles order CRUD with status transitions. Exposed on port 3002, reachable only from the user API tier.
@acme/shared-testing provides a JWT factory and static fixtures so every service test file can generate valid tokens in one line, with no boilerplate.
Build, typecheck, test, and clean tasks run in dependency order with Turborepo caching. Run everything from the root or target a single service with --filter.
pnpm front-end-services and pnpm core-services start individual tiers independently. pnpm dev starts everything in watch mode simultaneously.
cc-apis-demo-monorepo/
├── packages/
│ ├── shared-contracts/ # Zod schemas + TypeScript types
│ ├── shared-testing/ # JWT factory, fixtures
│ ├── cc-api-framework-errors/
│ ├── cc-api-framework-logger/
│ ├── cc-api-framework-networking/
│ └── cc-api-framework-fastify-plugins/
└── services/
├── front-end-services/
│ └── user-api/ # Public API — port 3001, JWT auth
└── core-services/
└── order-service/ # Internal API — port 3002, service-token
Browser / External Client
│ JWT Bearer token
▼
user-api :3001 ← front-end-services tier
(JWT auth, CORS, rate-limit, OpenAPI docs)
│ Service token
▼
order-service :3002 ← core-services tier
(internal only — no public exposure)
This monorepo was designed, directed, and shipped using Vibe Coding — organized thinking and 32 years of experience translated into production software by AI.
Learn About Our Process