← ClaudeAtlas

artgen-scaffoldlisted

Docs-only guidance for turning a bounded 2D asset request into a reusable brief, provider-neutral generation prompt, versioned output plan, manual checks, and copy-ready handoff. Use for sprites, animation frames, tiles, icons, UI elements, and simple props; do not use it to claim that image generation or asset processing has occurred.
bohewu/agents_pipeline · ★ 1 · AI & Automation · score 77
Install: claude install-skill bohewu/agents_pipeline
# Artgen Scaffold Create a reviewable asset brief and prompt package for one bounded 2D asset or asset family. Pixel art is the canonical example, but the contract works for adjacent 2D styles when style and dimensions are explicit. If the request says `sprite` without mentioning animation, frames, a loop, a cycle, or a sequence, treat it as one static sprite. ## Boundary This skill produces documentation only. It does not generate images, call a provider, run post-processing, pack atlases, or promise emitted files. A later, separately requested generation task may place assets in the consuming project or another user-selected location. Return: - a request record - an asset brief - one reusable prompt - a suggested output plan - manual checks - an external handoff package - a final direct-use prompt Keep the handoff provider-neutral, human-readable, copy-ready, and non-operative. Do not add wrapper commands, job metadata, queues, retries, or provider-specific promises. ## Resolve Only Material Gaps Infer conservative details when doing so is low risk and label every inferred value `Assumption: ...`. Ask only when a missing choice would materially change the asset family, dimensions, viewpoint, or style. Always make these explicit: - asset type and subject - style - size plan - viewpoint or screen role - palette direction - background rule - variant, state, tile-role, or frame requirements Use the appropriate size form: - static sprite or prop: canvas dimensions -