← ClaudeAtlas

pixelkilnlisted

Use PixelKiln to plan, generate, review, recover, audit, pack, and export manifest-driven pixel-art projects. Apply when a task uses the PixelKiln CLI, manifest, lockfile, or generated asset workflow; do not use for unrelated one-off image generation.
gfargo/skills · ★ 2 · Data & Documents · score 75
Install: claude install-skill gfargo/skills
# PixelKiln Treat generated pixel art as build output. Read the manifest, report the cost before submission, stop for human review, and record the source and output hashes. ## Working rules - Locate `pixelkiln.manifest.json` first. Paths are manifest-relative. - Treat `style.extends` as a source-level variant, not a reason to copy the parent. Keep every child `outDir` explicit, inspect the resolved plan, and remember that a pixel-affecting parent edit intentionally makes children stale. - Never inspect, print, or commit provider credentials. Read the top-level provider default and every style override, then load the matching provider references below. - Run `pixelkiln doctor --dry-run` and `pixelkiln plan` before paid work. Report actionable, recoverable, and estimated cost figures with their provider unit. - Do not regenerate recoverable work. Follow the exact zero-cost action printed by `plan`: `poll`, `pick`, `fetch`, or `restore`. - Submit paid work only when the user has authorized generation. Always pass an explicit `--budget` no higher than the authorized estimate. For mixed work, pass one `--budget provider=amount` ceiling for every paid provider in the plan. - Leave visual selection to the local `pixelkiln pick` review page unless the user explicitly provides a selection rule. Closing it applies nothing. - When a selected style declares `quality`, run manifest-mode `pixelkiln refine` after its source is accepted and downloaded. Read the quality