Overview

Lumberyard Overview and Platform Reference

Faithful, original-prose reference for Lumberyard and CryEngine-family overview, the editor, asset pipeline, Cloud Canvas / AWS gems, Lua scripting, and general workflow. Identifiers (component names, EBus calls, material/shader parameters, file formats, enum values, numbers) are preserved verbatim. One subject per file across 64 reference files.

When to use this

Use this sub-skill when the task involves Lumberyard overview, editor, asset pipeline, Cloud Canvas, AWS gems, Lua, setup, project. It applies even when "Lumberyard" is not named but a relevant tool, file format, or component is in play.

Workflow

1. Open references/INDEX.md (or references/topics.json) and pick the one file that matches — the INDEX "Covers" column lists the subjects in each file.
2. 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.
3. 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\overview"