MoonBit Orientation

Use this skill to solve MoonBit developer questions by identifying the missing context first. This is an orientation skill, not a bundled copy of all MoonBit documentation.

Default workflow

1. Classify the user's situation and likely missing layer.
2. Check the gotchas below and the freshness gate before choosing a path.
3. Load the smallest relevant reference file.
4. If code, APIs, package config, or diagnostics are involved, inspect local files or run the narrowest discovery command before answering.
5. Give a practical answer: direct capability answer, MoonBit equivalent, exact verification command or link, and narrow validation command when code changed.
6. If the final answer gives an exact API, import, error-code meaning, target rule, or docs claim, include the command or URL that verifies it. Do this even when the answer is short.