trellis-meta

Local Trellis architecture is the project-specific structure generated by trellis init, comprising the .trellis directory, platform directories, and a shared skill layer that organizes settings, agents, commands, prompts, and workflows for AI-driven customization.

To modify platform hooks and workflows generated by trellis init, reference the local architecture references and apply changes directly to the generated files inside .trellis or platform directories, adjusting routing and local conventions as needed.

Yes, you can customize Trellis routing and local conventions by modifying the generated files within the .trellis directory and platform hooks. The architecture is designed to support adjusting task lifecycles, specs, and workflow routing according to project needs.

Yes, the Trellis architecture supports modifying task lifecycles and specs. It reads and internalizes the local structure to guide modifications to workflows, specs, and platform hooks, explaining how changes propagate throughout the project setup.

The best way to map local Trellis structure to a customization plan is to explore the local architecture references, identify the relevant .trellis files and platform hooks, then direct the AI to modify the generated agents, skills, commands, or workflows accordingly.

You need to reference local architecture references before adjusting Trellis settings whenever modifying .trellis configurations, platform hooks, agents, skills, commands, prompts, or workflows, ensuring changes align with the established local layout and propagate correctly.