trellis-meta
Skill301 starsChanged 6 months agoMITView on GitHub
Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, or workflows generated by trellis init.
- Installs packages
21 other projects use a version of this, 19 of them edited.
Adopted by
Most recently taken up by
- vibex-ai/vibexedited, first seen Nov 12, 2026
- phoben/agent-skillsedited, first seen Nov 8, 2026
- mipawn/cc-useedited, first seen Nov 1, 2026
- deequoique/stashseekedited, first seen Oct 20, 2026
- tmdy/CodeDeckedited, first seen Oct 18, 2026
- zhexin233-ui/easytoagentsedited, first seen Oct 11, 2026
Used with
Projects with it also use trellis-channel, trellis-session-insight and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
wayfarer35Skilltrellis-channel
Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.
Also in 18 projects that use this
wayfarer35Skilltrellis-session-insight
Reach into past AI conversation history through the `trellis mem` CLI. Use whenever the user asks 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', 'remind me what we did in this task', '上次怎么解的', '之前讨论过吗', '想起一段对话', or when starting a brainstorm that overlaps prior work, debugging a familiar bug, continuing a task across sessions, or doing a finish-work review. Returns raw past dialogue; decide for the moment whether to update spec, append to task notes, quote inline in the answer, or just internalize.
Also in 18 projects that use this
- +1 more from wayfarer35
Other versions21 projects use a version of this.
Word for word · 2
- mumu-0922/GankAIGC★ 396100% same
- linyimin0812/folyn★ 41100% same
Edited · 19
- mindfold-ai/Trellis★ 15k28% same
- EcoPasteHub/EcoPaste★ 7.5k29% same
- QiaoKes/fntv-electron★ 1.3k28% same
- CharTyr/STS2-Agent★ 35729% same
- hsingjui/ContextWeaver★ 29528% same
- vibex-ai/vibex★ 24529% same
- fy-agent/fyagent★ 21828% same
- deequoique/stashseek★ 5829% same
- mipawn/cc-use★ 928% same
- xhl592576605/agent-skills-mesh★ 829% same
9 more not listed
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- trellis-before-devSkill
- trellis-brainstormSkill
- trellis-break-loopSkill
- trellis-checkSkill
- trellis-continueSkill
- trellis-finish-workSkill
- trellis-spec-bootstarpSkill
- trellis-startSkill
- trellis-update-specSkill
The file
We split this skill into the rules it gives an agent
10 rules. 2 are common, 2 are distinctive, and 6 are very specific to this project.
2
Common
Most of the 19 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 16
Do not assume the user has the Trellis source repository.
- Very specific: line 20
Read references/local-architecture/overview.md first to establish the local Trellis system model.
- Very specific: line 21
If the request involves a specific AI tool, read references/platform-files/platform-map.md and the relevant platform file notes.
- Very specific: line 22
If the user wants to change behavior, read references/customize-local/overview.md, then open the specific customization topic.
- Common: line 23
Before editing, read the actual files in the user project and treat local content as authoritative.
- Common: line 69
Do not treat Trellis upstream source code as the default target for local customization.
- Very specific: line 70
Do not modify the global npm install directory or node_modules/@mindfoldhq/trellis to implement project needs.
- Distinctive: line 71
Do not overwrite user-modified local files with default templates.
- Very specific: line 72
Do not put team-private project rules into the public trellis-meta.
- Distinctive: line 73
Do not describe removed historical mechanisms as current Trellis behavior.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Trellis Meta
This skill is for local Trellis users who have already run trellis init in a project. After reading it, an AI should understand the Trellis architecture, operating model, and customization entry points inside that user project, then modify the generated .trellis/ and platform directory files according to the user's request.
The default operating scope is local files in the user project:
.trellis/: workflow, config, tasks, spec, workspace, scripts, and runtime state.- Platform directories:
.claude/,.codex/,.cursor/,.opencode/,.kiro/,.gemini/,.qoder/,.codebuddy/,.github/,.factory/,.pi/,.kilocode/,.agent/,.windsurf/, and similar directories. - Shared skill layer:
.agents/skills/.
Do not assume the user has the Trellis source repository. Do not default to modifying the global npm install directory or node_modules.
How To Use
- Read
references/local-architecture/overview.mdfirst to establish the local Trellis system model. - If the request involves a specific AI tool, read
references/platform-files/platform-map.mdand the relevant platform file notes. - If the user wants to change behavior, read
references/customize-local/overview.md, then open the specific customization topic. - Before editing, read the actual files in the user project and treat local content as authoritative.
References
Local Architecture
references/local-architecture/overview.md: The three-layer local Trellis architecture and customization principles.references/local-architecture/generated-files.md: Files generated bytrellis initand their customization boundaries.references/local-architecture/workflow.md: Phases, routing, and workflow-state blocks in.trellis/workflow.md.references/local-architecture/task-system.md: Task directories, active tasks, JSONL context, and task runtime.references/local-architecture/spec-system.md: How.trellis/spec/is organized and injected.references/local-architecture/workspace-memory.md:.trellis/workspace/, journals, and cross-session memory.references/local-architecture/context-injection.md: Hooks, sub-agent preludes, and context injection paths.
Platform Files
references/platform-files/overview.md: How shared.trellis/files relate to platform directories.references/platform-files/platform-map.md: Platform directories and paths for skills, agents, hooks, and extensions.references/platform-files/hooks-and-settings.md: How settings/config files, hooks, plugins, and extensions connect to Trellis.references/platform-files/agents.md: Local file responsibilities fortrellis-research,trellis-implement, andtrellis-check.references/platform-files/skills-and-commands.md: Differences between skills, commands, prompts, and workflows, plus how to change them.
Local Customization
references/customize-local/overview.md: Choose the right local customization entry point for the user's request.references/customize-local/change-workflow.md: Change phases, routing, next actions, and workflow-state.references/customize-local/change-task-lifecycle.md: Change task creation, status, archive behavior, and hooks.references/customize-local/change-context-loading.md: Change how tasks, specs, journals, and hook context are loaded.references/customize-local/change-hooks.md: Change platform hooks, settings, and shell session bridges.references/customize-local/change-agents.md: Change research, implement, and check agent behavior.references/customize-local/change-skills-or-commands.md: Add or modify local skills, commands, prompts, and workflows.references/customize-local/change-spec-structure.md: Adjust the project spec structure under.trellis/spec/.references/customize-local/add-project-local-conventions.md: Put team rules into project-local specs or local skills.
Current Rules
.trellis/workflow.mdis the local workflow source of truth..trellis/config.yamlis the project-level Trellis configuration and task hook configuration entry point..trellis/spec/stores the user's project-specific coding conventions and design constraints..trellis/tasks/stores task PRDs, technical notes, research files, and JSONL context..trellis/workspace/stores developer journals and cross-session memory.- Platform settings/config files decide which hooks, agents, skills, commands, prompts, and workflows actually run.
.trellis/.template-hashes.jsonand.trellis/.runtime/are management/runtime state files. Confirm necessity before editing them.
Do Not
- Do not treat Trellis upstream source code as the default target for local customization.
- Do not modify the global npm install directory or
node_modules/@mindfoldhq/trellisto implement project needs. - Do not overwrite user-modified local files with default templates.
- Do not put team-private project rules into the public
trellis-meta; put project rules in.trellis/spec/or a project-local skill. - Do not describe removed historical mechanisms as current Trellis behavior.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

