trellis-meta

To customize local Trellis architecture, you inspect the generated .trellis files in your project to safely modify workflows, hooks, agents, and specs. This preserves your local modifications while avoiding changes to the global installation or upstream source.

Local Trellis workflow and platform integration layers define project-specific implementation-agent behavior, task routing, and engineering conventions. They separate your local project configurations from the upstream source to ensure safe customization.

You change implementation-agent behavior and hooks by inspecting the local .trellis files and updating the appropriate agent, hook, or workflow entry point. This routes customizations to the correct local files without altering global installations.

Trellis workflow customization supports Cursor and other AI platform directories by guiding changes across platform-specific paths. It preserves local modifications and maintains synchronization across your project's platform integration files.

You should avoid modifying upstream Trellis source because local architecture customizations must be isolated to your project's generated .trellis files. This prevents synchronization conflicts and protects the global installation from unintended changes.

You need to inspect local Trellis files when your project requires different implementation-agent behavior, updated engineering conventions, or modified platform hooks. This identifies the correct local source-of-truth files for changing the specified workflow.