Standardizes Effect libraries from one versioned blueprint. CLI, Nx, and MCP all call the same policy, planner, ts-morph renderer, and executor.
contract: schemas, errors, events, ports, consolidated Effect RPC contracts, and shared typesdata-access: contract-backed services withLive,Test,Auto, and a colocated test harnessfeature: server feature services plus optional contract-derived RPC clients and React query hooksprovider: external integration services withLive,Test, andAutoinfra: infrastructure services withLive,Test, andAuto
Generated libraries use exact package exports, TypeScript project references, import-derived dependency sections, colocated specs, and Vitest's forks pool. Feature libraries default to root and server. Declaring client requires a contract and generates a domain-scoped AtomRpc client plus typed query hooks without re-exporting server implementations. The generator does not emit Context.Tag, Effect.Service, Dev layers, public layers.ts composition, data-access operations/ directories, or micro-barrel trees.
mlg init
mlg generate contract --capabilities entities,errors,events,ports order
mlg generate data-access --contract order order
mlg generate data-access --contract form --modules form-state,marketing/campaign,marketing/subscriber form
mlg generate feature --modules cart,payment --data-access order checkout
mlg generate provider --entrypoints root,server stripe
mlg generate infra queueGenerate from a committed blueprint:
mlg generate blueprint ./blueprints/order.jsonAudit or normalize an existing library:
mlg standardize --check libs/feature/checkout
mlg standardize libs/feature/checkoutmlg init creates mlg.config.json. It does not generate sample libraries or implicit provider/infra packages.
{
"schemaVersion": 1,
"kind": "feature",
"name": "checkout",
"modules": [{ "name": "cart" }, { "name": "payment" }],
"contract": "checkout",
"dataAccess": ["order"],
"entrypoints": ["root", "client", "server"],
"testMode": "unit"
}The same blueprint is accepted by every interface. Planning is deterministic and produces a hash, file set, package manifest, exports, dependencies, and project references before files are written.
Data-access module paths are recursive. marketing/campaign generates
src/lib/marketing/campaign/{service.ts,service.spec.ts,index.ts}; grouping directories do not receive duplicate services.
Contracts use the same paths to describe capabilities, but expose only top-level subdomain boundaries. For example, marketing/campaign and marketing/subscriber are both declared in src/lib/marketing/ports.ts. Providers are a single external SDK boundary and do not accept modules.
Committed blueprint files may express the same hierarchy structurally:
{
"modules": [
{ "name": "form-state" },
{
"name": "marketing",
"modules": [{ "name": "campaign" }, { "name": "subscriber" }]
}
]
}pnpm nx g @samuelho-dev/monorepo-library-generator:contract order \
--capabilities=entities,errors,events,portspnpm test
pnpm typecheck
pnpm buildChangesets on main open a version pull request. After it merges, the Release workflow checks types, lint, tests, and build, then publishes the built tarball to npm with trusted publishing and provenance. It checks the exact published version and SHA-512 integrity against that tarball. Existing versions are skipped; manual npm publish is not supported.
The npm trusted publisher must be configured for samuelho-dev/monorepo-library-generator, workflow release.yml, and no environment. Publishing uses GitHub-hosted runners with Node 24 and npm 11.21.0, without an npm token. The separate Snapshot workflow uses pkg.pr.new, not npm, and retains its existing policy.
Registry verification allows up to 120 checks, ten seconds apart, for npm processing. Publishing is not retried; an integrity mismatch still fails the release.