LeoYeAI/agent-master-skills / skills/animation-shader
animation-shader
VerifiedREAD this skill when implementing or configuring animation-style shaders (Toon/Cel Shaders) — including outlines, rim lighting, toon shading, MatCap, emission, dissolve, hatching, or any stylized rendering effect. Contains preset styles and feature-to-reference mappings for lilToon, Poiyomi, UTS2, RToon, SToon, and ToonShadingCollection. Works as a domain knowledge plugin alongside workflow skills (OpenSpec, SpecKit) or plan mode of an agent.
references/ToonShadingCollection/Details/01_ArtStyles.md
View on GitHub# Art Styles (画风概述)
## 美式卡通 vs 日式卡通
### 美式卡通 (Western Style)
* **着色**: 色彩比较连续、有渐变色,接近真实感光照。阴影和高光方面通常也有夸张和变形。依赖艺术家定义的 tone 色调。
* **造型**: 人物造型夸张。
* **典型例子**: 《军团要塞2》
### 日式卡通 (Eastern/Anime Style)
* **着色**: 趋向于大片纯色色块(Cel-Shading)。明暗交界分明(Hard Edge),趋向于不连续的渐变。
* **造型**: 人物造型比美式写实,但五官风格化(大眼、概括的鼻子嘴巴)。
* **典型例子**: 《崩坏3》、《原神》、《罪恶装备》
## 画风趋势探讨
卡通渲染在动画和游戏中的制作思路是不同的:
* **动画**: 相机经常是固定角度,可以手动修正瑕疵。
* **游戏**: 注重在不同环境与角度下效果表现的合理性。因为 2D 画面在 3D 空间中并非完全成立,需要大量 Trick。
### 构成画面感的四个要素
无论做赛璐璐风格还是半写实风格,以下四个要素是通用的:
1. **减少色阶的数量 (Quantization)**: 随着色阶减少,卡通感增强。
2. **明暗色调分离 (Tone Separation)**: 亮面暖色调,暗面冷色调,增强光感。
3. **阴影的手绘控制 (Stylized Shadow Control)**: 阴影形状服务于美术审美,而非纯物理计算(如脖子上的固定阴影、脸部特殊的阴影形状)。
4. **描边 (Outline)**: 重要的轮廓表现,强调主体。
### 发展方向
1. **极致赛璐璐**: 忽略结构,对 Mesh 进行更夸张的处理(如《罪恶装备》的逐帧模型替换)。
2. **PBR 结合**: 使用 PBR 流程表现材质(金属、皮革),但保留卡通的光影概括。
3. **动画摄影后期**: 引入影视行业的后期合成特效(Flare, Para, 滤镜)。
## “赛璐璐已死”?
关于单纯赛璐璐风格在现代游戏竞争中的局限性讨论:
* **观点**: 单纯的赛璐璐在表现力上已难拉开差距(同质化严重)。死守赛璐璐路线可能面临“卷”不赢头部厂商的风险。
* **“借物”的重要性**: PBR 的优势在于可以“抄袭”现实(低成本高产能)。NPR 需要寻找成体系的参考物(如成熟的 2D 动画影视作品)。
* **出路**:
* 探索 NPR 与 PBR 的结合。
* 引入影视化的后期效果。
* 风格细分(如“厚涂”风格的游戏化)。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |