Turning recurring monorepo and deployment decisions into an explicit contract for developers, CI, and coding agents.
- Context
- Teams and coding agents repeatedly spend time rediscovering repository layout, workspace boundaries, validation, containers, and deployment conventions.
- What I owned
- I created and lead the product architecture, JavaScript implementation, create-monox CLI, delivery model, CI and release controls, and project governance.
- Key decisions
- The create-monox CLI generates maintained JavaScript, TypeScript, Python, PHP, and Go workspace recipes, plus local services, CI, containers, and a deterministic project lock. Each deployable package owns its deployment contract. Local Docker has a built-in executor; PM2, Coolify, and Kubernetes paths stay guarded behind explicitly injected transports.
- Outcome
- A public MIT repository at Mosharush/MonoX with 24 tested workspace recipes, green CI and CodeQL, explicit dependency and deployment contracts, and fail-closed delivery validation. create-monox 0.2.0 is published as npm's latest version through trusted publishing with provenance.