菜单
Set up MoonBit project instructions and agent configuration for coding assistants. Use when bootstrapping agent guidance, validation commands, hooks, project conventions, or shared MoonBit context for Codex, Claude Code, or other agent environments.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | moonbit-agent-setup |
| description | Set up MoonBit project instructions and agent configuration for coding assistants. Use when bootstrapping agent guidance, validation commands, hooks, project conventions, or shared MoonBit context for Codex, Claude Code, or other agent environments. |
Create project-level agent instructions for a MoonBit repository. Keep the core guidance agent-neutral, then apply the adapter for the active agent only when the user wants tool-specific files or hooks.
Scan from the working directory:
find . -name "moon.mod.json" -not -path "./.worktrees/*"
find . \( -name "moon.pkg.json" -o -name "moon.pkg" \) -not -path "./.worktrees/*" -not -path "./.mooncakes/*"
find . \( -name "*_test.mbt" -o -name "*_wbtest.mbt" -o -name "*_benchmark.mbt" \) -not -path "./.mooncakes/*" | head -20
test -f .gitmodules && cat .gitmodules
Record module names, package paths, test locations, docs directories, and submodule presence.
Use one adapter:
| Target | Signals | Output |
|---|---|---|
| Codex | user asks for Codex, AGENTS.md exists, .agents/ exists | AGENTS.md, optional helper scripts |
| Claude Code | user asks for Claude, CLAUDE.md exists, .claude/ exists | CLAUDE.md, optional .claude/settings.json hooks |
| Generic | no clear agent target | docs/development/agent-guide.md or another user-approved Markdown file |
If the user names a target, prefer that target over filesystem signals. If multiple targets are requested, generate each adapter separately and avoid cross-linking product-specific files.
Reference files:
references/codex.md.references/claude-code.md.references/generic-agent.md.Every adapter should include the same project-specific information:
moon.mod.json.docs/ exists.Keep generated instruction files short. Put stable shared MoonBit conventions in the installed base file:
~/.agents/moonbit-base.md~/.claude/moonbit-base.mdUse an import only when the target agent supports that instruction-file syntax. Otherwise, summarize the relevant rules briefly and point to the base file.
If the target file already exists:
If adding JSON config for an adapter:
Run the checks that match the generated adapter:
moon check
If JSON config was written:
python3 -m json.tool <path-to-config-json>
If an instruction file was generated or merged, inspect the first section order:
head -80 <instruction-file>
| Mistake | Fix |
|---|---|
| Treating Claude Code as the default | Select an adapter first |
| Writing product-specific details into the core workflow | Move them to references/<adapter>.md |
| Overwriting an existing instruction file | Merge by headings and preserve user text |
| Listing every doc file | Say how to browse docs and capture only durable rules |
| Embedding generic MoonBit rules in every project | Use the installed base file when supported |
| Hardcoding absolute paths | Use paths relative to the project root |
Error handling conventions for MoonBit projects. Use when designing error types, choosing between abort/fail/raise, writing catch blocks, defining FFI boundaries, or reviewing error handling patterns. Triggers on: error handling, abort, fail, raise, catch, Result, error types, fallible functions, boundary safety, error recovery.
Use when reviewing a MoonBit/Canopy change or pull request before merge and multiple independent review perspectives are useful
Use when writing or reviewing MoonBit code against the `dowdiness/incr` reactive library (v0.14.x+) — building Inputs/Deriveds/ReachableDeriveds, attaching long-lived derived cells with `Watch`/`Observer`, adding microbenchmarks, or wrapping a reactive pipeline in a struct. Catches recurring idiom misses (inside-vs-outside read semantics, GC-anchor `Watch`/`Observer`, `Type::Type` constructor naming, defensive copies).
Use when creating or editing a GitHub PR/issue body, comment, or commit message from a shell, or when writing a grep/rg search pattern — especially if the Markdown or pattern contains backticks, `$()`, `>`, or other shell metacharacters that could be expanded before the tool sees them.
Use when creating, removing, or working across git worktrees or submodules — before force-pushing, before deleting a worktree, after `git worktree add`, when merging or deleting branches with `gh pr merge`/`gh pr close`, when bumping a submodule pointer, when merging a stack of dependent PRs, or when another agent/process may be operating on the same checkout concurrently.
Use when writing MoonBit code involving derive(Debug) on container fields, a trait method whose name matches a callable field, JS-target-only public APIs or JS numeric formatting, `guard` early-exit syntax, package visibility (`pub` vs `pub(all)`) on mutable-container fields, or `moon fmt` touching a comment-only or multi-line closure body — silent-failure compiler/formatter behaviors that `moon check` and `moon fmt` don't flag.