trellis-before-dev
Skill301 starsChanged 6 months agoMITView on GitHub
Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.
21 other projects use a version of this, 21 of them edited.
Adopted by
Most recently taken up by
- phoben/agent-skillsedited, first seen Nov 8, 2026
- 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
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
- wayfarer35Skill
trellis-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 · 0
None found.
Edited · 21
- mindfold-ai/Trellis★ 15k47% same
- EcoPasteHub/EcoPaste★ 7.5k72% same
- QiaoKes/fntv-electron★ 1.3k47% same
- mumu-0922/GankAIGC★ 39672% same
- CharTyr/STS2-Agent★ 35774% same
- hsingjui/ContextWeaver★ 29547% same
- fy-agent/fyagent★ 21849% same
- vibex-ai/vibex★ 7072% same
- deequoique/stashseek★ 5872% same
- linyimin0812/folyn★ 4198% same
11 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-brainstormSkill
- trellis-break-loopSkill
- trellis-checkSkill
- trellis-continueSkill
- trellis-finish-workSkill
- trellis-metaSkill
- trellis-spec-bootstarpSkill
- trellis-startSkill
- trellis-update-specSkill
The file
We split this skill into the rules it gives an agent
2 rules. 2 are common, 0 are distinctive, and 0 are very specific to this project.
2
Common
Most of the 21 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 6
Read the relevant development guidelines before starting your task.
- Common: line 23
Follow the "Pre-Development Checklist" section in the index.
“Common” is measured: kept by at least 6 in 10 of the 21 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
Read the relevant development guidelines before starting your task.
Execute these steps:
- Discover packages and their spec layers:
python ./.trellis/scripts/get_context.py --mode packages - Identify which specs apply to your task based on:
- Which package you're modifying (e.g.,
cli/,docs-site/) - What type of work (backend, frontend, unit-test, docs, etc.)
- Which package you're modifying (e.g.,
- Read the spec index for each relevant module:
Follow the "Pre-Development Checklist" section in the index.cat .trellis/spec/<package>/<layer>/index.md - Read the specific guideline files listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g.,
error-handling.md,conventions.md,mock-strategies.md). Read those files to understand the coding standards and patterns. - Always read shared guides:
cat .trellis/spec/guides/index.md - Understand the coding standards and patterns you need to follow, then proceed with your development plan.
This step is mandatory before writing any code.
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.