moonbit-agent-guide

MoonBit project organization standardizes module and package layouts using moon.mod.json and moon.pkg configurations. This keeps multi-package codebases tidy and ensures agents navigate module boundaries consistently across the project.

A canonical MoonBit agent workflow runs steps sequentially: clarify goals, locate module boundaries, discover APIs with moon ide, refactor with moon rename, then validate using moon check and moon test for reproducible code changes.

MoonBit tooling validation relies on moon check, moon build, moon test, and moon info commands. These tools execute rapid validation, build artifacts, run tests, and generate documentation for standard project workflows.

Yes, MoonBit workflows require Moon CLI installed and standard validation steps to execute. The environment setup provides build, check, run, test, and doc tooling capabilities necessary for agent-driven project automation.

Yes, MoonBit tooling includes moon ide guidance for discovering APIs within module boundaries. Agents leverage this to navigate multi-package projects and apply consistent practices across interconnected modules during refactoring.

MoonBit package configurations via moon.pkg files define module boundaries and dependencies. Standardizing these configurations prevents layout issues and maintains tidy codebases when agents edit or restructure multiple packages.