moonbit-agent-guide

Structure a MoonBit project by placing a moon.mod.json at the module root and a moon.pkg.json inside each package directory. This standard layout organizes files, tests, and docs consistently across repositories.

The best way to test and check a MoonBit module is using moon commands. Run `moon check` to verify type safety across packages and `moon test` to execute tests, ensuring continuous code quality throughout development.

Generate documentation for a MoonBit package by using the `moon doc` command and consulting README.mbt.md files. This tooling workflow extracts module documentation automatically based on the standardized project layout.

Yes, a MoonBit project requires a moon.mod.json file at the module root to define the project. Individual package directories within the module must also include a moon.pkg.json file for proper package configuration.

Adopting standard MoonBit project layouts solves the problem of inconsistent file organization and tooling adoption. It accelerates new contributor onboarding by providing a clear, shared structure and concrete playbook for development.

Yes, you can use moon commands for continuous integration in MoonBit. Running `moon check` and `moon test` verifies type safety and executes tests across all packages, ensuring continuous quality during development.