Agent Skills › MMFoundation/WallpaperMachine › wallpaper-issue

wallpaper-issue

GitHub

用于排查和修复壁纸渲染差异问题。通过下载壁纸、捕获参考帧、定位解析代码、编写测试并修复机制，最终验证对比结果，确保渲染效果与 Wallpaper Engine 一致。

.agents/skills/wallpaper-issue/SKILL.md MMFoundation/WallpaperMachine

Trigger Scenarios

收到关于壁纸颜色、图层或特效显示异常的 GitHub Issue 需要复现并解决第三方壁纸在应用中的渲染偏差

Install

npx skills add MMFoundation/WallpaperMachine --skill wallpaper-issue -g -y

More Options

Non-standard path

npx skills add https://github.com/MMFoundation/WallpaperMachine/tree/main/.agents/skills/wallpaper-issue -g -y

Use without installing

npx skills use MMFoundation/WallpaperMachine@wallpaper-issue

指定 Agent (Claude Code)

npx skills add MMFoundation/WallpaperMachine --skill wallpaper-issue -a claude-code -g -y

安装 repo 全部 skill

npx skills add MMFoundation/WallpaperMachine --all -g -y

预览 repo 内 skill

npx skills add MMFoundation/WallpaperMachine --list

SKILL.md

Frontmatter

{
    "name": "wallpaper-issue",
    "description": "Triage and fix a WallpaperMachine report that a wallpaper looks or behaves differently from Wallpaper Engine (wrong colours, missing or misplaced layers, effects, particles, text, timing), usually a GitHub issue with a Workshop id. Downloads the wallpaper with the app's saved Steam sign-in, captures Wallpaper Engine's own frames in the Parallels Windows VM, decides whether the report is a real rendering bug or a misleading preview, then fixes the general mechanism with a test first and a before\/after comparison."
}

Wallpaper issue: triage, fix, verify

The guide is docs/testing/wallpaper-fixes.md; read it first and follow its order. The rules in AGENTS.md outrank this skill. This skill grants nothing beyond them; the standing permissions it relies on are written there.

Without asking the user, a wallpaper fix may:

download the reported item: python3 scripts/we_reference.py fetch <id> --into artifacts/issue-<n> (the app's saved Steam sign-in, never a new one; if it reports the sign-in is no longer accepted, stop and ask the user to sign in again in the app);
wake the Parallels Windows VM (open -a "Parallels Desktop"), capture Wallpaper Engine's frames with capture (muted, started by the VM's background poller), and suspend the VM again through the Parallels menu (how).

Steps, each detailed in the guide:

Triage: get the wallpaper and Wallpaper Engine's frames (reuse shared shots), copy metal_scene_draw_smoke to artifacts/issue-<n>/smoke-before before any renderer edit, render before, compare. Ours matching Wallpaper Engine means it is not a renderer bug: report that with the numbers and stop.
Localize: we_reference.py unpack, read scene.json, find the parser code for the keys involved. When Wallpaper Engine's rule is unclear, capture a generated probe scene and read the pixels instead of guessing.
Fix the general mechanism with a failing test first; no per-frame cost; a ThirdParty/ change updates ThirdParty/provenance.json and the owning docs.
Verify: render after, compare before,after, run the gates once, suspend the VM.
Deliver: commit with Fixes #<n> in the body (push only when asked), Release build only per AGENTS.md or local opt-in, delete this task's artifacts/ output, keep the Workshop items' shared shots.