trellis-meta

Read and customize local Trellis architecture files within a user project.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/C-jcbest/agent --skill trellis-meta-c-jcbest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-meta
Source: https://github.com/C-jcbest/agent/tree/main/.agents/skills/trellis-meta
Command: npx skills add https://github.com/C-jcbest/agent --skill trellis-meta-c-jcbest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Understand and customize the local Trellis architecture inside a user project to tailor the generated .trellis/ and platform files to project needs while avoiding modifications to upstream Trellis sources.

Core Features & Use Cases

  • Reads and interprets the local Trellis structure (including .trellis/workflow.md, .trellis/spec/, .trellis/tasks/, workspace, and platform directories like .claude/, .codex/, etc.).
  • Guides safe, project-bound customization by editing only generated files or project-local specs and skills.
  • Supports aligning workflow routing, task lifecycles, and local conventions with the project's reality, then applying changes across the relevant platform directories when requested.

Quick Start

Read the local Trellis architecture and platform entry points, then instruct the AI to modify the appropriate .trellis/ and platform files in the user project.

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 architecture inside my project?

To customize the local Trellis architecture, you edit only the generated files within the .trellis/ directory and platform directories like .claude/, .codex/, and .cursor/, ensuring changes stay project-bound without modifying upstream Trellis sources.

What files does the local Trellis workflow structure include?

The local Trellis workflow structure includes files under .trellis/ such as workflow.md, spec/, tasks/, workspace, alongside platform directories including .claude/, .codex/, and .cursor/ that manage project-specific routing and context.

Can I modify platform directories like .claude and .codex without affecting upstream Trellis?

Yes, you can modify platform directories like .claude and .codex safely. The skill reads relevant JSONL and context files, updating only allowed project-local files to align with your conventions while preventing modifications to upstream Trellis.

How do I align workflow routing and task lifecycles with my project's reality?

You align workflow routing and task lifecycles by reading the local Trellis architecture and instructing the AI to modify the appropriate .trellis/ and platform files, applying changes across relevant directories to match your project's reality.

Do I need to run trellis init before customizing local architecture files?

Yes, you need to run trellis init first. This skill specifically targets projects where trellis init has already been run, ensuring the local .trellis/ structure and platform entry points exist before applying any project-bound customizations.

What are the limitations when editing local Trellis spec and skill files?

The main limitation is that you cannot modify upstream Trellis sources. Customization is strictly constrained to editing generated files or project-local specs and skills within the .trellis/ and platform directories to ensure safe changes.