MoonBit Task Checklist

• Locate the enclosing moon.mod and relevant moon.pkg files before editing.
• Discover APIs with moon ide doc; use outline, peek-def, find-references, hover, and rename for semantic navigation and refactoring.
• Use .mbtx exclusively for agent-authored automation; keep automation logic out of shell scripts and other scripting languages.
• Keep changes within the correct package. Files do not define namespaces; separate top-level items with ///|.
• Add regression tests for bug fixes. Add black-box tests and docstring examples for new public APIs.
• Validate with moon check and the narrowest relevant moon test; use moon test --update only for intended snapshot changes. Use moon explain --diagnostic to list warnings and --warn-list to enable selected warnings (for example, +unnecessary_annotation).
• Run moon fmt and moon info before handoff. Review generated .mbti changes, especially when the public API should remain stable.

MoonBit Project Layouts