hyfdev

Verified MoonBit language reference pinned to an exact moonc version. Use when understanding, writing, reviewing, or fixing .mbt and .mbt.md code; resolving syntax, type, pattern, visibility, trait, or error diagnostics; designing APIs; checking whether a feature exists; or translating Rust, TypeScript, or Go habits. Covers functions and labelled/optional/autofill arguments, structs, enums and extenum, bitstring/JSON/regex patterns, traits and explicit extend/pub extend, generics, visibility, checked errors, async, tests, and FFI declarations. Language semantics only - use moonbit-toolchain for commands, configuration, dependencies, targets, or project setup; load both when code and project operation are involved.

Maintain hyfdev/moonbit-agent-skills across MoonBit releases, official documentation drift, and product-scope gaps. Use whenever a user supplies MoonBit release notes, asks whether a release or the general language reference is covered, requests a re-pin or upgrade, mentions newly added/deprecated/removed behavior, or asks to repair an omitted capability. Generate the relevant upstream inventory before editing, attach executable evidence, make every actionable item discoverable from a product SKILL.md, update discriminating evals, and run the complete gates. Do not use for ordinary MoonBit application coding.

Verified operation of the MoonBit toolchain, pinned to exact moon and moonrun versions - creating modules and packages, moon.mod and moon.pkg configuration (plus legacy moon.mod.json / moon.pkg.json), dependencies and mooncakes packages, moon check, build, run, test, fmt, info, doc, coverage, bench, test filtering and snapshot updates, targets (wasm, wasm-gc, js, native), conditional builds, linking, native stubs, workspaces, publishing, and moon ide API queries. Use when running or explaining moon or moonrun commands, editing moon.mod, moon.pkg, or moon.work files, scaffolding MoonBit modules or packages, adding dependencies, configuring targets or CI, or debugging MoonBit build, test, or dependency-resolution failures. Project operation only - for MoonBit syntax and language semantics use moonbit-language; load both for tasks that change code and configuration together.

Set up Project Context Records (PCR) in the current project — safely install or update the marked PCR block in the project's AGENTS.md, create the records folder, and offer to seed the suggested topic records, idempotently; on update, reconciles legacy record names (offers a goal.md → intent.md rename). Also opens an area decision ledger when a project already carrying the PCR block declares one. Use when the user runs /pcr-setup, asks to set up, adopt, install, add, update, or re-sync PCR / Project Context Records in a project, or — in an already-adopted project — declares that an area should record decisions. Do NOT use for writing or editing individual records (the ledger scaffold is the one exception), never adopt PCR implicitly, and do not use it for changing the methodology doc itself.

Reviewer-side review of rolldown/rolldown pull requests and PR stacks that ends in an evidence-backed Approve or Request changes decision. Use whenever the user asks to review, adversarially review, re-review, approve, request changes on, or decide whether to merge a Rolldown PR or stack. Do not use for implementing fixes or for addressing review comments received on the user's own PR.