trellis-meta

Document local Trellis project architecture and customization entry points.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/znc15/Open-Design --skill trellis-meta-znc15
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-meta
Source: https://github.com/znc15/Open-Design/tree/main/.cursor/skills/trellis-meta
Command: npx skills add https://github.com/znc15/Open-Design --skill trellis-meta-znc15

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a centralized knowledge base for managing local Trellis project configurations, preventing the need to guess how to customize workflows, agents, or project-specific conventions.

Core Features & Use Cases

  • Architecture Guidance: Explains the three-layer Trellis model (Workflow, Persistence, Platform Integration).
  • Customization Entry Points: Provides clear instructions on where to modify hooks, agents, and spec files without touching upstream source code.
  • Use Case: When a team needs to enforce specific coding standards or modify the task lifecycle, this skill guides the AI to the correct local configuration files like .trellis/spec/ or .trellis/config.yaml.

Quick Start

Read the local architecture overview to understand how to customize the Trellis workflow for this project.

Frequently Asked Questions about trellis-meta

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

FAQPage Schema
What is the three-layer Trellis architecture for local project configuration?▼

The three-layer Trellis architecture consists of Workflow, Persistence, and Platform Integration layers. It provides a structured model for managing local project configurations, ensuring AI references authoritative local files rather than global dependencies.

How do I customize Trellis workflow phases and task lifecycles without modifying upstream source code?▼

Customize Trellis workflow phases and task lifecycles by modifying local configuration files like .trellis/spec/ or .trellis/config.yaml. This approach provides clear entry points for hooks, agents, and spec files without touching upstream source code.

Where should I configure platform-specific hooks in a Trellis project?▼

Configure platform-specific hooks in local project configuration files. The skill directs AI to authoritative local files such as .trellis/spec/ or .trellis/config.yaml, ensuring consistent configuration management without relying on global dependencies.

Can I enforce specific coding standards for my team using local Trellis configuration files?▼

Yes, you can enforce specific coding standards by guiding AI to local configuration files like .trellis/spec/ or .trellis/config.yaml. This centralizes project-specific conventions and prevents the need to guess how to customize workflows or agents.

Why does my AI agent struggle with consistent configuration management in a customized Trellis workflow?▼

AI agents struggle with consistent configuration management when they reference global dependencies instead of authoritative local files. This skill solves the issue by directing the AI to local files like .trellis/config.yaml for project-specific engineering specifications.