用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/aotter/mantle --skill update命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Start a new Mantle site locally from a deterministic starter bundle, or orient and continue an existing local or Mantle landing project. Use when the user gives a Mantle repository URL and asks to try or build with it, invokes the Mantle install skill, wants a new Mantle site, or opens an existing generated site.
Work on any Mantle project using the Core SDK contract. Use for manifest, runtime, content model, handler, adapter, validation, and MCP work after a project already exists.
Audit and safely remove stale, uncommitted public media uploads from a Mantle Cloudflare R2 bucket. Use when a Mantle operator asks to inspect or clean orphan media objects left after create_media_upload without commit_media_upload.
正在显示 SKILL.md
| name | update |
| description | Check a Mantle project for drift against its Core SDK, starter source, or installed plugin lockfiles. |
| metadata | {"source":"@aotter/mantle","sourcePath":"skills/update/SKILL.md","applies_to":"mantle grammar v0.1","projection":"project, plugin"} |
Use this for drift checks. Do not blindly overwrite user-owned code.
package.json and lockfile for installed @aotter/mantle* versions..mantle/launch-state.json and .mantle/features.json when the project
came from Mantle landing..mantle/plugins.json and .mantle/plugins.lock.json when plugins are
installed.mantle:update, validate, and
typecheck; the installed mantle update command is authoritative.pnpm exec mantle update --ref <immutable-ref>
For the one-time alpha.63 bridge, invoke the exact newer Core package and provide the current bundle location because alpha.63 metadata does not contain it:
pnpm dlx @aotter/mantle@<exact-version> update \
--ref <immutable-ref> \
--bundle-base-url 'https://raw.githubusercontent.com/aotter/mantle-starters/{ref}/provision-bundles'
Do not extract or replace a repo-local updater. The Core command accepts
the alpha.63 no-v source ref, writes only the report, and records the
versioned bundle location for the reviewed metadata migration.
3. Read the generated report before editing.
4. Triage each path; do not treat the report as a patch or merge plan.
5. Port confirmed upstream changes one hunk at a time.
6. Apply only the report's .mantle/launch-state.json and
.mantle/features.json metadata migration, preserving every other field.
7. Re-run:
pnpm validate
pnpm typecheck
Current reports compare three states: the original starter ref, the target ref, and the local project.
upstream to find starter changes worth porting. Use local only to
understand project-owned drift from the original starter..mantle/launch-state.json or
.mantle/features.json; the report omits them and gives a field-level
migration instead. Preserve Worker/D1 names, bindings, origins, provider
values, and all unlisted launch state.upstream proposes mantle-<type> names for a real project, stop: the
bundle is incompatible and must not be ported.local section is normal after customization. Counts are not a
confidence score.Starter bundles and plugin packages can provide source snapshots, but Core owns the workflow vocabulary. Repo-local update guidance may recover an older updater, but it does not override the installed Core runtime/API contract.