What problem does it solve? After running trellis init, AI assistants often lack a map of the generated .trellis/ directory and platform integration files, leading to edits in the wrong place (such as node_modules or upstream source) or broken workflow semantics. This Skill gives the AI a complete architectural model and customization entry points for local Trellis projects. ## Core Features & Use Cases - Architecture Reference: Explains the three-layer local Trellis model covering workflow.md, tasks, specs, workspace memory, and context injection. - Platform File Map: Documents where hooks, settings, agents, skills, and commands live across Claude Code, Cursor, Codex, Kiro, Gemini, and other platforms. - Customization Guides: Provides task-oriented guides for changing workflows, task lifecycles, context loading, hooks, agents, skills, and spec structure. - Use Case: A user asks to make the check agent run project-specific lint commands; the AI reads the change-agents guide, locates the platform's trellis-check agent file, and edits it while preserving role boundaries. ## Quick Start Ask the AI to use the trellis-meta skill to change the local Trellis workflow so that task creation is optional for small fixes.