菜单
Manage Create-Delight Remake Packwiz assets. Use when adding, updating, removing, syncing, validating, or packaging mods/resourcepacks/shaderpacks, packwiz-files payloads, CurseForge/manual-download metadata, or the Create Delight Core packaged jar.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
连接、诊断、测试、操作、修复、构建和部署 minecraft-mod-mcp（mcpmod）及其 Forge 1.20.1 模组，并通过运行时帮助探索 FTB Library、KubeJS 等模组指令。用于 CDRdev 中的 MCP 端口冲突、Mod not connected、截图/键鼠/命令调用、玩家或世界数据异常、生产环境反射映射失效、测试 JAR 替换与真实游戏回归。
Keep the Create-Delight Remake checkout current and locally runnable after Git updates. Use when the user asks to pull latest changes, switch to main, rebase on main, merge upstream changes, update a branch, or otherwise run Git operations that may bring in packwiz metadata, packwiz-files payloads, or CDC submodule pointer changes.
开发知识路由、知识库整理、实现记录、代码位置索引、设计规划归档、技术 how-to。用于查找或记录 Create-Delight Remake 项目知识，或判断信息应写入 AGENTS、docs/dev-knowledge、docs/plan、docs/lessons-learned 还是项目 skill。
实现后知识检查、知识库维护、项目经验沉淀。用于代码、配置、脚本、文档或流程变更完成后，判断是否需要记录项目知识，并将知识路由到 AGENTS、docs/dev-knowledge、docs/plan、docs/lessons-learned 或项目 skill。
Create-Delight Remake modpack release workflow - version bump, tag, artifacts download, and GitHub release creation
| name | packwiz-assets |
| description | Manage Create-Delight Remake Packwiz assets. Use when adding, updating, removing, syncing, validating, or packaging mods/resourcepacks/shaderpacks, packwiz-files payloads, CurseForge/manual-download metadata, or the Create Delight Core packaged jar. |
Use this workflow for modpack asset operations that touch mods/, resourcepacks/, shaderpacks/, packwiz-files/, pack.toml, index.toml, or the packaged CDC jar.
mods/, resourcepacks/, and shaderpacks/ contain .pw.toml metadata only; do not track runtime jars there.packwiz-files/{mods,resourcepacks,shaderpacks}/ with matching raw-URL metadata.scripts/update-packwiz-meta.ps1 -Category ...; avoid manual metadata edits unless repairing generated output.scripts/update-packwiz-meta.ps1 on short-lived feature/PR branches because it derives packwiz-files raw URLs from the current branch and can rewrite unrelated .pw.toml files to branch URLs that disappear after merge.main and long-lived LTS/release-maintenance branches that must serve their own Packwiz payloads.pack.toml and index.toml are generated from modpack.toml; do not commit them.Clrwl are generated locally and must not be tracked.side = "client" or side = "server" explicitly for client-only or server-only mods.packwiz-files/<category>/ directory../scripts/update-packwiz-meta.ps1 -Category mods|resourcepacks|shaderpacks only on main or a long-lived LTS/release-maintenance branch.-Proxy "http://127.0.0.1:7890"..pw.toml plus packwiz-files changes before staging../scripts/sync-packwiz-assets.ps1 when local runtime files must match metadata.main, remove an asset by deleting its .pw.toml metadata.packwiz-files payloads only when the committed payload is intentionally retired.packwiz-files/mods/Create-Delight-Core-1.20.1-dev.jar.mods/create-delight-core.pw.toml hash for the new jar and keep its raw URL pointing at main; do not run the full metadata update script.main, first set PACKWIZ_FILES_RAW_PREFIX=https://raw.githubusercontent.com/Jasons-impart/Create-Delight-Remake/main/packwiz-files/, then inspect and revert unrelated .pw.toml URL rewrites before committing.CDC-mod-src origin/1.20.1; if it fast-forwards, include the submodule pointer in the same commit so source matches the packaged jar.For pull, rebase, merge, or branch updates, use repo-sync: it installs local .git/hooks shims that call tracked scripts/.githooks, then calls scripts/sync-packwiz-assets.ps1 -IfGitChanged so Packwiz runtime sync logic stays in one script.