sprite-spec

Solid

Iris's sprite design specification skill. Produces a complete pixel-art sprite spec — palette, proportions, silhouette, accessories, animation states, frame counts, and AI image-gen prompts. Returns honesty ledger.

AI & Automation 11 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Sprite Spec You are Iris producing a complete sprite design specification. You design; Lyra implements. ## What this skill does Author a pixel-art sprite specification precise enough that an implementation agent (Lyra) or a human artist can execute it without design questions. Every decision gets one line of rationale. ## Protocol ### Step 1: Confirm the character From the user's prompt, extract: - Character name and role - Intended platform / sprite size (16x16, 32x32, LPC 64x64, etc.) - Visual archetype or reference (warrior, scholar, mage, etc.) - Any mandatory design constraints (palette limit, style reference, layer compatibility) ### Step 2: Design the spec Produce a complete specification with these sections: ```yaml ## Sprite Spec: <character name> ### Identity - Name: - Role: - Archetype: - Platform: <LPC / custom / size> ### Palette # 3-7 colors maximum for pixel art. Include hex values. - Primary: #XXXXXX (<color name> — <rationale>) - Secondary: #XXXXXX - Accent: #XXXXXX - Shadow: #XXXXXX - Highlight: #XXXXXX ### Proportions & Silhouette - Head: <description> - Torso: <description> - Silhouette distinguisher: <the one thing that makes this character recognizable at 16px> ### Layers (for LPC-compatible sprites) - Body: <skin tone / variant> - Hair: <style, color> - Torso: <garment, color> - Legs: <garment, color> - Feet: <footwear> - Accessory: <hat, belt, weapon, etc.> ### Animation States | State | Frames | Notes | |-------|--------|--...

Details

Author
wrg32786
Repository
wrg32786/aigent-os
Created
1 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

artgen-scaffold

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.

1 Updated 3 days ago
bohewu
AI & Automation Solid

pixel-art-studio

Create production-quality pixel art and animations programmatically. Use when the user asks to "create pixel art", "draw a sprite", "make pixel animation", "generate sprite sheet", "convert image to pixel art", "pixelate this image", "make a pixel character", "пиксель арт", "пиксельная графика", "спрайт", "像素画", "像素艺术", "도트 그래픽", "픽셀 아트", "8-bit/16-bit/hi-bit style", "retro game art", "Aseprite-like output", "indie game sprite". Covers single-frame sprites, frame-by-frame animations, walk cycles, idle/attack/death animations, sprite sheets, GIF/APNG export, image-to-pixel-art preprocessing (downsample + quantize + dither), 30+ bundled palettes (NES, GameBoy, PICO-8, Endesga 32/64, DawnBringer 16/32, Sweetie 16, Resurrect 64, Korean 오방색/단청, Chinese 故宫/青花/五行, Russian Stoneshard-inspired), 5 dithering algorithms (Bayer 2/4/8, Floyd-Steinberg, Atkinson, Ordered, Blue Noise), automated quality scoring (orphan pixels, doublies, banding, pillow-shading, AI-slop detection), and Generator-Evaluator review via the pixe

138 Updated yesterday
AnastasiyaW
AI & Automation Listed

specify

Interview the user to produce a complete, agent-ready specification, then emit what is needed to build it: for a coded feature/agent a phase-scoped build prompt, or for a skill / declarative agent the artifact itself (SKILL.md / AGENT.md). Surfaces every assumption for review, slices the work into a phased plan, and runs a build-readiness (model/effort) check. Use when the user wants to design, specify, plan, or scope a new agent, feature, or skill; turn a vague idea, PRD, or plan into a rigorous spec; write requirements in EARS / SHALL with testable acceptance criteria; produce a build prompt for a coding agent; or amend, advance, review, audit or sweep an existing spec under specs/ for drift and staleness. Reasoning-driven, one question at a time.

2 Updated yesterday
hmbseaotter