菜单
Game Art Principles workflow skill. Use this skill when the user needs game art principles: visual style selection, asset pipeline decisions, animation workflow, and production-aware art direction that can ship. Preserve upstream intent and provenance when handing off or merging.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/diegosouzapw/awesome-omni-skills --skill game-art命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Daily Gift workflow skill. Use this skill when the user needs Relationship-aware daily gift engine with five-stage creative pipeline — editorial judgment, synthesis, concept generation, visual strategy, and rendering in H5, image, or video and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Daily Gift workflow skill. Use this skill when the user needs Relationship-aware daily gift engine with five-stage creative pipeline — editorial judgment, synthesis, concept generation, visual strategy, and rendering in H5, image, or video and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
High-Agency Frontend Skill workflow skill. Use this skill when the user needs building high-agency frontend interfaces with strict design taste, calibrated color, responsive layout, and motion rules and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
基于 SOC 职业分类
| name | game-art |
| description | Game Art Principles workflow skill. Use this skill when the user needs game art principles: visual style selection, asset pipeline decisions, animation workflow, and production-aware art direction that can ship. Preserve upstream intent and provenance when handing off or merging. |
| version | 0.0.1 |
| category | cli-automation |
| tags | ["game-art","game","art","art-direction","asset-pipeline","animation","style-guide","production","omni-enhanced"] |
| complexity | intermediate |
| risk | caution |
| tools | ["codex-cli","claude-code","cursor","gemini-cli","opencode"] |
| source | omni-team |
| author | Omni Skills Team |
| license | Unknown |
| date_added | 2026-04-15 |
| date_updated | 2026-05-10 |
| source_type | omni-curated |
| maintainer | Omni Skills Team |
| family_id | game-art |
| family_name | Game Art Principles |
| variant_id | omni |
| variant_label | Omni Curated |
| is_default_variant | true |
| derived_from | skills/game-art |
| upstream_skill | skills/game-art |
| upstream_author | sickn33 |
| upstream_source | community |
| upstream_pr | 271 |
| upstream_head_repo | diegosouzapw/awesome-omni-skills |
| upstream_head_sha | 93ab394af5645f7127d5003ee02c9566ae5353cd |
| curation_surface | skills_omni |
| enhanced_origin | omni-skills-private |
| source_repo | diegosouzapw/awesome-omni-skills |
| replaces | ["game-art"] |
This skill preserves the upstream intent of game art principles while making it operational for production use. Use it to turn a vague art-direction request into a concrete, shippable plan covering:
This is not a drawing tutorial. It is a workflow for deciding how art should be made and integrated so the project stays consistent, readable, and technically manageable.
Use this skill when the request is about defining or reviewing how game art should be structured, not just whether something “looks cool.”
Typical triggers:
Do not use this skill as the primary tool when:
Before recommending a style or pipeline, collect the minimum production context:
If these are unknown, state assumptions explicitly before proposing a pipeline.
Define the visual target in production terms
Lock camera, readability, and interaction priorities
Set resolution and scale rules before asset production
Choose asset structure and import rules
Design the animation workflow around reuse
Apply color, contrast, and accessibility checks
Document anti-patterns and acceptance rules
Produce the handoff brief
A good final answer from this skill usually contains:
Input
Game: top-down mobile action roguelite
Platforms: iOS and Android
Camera: distant, always moving
Needs: readable enemies, fast combat clarity, many repeated props
Team: 2 artists, 1 animator
Recommended output
Choose stylized 2D with simplified shapes and high silhouette contrast.
Avoid detail-heavy painted textures because gameplay distance is too far to reward them.
Use a limited palette with strong value separation between player, enemies, hazards, and pickups.
Atlas repeated environment props by biome.
Keep VFX shapes bold and short-lived so they do not hide enemy attacks.
Prefer cutout or lightweight skeletal animation for reusable enemies and UI-adjacent character motion.
Input
Game: side-view platformer
Art direction: pixel art
Problem: character, tiles, and UI mockups were created at different pixel densities
Recommended output
Stop new asset production until a base pixel density is defined.
Set one character reference sheet and one tile-size rule as the project anchor.
Require environment tiles, props, and effects to match that density.
Keep UI either intentionally pixel-matched or intentionally separated as higher-resolution interface art; do not mix by accident.
Input
Game: third-person RPG
Need: 20 humanoid NPC variants with similar movement
Recommended output
Adopt a shared humanoid skeleton and consistent bone naming before authoring variants.
Retarget common locomotion and idle sets rather than animating each NPC from scratch.
Define export settings and validation checks once, then require all variants to conform.
Reserve unique animation work for hero characters and special interactions only.
For a longer worked example with concrete decision tables, open examples/worked-example.md.
Do choose style based on camera distance, gameplay density, and production capacity.
Do define scale, texel density, or pixel density before content volume grows.
Do establish folder, naming, and export rules before multiple contributors start producing assets.
Do treat atlas and import settings as design decisions, not cleanup work for later.
Do plan animation reuse early when many related characters or props exist.
Do evaluate color and contrast under actual gameplay conditions, not only isolated mockups.
Do preserve provenance and existing upstream support files when the task is an enhancement or handoff.
Do not approve a style that depends on fine texture detail when the gameplay camera is far away.
Do not let each artist invent their own scale or naming rules.
Do not mix realistic materials, exaggerated silhouettes, and conflicting UI styles without a deliberate system.
Do not rely only on color to indicate team, danger, rarity, or interaction state.
Do not create unique skeletons or export settings per character unless there is a strong reason.
Do not postpone import and packing policy until after hundreds of assets already exist.
Symptoms: The art looks good in mockups but unreadable during gameplay.
Solution: Re-check gameplay camera distance, movement speed, object overlap, and silhouette contrast. Simplify shapes, increase value separation, and remove detail that does not survive at runtime scale.
Symptoms: Assets feel inconsistent even though individual pieces are high quality.
Solution: Audit scale, line weight, texture treatment, palette range, and naming/export conventions. Inconsistency usually comes from missing production rules, not lack of artistic effort.
Symptoms: UI and world art clash visually.
Solution: Decide whether UI should share the world style or intentionally sit above it. Align typography, icon treatment, contrast targets, and scale logic instead of letting UI evolve independently.
Symptoms: Import settings and atlases keep changing late in production.
Solution: Move import defaults, atlas policy, and source/export ownership into the project brief. Late churn here usually signals that the pipeline was never defined clearly enough.
Symptoms: Animation integration is slow and brittle.
Solution: Standardize skeletons, naming, export settings, and clip ownership. Reduce one-off rigs where reuse is expected. Validate engine import assumptions before expanding content production.
Symptoms: Players miss hazards or interactables.
Solution: Increase silhouette distinction, motion cues, contrast, and placement logic. Confirm that critical states are readable without relying only on hue.
references/domain-notes.md — open this for compact engine- and pipeline-oriented notes on atlas policy, naming, redirector cleanup, scale systems, accessibility checks, and animation import caveats.examples/worked-example.md — open this when you need a concrete before/after transformation from vague art request to production-ready brief.No verified related local skills were provided in the source context.