What problem does it solve? Adding a new REST endpoint in this polyglot DDD codebase requires following strict, language-specific conventions — schema validation, middleware composition, DI registration, and OpenAPI metadata — and getting any of them wrong produces silent failures like unregistered routes or missing SDK types. ## Core Features & Use Cases - Language dispatch hub: Routes to the TypeScript or Go playbook based on file extension, so the correct idioms (Zod schemas vs. types.Controller structs) are always applied. - TypeScript controllers: Generates @injectable() Controller classes with InputSchema/OutputSchema, .example() annotations, ctx.session auth injection, middleware overrides, and MCP tool exposure via static mcpScopes. - Go controllers: Scaffolds structs implementing types.Controller with Metadata() + Handle(), auto-registered through fx group:"controllers", using httputil.DecodeRequest and validator/v10 tags. - Pattern registries: Ships registry.yaml files per language encoding mandatory patterns (CTRL-01…CTRL-GO-11) and detectable bad practices for automated review. - Use Case: Ask to add POST /channels/whatsapp and receive a complete controller — request struct or Zod schema, use case wiring, middleware declaration, and module registration — that passes the project's review checks. ## Quick Start Ask the agent to create a new HTTP endpoint such as "add a GET /products/:id controller to the product context" and it will scaffold the controller following the matching language playbook.