trellis-spec-bootstrap
Skill0 starsChanged 11 days agoMITView on GitHub
通过平台无关的单代理流程建立或刷新项目专属 Trellis 编码规范；适用于创建 .trellis/spec、通过 GitNexus、ABCoder 或源码分析代码库、拆分包与层的规范工作并编写有真实代码依据的文档时。
17 other projects use a version of this, 17 of them edited.
Adopted by
Most recently taken up by
- vibex-ai/vibexedited, 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
- CharTyr/STS2-Agentedited, first seen Oct 8, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 17
- mindfold-ai/Trellis★ 15k87% same
- EcoPasteHub/EcoPaste★ 7.5k87% same
- QiaoKes/fntv-electron★ 1.3k87% same
- CharTyr/STS2-Agent★ 35787% same
- hsingjui/ContextWeaver★ 29587% same
- fy-agent/fyagent★ 21887% same
- vibex-ai/vibex★ 7087% same
- deequoique/stashseek★ 5887% same
- mipawn/cc-use★ 987% same
- xhl592576605/agent-skills-mesh★ 887% same
7 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- jev-browser-useSkill
- Plugin StructureSkill
- trellis-before-devSkill
- trellis-brainstormSkill
- trellis-break-loopSkill
- trellis-channelSkill
- trellis-checkSkill
- trellis-continueSkill
- trellis-finish-workSkill
- trellis-metaSkill
- trellis-session-insightSkill
- trellis-startSkill
- trellis-update-specSkill
- version-releaseSkill
The file
We split this skill into the rules it gives an agent
6 rules. 5 are common, 0 are distinctive, and 1 is very specific to this project.
5
Common
Most of the 17 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 16
Verify that the final specs are internally consistent and contain no template placeholders.
- Common: line 29
Treat templates as starting points, not contracts.
- Common: line 30
Prefer source-backed rules over generic advice.
- Common: line 31
Keep execution single-owner by default.
- Common: line 32
Do not write platform-specific instructions unless the target project already standardizes on that platform.
- Very specific: line 33
Do not leave placeholder text, empty headings, or copied boilerplate in .trellis/spec/.
“Common” is measured: kept by at least 6 in 10 of the 17 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 Spec Bootstrap
Use this skill to create or refresh .trellis/spec/ guidelines from the real codebase. One capable agent owns the full loop: analyze the repository, choose the spec boundaries, write the docs, and verify the result. The workflow does not depend on a specific host, CLI, or agent brand.
Workflow
- Confirm Trellis is initialized and inspect the current
.trellis/spec/tree. - Analyze the repository architecture with the best available tools: GitNexus, ABCoder, language tooling, and direct source reads.
- Decompose the spec work by package and layer only when that reflects the actual codebase.
- Fill or reshape the spec files with concrete patterns, file paths, examples, and anti-patterns from the project.
- Verify that the final specs are internally consistent and contain no template placeholders.
Reference Routing
| Need | Read |
| Repository architecture analysis | references/repository-analysis.md |
| Spec work decomposition and task planning | references/spec-task-planning.md |
| Writing high-signal Trellis spec files | references/spec-writing.md |
| GitNexus and ABCoder MCP setup | references/mcp-setup.md |
Operating Rules
- Treat templates as starting points, not contracts. Delete, rename, split, or add spec files when the repository calls for it.
- Prefer source-backed rules over generic advice. Every important recommendation should point at a real file or repeated local pattern.
- Keep execution single-owner by default. Optional helper agents are an implementation detail, not a requirement or user-visible dependency.
- Do not write platform-specific instructions unless the target project already standardizes on that platform.
- Do not leave placeholder text, empty headings, or copied boilerplate in
.trellis/spec/.
Done Criteria
.trellis/spec/describes the project as it exists now.- Each relevant package or layer has practical coding guidance with real examples.
- Non-applicable template sections are removed.
index.mdfiles match the final spec file set.- Any required setup or analysis assumptions are documented in the relevant spec or task notes.
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.