Megamono documentation

Megamono helps you organize applications, shared libraries, and repository documentation in one workspace. It works with Nx: Nx understands your projects and runs their tasks, while Megamono provides conventions and generators to keep the repository consistent as it grows.

Start here

#

• Check requirements and compatibility for your workspace and platform plugins.
• Create a workspace if you are starting a new project.
• Adopt an existing workspace if you already use Nx.
• Understand the repository structure to learn what belongs in apps, libraries, packages, and docs.
• Explore the CLI to find the command for your next task.

You can use Megamono locally without a hosted account or subscription. You can also use it without Playstack; integrations are optional.

The public hosted service has not launched. Local creation, adoption, checks, and feedback reports are available now; hosted sign-in, account switching, and feedback submission require a configured service.

Build and extend

#

• Add applications and libraries with consistent configuration.
• Start a packages-only workspace for a toolkit or SDK.
• Create a native Android app with Kotlin and Compose.
• Set up a database project using Prisma or Drizzle.
• Build and consume a Prisma client with explicit application build ordering.
• Work with different platforms, including Rust, Swift, Cloudflare, browser extensions, and PHP.
• Write specifications, plans, and decisions so people and agents can understand your repository.
• Run checks and tasks as you develop.
• Adopt gradually without weakening checks with reviewed warning budgets and explicit health coverage.
• Integrate Playstack when you want shared application capabilities.

A typical workflow

#

Start with a workspace or an adoption survey. Add the applications and shared code you need, then use Nx to run their development, test, and build tasks. Review generated changes in Git just as you would review handwritten code.

Megamono does not deploy your applications or manage production credentials for you. Keep your existing deployment process and application tests.

Find a specific option

#

Use Search documentation to find commands, options, and page headings. Command pages include examples and help; generator and task pages explain their options.

If an installed command behaves differently from the docs, check its local help and use package diagnostics. Contributors testing unpublished changes can follow local package development.