trellis-meta

Map and customize local Trellis architecture within initialized user projects.

92|8|Updated May 15, 2026
One-click install
npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill trellis-meta-lonelyherbivore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-meta
Source: https://github.com/LonelyHerbivore/Trellis-Herbivore/tree/main/.cursor/skills/trellis-meta
Command: npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill trellis-meta-lonelyherbivore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps you understand and safely customize the local Trellis architecture inside an already-initialized user project, so the AI edits the right files in the right places instead of guessing.

Core Features & Use Cases

  • Maps the local Trellis system: clarifies the workflow, task system, spec injection, workspace memory, and context-loading mechanisms within .trellis/.
  • Guides correct customization targets: directs edits toward .trellis/ plus the appropriate platform directories (e.g., .claude/, .cursor/, .github/) and the shared skill layer when applicable.
  • Ensures on-project authority: instructs the AI to read the user project’s existing generated files first and avoid assuming upstream Trellis source or global npm locations.

Quick Start

Use the trellis-meta skill to adjust your project’s Trellis behavior by asking: "Update my local Trellis setup to change how context is injected for sub-agents, and apply the changes only inside this repo."

Frequently Asked Questions about trellis-meta

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I customize the local Trellis workflow in my project after running trellis init?

To customize your local Trellis workflow, modify the generated files within the .trellis directory and the appropriate platform directories like .claude or .cursor. Always read the existing project files first to ensure your edits target the correct local architecture.

Where should I place configuration changes for Trellis context injection and sub-agents?

Configuration changes for Trellis context injection and sub-agents belong inside the .trellis directory and applicable platform folders. This ensures the local runtime loads your custom context boundaries correctly without altering upstream Trellis source code.

Can I modify Trellis platform hooks and workspace memory without affecting the global install?

Yes, you can modify platform hooks, skills, and workspace memory safely. Direct your edits strictly to the local .trellis directory and shared skill layer, completely avoiding changes to the global node_modules or upstream Trellis source installs.

What is the correct approach for adjusting spec management and task systems in an initialized Trellis project?

The correct approach for adjusting spec management and task systems is to use references-first guidance. Read the authoritative files under .trellis to understand the existing mechanisms before applying targeted edits to the local workflow configuration.

Why does my AI assistant edit the wrong files when I try to update my Trellis setup?

Your AI assistant edits wrong files when it assumes upstream Trellis source locations instead of local project directories. Use trellis-meta to map the local .trellis architecture so the AI understands the correct context loading boundaries and customization targets.