Vfx rendering
Agent Kaizen skill for Claude Code & Codex: faithful, identifier-preserving reference for AWS Lumberyard and CryEngine-family tooling, editor, asset pipeline, Cloud Canvas & AWS gems, Lua; entities, components, EBus, slices, prefabs; CGA/CAF/CHRPARAMS animation; MTL materials, shaders; VFX; Wwise/ATL audio. Archived; O3DE successor.
npx -y skills add LevyBytes/AI-SKILL-lumberyard --skill vfx-renderingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a Lumberyard task involves VFX, particles, rendering, render, effects. Part of the Lumberyard reference router; covers particle effects, VFX, and rendering.
SKILL.md
1.6 KB, as published. Nobody here has run it
Lumberyard VFX, Particles, and Rendering Reference
Faithful, original-prose reference for particle effects, VFX, and rendering. Identifiers (component names, EBus calls, material/shader parameters, file formats, enum values, numbers) are preserved verbatim. One subject per file across 21 reference files.
When to use this
Use this sub-skill when the task involves VFX, particles, rendering, render, effects. It applies even when "Lumberyard" is not named but a relevant tool, file format, or component is in play.
Workflow
- Open
references/INDEX.md(orreferences/topics.json) and pick the one file that matches — the INDEX "Covers" column lists the subjects in each file. - Read only that file; open another only if the task spans subjects. Grep across files when a subject may be split:
rg -n "PATTERN" references/*.md. - Treat every component name, EBus call, parameter, file format, enum value, and number as an exact reference fact — never invent or paraphrase identifiers.
Gotchas
Recurring failure modes and what to do instead live in the sibling GOTCHA.md.
References
All depth lives in references/ — start at references/INDEX.md, with metadata in
references/topics.json. One subject per file.
Verification
python "$env:DEVROOT\SKILLS\skills\skill-drafting\scripts\validate_skill_package.py" "$env:DEVROOT\SKILLS\skills\lumberyard\vfx-rendering"