0001: Next.js route handlers for the API and MCP
The REST API and MCP server stay as Next.js route handlers in apps/api instead of Hono, oRPC, and a separate apps/mcp.
0003: The apps/saas name and host-based routing
The product app stays apps/saas, and every surface is served from its own subdomain instead of path prefixes.
0001: Next.js route handlers for the API and MCP
The REST API and MCP server stay as Next.js route handlers in apps/api instead of Hono, oRPC, and a separate apps/mcp.
0003: The apps/saas name and host-based routing
The product app stays apps/saas, and every surface is served from its own subdomain instead of path prefixes.
Domain logic stays split into bounded contract, core, and supabase packages instead of domain, contract, and services.
The repo standard groups domain logic into packages/domain, packages/contract, packages/services, and packages/supabase. CentraKit uses a provider-swappable three-layer model per bounded context:
foundation, identity, tenant, crm, catalog, work, commerce, conversations, automation, platform, portal, people) own interfaces, schemas, and domain errors.packages/supabase-* packages own the Supabase implementations.packages/core and packages/core-* own request-scoped service wiring.Integrations with third parties live under packages/integrations/*, which is an extra workspace glob.
Keep the bounded topology and the packages/integrations/* glob. Turbo boundary tags encode the same import rules the architecture rule describes.
@workspace/core-* factories.packages/integrations/* in addition to the standard globs.app, core, provider, contract, ui, config, integration, and test instead of the standard package names.Last updated on
0001: Next.js route handlers for the API and MCP
The REST API and MCP server stay as Next.js route handlers in apps/api instead of Hono, oRPC, and a separate apps/mcp.
0003: The apps/saas name and host-based routing
The product app stays apps/saas, and every surface is served from its own subdomain instead of path prefixes.