菜单
Create a new Wally package under lib/ in this repo. Use when asked to scaffold, add, or create a new package/module/library. Covers the scaffold script, the pure-Luau vs datamodel entry-point decision, and post-scaffold registration steps.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Work on the coverage system itself under tools/coverage (Rust full_moon engine or Lune orchestrator). Use when modifying instrumentation, probes, mutation testing, the report, adapters, or when golden tests fail. Covers building, testing, golden regeneration, and layout boundaries.
Publish or version-bump a Wally package in this repo. Use when asked to publish, release, or bump a package version. Covers the publish script's non-interactive flags, the auto-generated init.luau, and CI workflow actions.
Run tests and coverage for a package in this repo. Use when asked to run tests, check coverage, run the test suite, or verify a package's specs pass. Covers command forms, flags, pipeline selection (Lune vs Roblox Studio), and reading the output.
Write or edit documentation in this repo — moonwave API docs, doc comments, or guide pages. Use when asked to document an API, add a guide, fix docs, or preview the docs site. Covers moonwave comment forms, guide-file conventions, classOrder registration, and previewing.
Write or modify tiniest test specs (.spec.luau) in this repo. Use when adding tests, fixing failing tests, or improving coverage for a package. Covers spec structure, the expect matcher API, snapshots, Roblox class shims, and the FakeIntermediary bridge for replicator tests.
| name | new-package |
| description | Create a new Wally package under lib/ in this repo. Use when asked to scaffold, add, or create a new package/module/library. Covers the scaffold script, the pure-Luau vs datamodel entry-point decision, and post-scaffold registration steps. |
npm run newpackage runs scripts/new_package.py, which is interactive
(prompts for folder name, display name, description). When running
non-interactively, scaffold by hand instead, matching what the script creates:
lib/<name>/
wally.toml # name = "raild3x/<name>", version 0.1.0, [custom] formattedName + docsLink
src/init.luau # module table with a --[=[ @class <FormattedName> ]=] doc block
src/init.spec.luau # tiniest suite: return function(t: tiniest) ... end
Copy the exact templates from scripts/new_package.py (create_wally_toml,
create_init_luau, create_init_spec_luau). Then run
npm run setup <name> semantics via: python scripts/setup_package_for_testing.py <name>
(wally install + sourcemap + package types).
src/init.luau as
the entry point — delete it and name the entry module after the package
(e.g. TableManager.luau). This keeps the package testable under the fast
Lune pipeline. npm run publish auto-generates a passthrough init.luau
(re-exporting all export types) at publish time — never commit one.game, Instance, RunService, etc.): a real
src/init.luau is fine; tests will run via Roblox Studio.init.luau either way.[[classOrder]] section (or items) in moonwave.toml if the
package should appear in the docs sidebar.README.md lists packages from every wally.toml — regenerate with
npm run readme, don't hand-edit.lune run coverage.luau package=<name> runs the scaffolded spec.