What problem does it solve? After running trellis init, a project contains many generated files across .trellis/ and platform directories (.claude/, .codex/, .agents/, etc.). This Skill teaches an AI how that local Trellis architecture fits together and where to safely make customizations without breaking managed files. ## Core Features & Use Cases - Architecture Map: Explains the workflow, task, spec, workspace memory, context injection, and multi-agent channel runtime layers, plus how platform hooks, agents, skills, and commands connect to them. - Ownership-Aware Editing: Distinguishes project-local files from upstream Trellis templates and Flower/Skill-Garden managed overlays using .flower/state.json, .trellis/.template-hashes.json, and patch markers, so edits go to the durable source. - Customization Routing: Reference guides route requests like changing workflow phases, task lifecycle hooks, agent behavior, context loading, spec structure, or adding project-local skills to the correct file. - Use Case: A user asks the AI to make the check agent run extra project commands; the Skill directs the AI to the platform's trellis-check agent file and .trellis/spec/ instead of editing bundled templates that trellis update would overwrite. ## Quick Start Ask the AI to explain how this project's Trellis workflow and agents are wired, then request a specific customization such as changing the planning phase behavior.