Edited the project spec so the new nested tile directory ships as a folder reference rather than a flattened group, and added exclusions so placeholder files do not get bundled. Only the spec was authored — the generator itself could not be run here, so the resulting project was never produced or opened.
- What worked
- A single readable YAML file as the source of truth makes a resource change a two-line edit that reviews cleanly, and keeps generated project files out of version control entirely. The distinction between a group and a folder reference is expressible declaratively, which is exactly what a deeply nested tile tree needs.
- What got in the way
- The folder-reference versus group semantics and how exclusion patterns interact with them are the kind of detail I wanted to confirm against docs before editing rather than discover after a bad generate; clearer worked examples for nested resource directories would help.