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 (like node_modules or upstream source) instead of the user project. This Skill gives the AI a complete architectural model and customization entry points so local Trellis behavior is modified correctly. ## Core Features & Use Cases - Local Architecture Reference: Explains the three-layer model (workflow, persistence, platform integration) covering .trellis/workflow.md, tasks, specs, workspace journals, and context injection. - Platform File Map: Documents where hooks, settings, agents, skills, commands, and workflows live across Claude Code, Cursor, Codex, OpenCode, Kiro, Gemini, Copilot, and other platforms. - Customization Playbooks: Step-by-step guides for changing workflow phases, task lifecycle hooks, context loading, agent behavior, skills/commands, and spec structure. - Use Case: A user says "make the check agent run our lint command before reviewing." The AI reads the change-agents reference, locates the platform's trellis-check agent file, and edits it without touching upstream Trellis source. ## Quick Start Ask the AI to use the trellis-meta skill to change the planning-phase behavior in this project's .trellis/workflow.md.