Loading...
Loading...
Found 10 Skills
Creating memorable, readable, and emotionally resonant game characters that work at every scale and in every contextUse when "character design, design a character, character art, character concept, character sheet, turnaround, expression sheet, character silhouette, shape language, character proportions, iconic character, memorable character, character lineup, character family, hero design, villain design, npc design, protagonist design, character, art-direction, visual-design, game-art, concept-art, silhouette, shape-language, color-theory, costume, expression, turnaround, iconic, readable" mentioned.
Expert texture artist specializing in PBR workflows, Substance suite, Quixel Mixer, and hand-painted techniques for games and film productionUse when "texture artist, PBR textures, Substance Painter, Substance Designer, Quixel Mixer, normal map, roughness map, metallic map, albedo texture, base color map, texture baking, bake normal, texel density, trim sheet, texture atlas, channel packing, material layering, wear and tear, edge wear, hand painted texture, stylized texture, UDIM workflow, height map vs normal, color ID map, material ID, texture seams, tiling texture, seamless texture, texture, pbr, substance-painter, substance-designer, quixel, megascans, normal-map, roughness, metallic, albedo, uv-mapping, baking, trim-sheet, material, hand-painted, stylized, photorealistic, game-art, 3d-art" mentioned.
Specialist in pixel art creation, sprite animation, and limited palette designUse when "pixel art, sprites, sprite sheet, sprite animation, retro game art, 8-bit, 16-bit, character sprites, tile art, pixel animation, aseprite, pixel-art, sprites, animation, game-art, retro, indie-games, 2d-graphics, sprite-sheets" mentioned.
Expert vehicle designer combining industrial design rigor with entertainment artistry. This skill embodies the methodologies of Scott Robertson's "How to Draw" precision, Syd Mead's future industrial aesthetic, and the functional-aesthetic balance demanded by AAA racing games like Gran Turismo, Forza, and sci-fi franchises like Halo and Star Wars. Every vehicle tells a story through its form. A racing car must look fast standing still. A military vehicle must communicate power and protection. A spacecraft must suggest propulsion physics even when none exist. This skill bridges the gap between "cool looking" and "believably functional" - the difference between concept art that ships and concept art that gets rebuilt from scratch. Use when "vehicle design, car design, spaceship design, aircraft design, tank design, mech design, motorcycle design, racing car, futuristic vehicle, sci-fi vehicle, military vehicle, hover vehicle, flying car, starship, fighter jet, boat design, submarine design, cockpit design, vehicle interior, vehicle customization, damage states, vehicle livery, form language, vehicle proportion, wheel design, hard surface vehicle, vehicle modeling reference, vehicle turnaround, vehicle, automotive, industrial-design, concept-art, hard-surface, sci-fi, racing, military, spacecraft, mech, transportation, game-art, form-language" mentioned.
Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot. Covers the full art pipeline from concept art and style guides to final sprites, sprite sheets, and import configuration. This skill should be used when creating game art, generating sprites, making tilesets, creating UI elements, or preparing assets for Godot import. Keywords: game assets, AI art, DALL-E, Replicate, fal.ai, sprite sheet, tileset, Godot, pixel art, character sprite, game art, texture, animation frames.
Upload local image files into SpriteCook through MCP without API keys or base64 logs. Use when the user provides a local file path that should become a SpriteCook asset for generation references, style guides, tilesets, animation, background removal, presets, or asset organization.
Use SpriteCook saved presets through MCP. Use when the user explicitly asks to use a preset, refers to one of their saved SpriteCook presets, asks for the same style/settings as a saved preset, or asks to save a private preset for future consistent asset generation.
Stylized art direction for Blender with shape language, exaggeration, color harmony, NPR rendering, and hand-painted asset workflows. Use for non-photorealistic game and animation projects.
Builds playable homage games (original takes on well-known games, with original names and art) whose in-game captures must hold up side by side with real shipped-game screenshots. Orchestrates separate planner, builder, and critic subagents through a brief with locked reference shots, a plan, a playable loop, a staged art pipeline, and live captures, then runs fresh-critic rounds against a per-game Visual Bar until WIN, with a diagnoser for stuck loops and a final orchestrator visual read before handoff. Use when asked to build, polish, or compare homage games or vertical slices where visual quality next to real games matters, when a game plays fine but its screenshots look like a browser toy beside the references, or when a reviewer keeps soft-passing weak visuals. Not for general app scaffolds or gameplay-only prototypes.
Score a game's combat skills and spells out of 10 with blind judges, then raise the weakest to a bar, for timing and readability (does a skill read as itself, does the blow land when it lands) and for art (detail, light, trails, impact, art direction, judged against a reference such as Diablo IV). Covers filming casts on a stopped, stepped clock, contact strips and close-ups, anonymised two-judge rounds, the levers that moved scores (hero props made from a painted concept with image-to-3D, own schedules and keyed moves, painted additive textures, camera-facing ribbons, light outside the body), the traps that cost points, asset and load budgets, and shipping each skill as its own version. Use when the user asks to score, review, improve, polish or rebuild combat skills, spells or attacks; says a skill "doesn't make sense", "looks bad" or should look like another game; names a target score; or starts a "next skill" thread. Project specifics (review hooks, harness settings, where each skill's code lives, scores so far) go in an optional local references/<project>.md next to this skill.