Keep the whole
system in view.
Megamono gives growing repositories a shared structure for applications, documentation, boundaries, automation, and the people and agents changing them.
01 / PRINCIPLES
Coherent by convention. Flexible by design.
Structure should explain itself. Projects, tags, docs, and boundaries form one legible system for people, agents, and automation.
Adopt without starting over. Survey the repository you already have, resolve only real ambiguity, and preserve repository-owned decisions.
Generate the repeatable parts. Scaffolds encode the conventions that should remain consistent while leaving product code in your hands.
02 / CAPABILITIES
The repository is a product, too.
Workspace adoption
Application scaffolds
Nx project inference
Repository governance
Documentation lifecycle
Boundary linting
Affected CI
Workspace health
03 / HOW TO USE MEGAMONO
Start with the repo you have.
Survey first. Make ambiguity visible. Apply a reviewed plan. Then use the same primitives to keep growing.
New workspace
npx create-megamono my-workspace --package-manager=npmStart with applications, shared code, and conventions that fit together.
Workspace setup →Existing Nx workspace
npm install -g @megamono/cliBring the repository you already have into a structure you can grow.
Adoption walkthrough →Every Megamono package is MIT licensed and works without a subscription.
01
Survey
megamono init --surveySee projects, platforms, toolchains, documentation, and conflicts before Megamono writes a file.
02
Adopt
megamono initSelect the governance modules that fit the repository and keep existing ownership explicit.
03
Grow
megamono add app webAdd applications and infrastructure through the same conventions available to new workspaces.
04
Verify
npm exec -- nx run megamono:checkCheck the graph, tags, managed artifacts, package alignment, and durable repository rules together.
04 / GUIDES & DOCUMENTATION
Learn the system by changing it.
Start with a practical guide, then explore the full documentation for CLI commands, generators, actions, and platform plugins.
01
EXISTING REPOSITORIES
Adopt an existing workspace
Survey first, resolve only real ambiguity, and bring Megamono into a repository without erasing its history.
↗
02
APPLICATION STRUCTURE
Add applications without adding drift
Add applications with consistent ports, project tags, tests, and workspace configuration.
↗
03
REPOSITORY GOVERNANCE
Give people and agents the same map
Treat documentation, durable decisions, and structural checks as part of the workspace rather than an afterthought.
↗
05 / MORE OF YOUR STACK
One graph. More of your stack.
Browser extensions
Grow extensions alongside the applications and shared code they use.
Laravel & NativePHP
Organize Laravel services and NativePHP desktop or mobile apps in one workspace.
06 / COMMUNE DEVELOPMENT TOOLS
Clear layers. Better handoffs.
Megamono
REPOSITORY
Creates and governs the workspace structure everything else builds on.
Explore Megamono ↓Playstack
PRODUCT
Adds composable product capabilities inside the applications Megamono places.
Explore Playstack ↗Springbar
RUNTIME
Runs local applications and services as one inspectable development environment.
Explore Springbar ↗