Make a Cross-Platform Desktop Character
Turn one user-owned reference image into a tested local desktop character without publishing the source image. Work inside an existing XiaoU Desktop Character checkout and preserve its code structure.
Start Safely
- Read
AGENTS.md,文件夹说明.md, andagent-guide/AGENT_GUIDE.mdcompletely. - Run
scripts/preflight.py --project <repo>from this skill. - Keep source photos, references, candidates, source sheets, and workflow state under the Git-ignored
user_assets/tree. - Never upload private images to GitHub, Issues, Releases, remote APIs, or public video assets.
- Stop and explain any missing system software instead of installing it without permission.
Register and Analyze the Character
- Register the image with the repository workflow tool so the original remains local.
- Analyze the face shape, eyes, brows, hair, clothing, accessories, body proportions, palette, and overall temperament.
- Ask the user to choose preserved style, light chibi, or full chibi when not already stated.
- Use the available image-generation capability to create exactly one transparent standard candidate. Keep distinctive features; do not reuse a generic face.
- Register the candidate and open the repository confirmation window.
- Pause until the user personally approves the character. Do not generate action sheets before approval.
Build the Action Set
Read references/action-contract.md before generating images.
- Use the approved candidate as the only identity reference.
- Generate transparent 3x2 sheets for expressions, daily actions, props, front-facing poses, and outfits.
- Keep all limbs visible and anatomically coherent. Reject extra heads, hands, fingers, legs, cropped hair, opaque corners, or inconsistent scale.
- Generate a 12-frame walk with alternating feet, planted contacts, body compression, lift, and restrained arm swing. Do not simulate walking by shaking or translating a static body.
- Create the GIF preview and pause for the user's walking approval.
- Continue only after both the character and walk gates are approved.
Integrate and Package
- Run
tools/prepare_custom_pet.pyto normalize frames to the shared 560x500 transparent canvas. - Inspect the generated action contact sheet and walk GIF directly.
- Run the full tests and a real GUI smoke test on the current platform.
- Read references/platform-build.md, then build the requested Windows and/or macOS package.
- Read references/quality-checklist.md and complete every release check.
- Tell the user the exact
.exeor.appto open. Do not hand off only source code or commands.
For commissioned customization, optionally copy examples/interaction-pack-romantic.json to the local user_assets/interaction_pack.json and replace its actions and dialogue with text the customer approved. Keep that pack local unless the customer explicitly authorizes publication.
Preserve the Two Gates
- Gate 1: confirm that the standard character resembles the reference.
- Gate 2: confirm that the walk has real steps and a natural rhythm.
Never mark either gate approved on the user's behalf and never bypass workflow.json checks.