agentleFS
Sign inStart free
mipawnmipawn/cc-use/.agents/skills/trellis-before-dev/SKILL.md

trellis-before-dev

Skill9 starsChanged 21 days 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, 17 of them edited; 2 new projects in the last 4 weeks, against 1 the 4 before.

Adopted by

Rising: 2 new projects took it in the last 4 weeks, 2× the 4 weeks before.thin data

Week of Sep 13: 1 new projectWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 0 new projectsWeek of Nov 1: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 3 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 2 are common, 2 are distinctive, and 0 are very specific to this project.

  • 2

    Common

    Most of the 17 edited versions we read keep these.

  • 2

    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
  1. Common:

    Read the relevant development guidelines before starting your task.

    line 6
  2. Common:

    Follow the "Pre-Development Checklist" section in the index.

    line 29
  3. Distinctive:

    if a local refactor is needed, how you will show it did not change behavior

    line 43
  4. Distinctive:

    If the real scope turns out to be clearly larger than this, say so and why before continuing.

    line 47

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Read the relevant development guidelines before starting your task.

Execute these steps:

  1. Read current task artifacts:
    • prd.md for requirements and acceptance criteria
    • design.md if present for technical design
    • implement.md if present for execution order and validation plan
  2. Discover packages and their spec layers:
    python3 ./.trellis/scripts/get_context.py --mode packages
  3. 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.)
    • Any spec/research paths referenced by the task artifacts
  4. Read the spec index for each relevant module:
    cat .trellis/spec/<package>/<layer>/index.md
    Follow the "Pre-Development Checklist" section in the index.
  5. 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.
  6. Always read shared guides:
    cat .trellis/spec/guides/index.md

  7. For a non-trivial task, state the change boundary before writing code. Non-trivial means it touches more than one file, crosses a layer, changes a public interface, or edits code you did not just write. Write down:

    • the smallest behavior gap between what happens now and what should happen
    • where that behavior actually lives (not where it is easiest to intercept)
    • which files you expect to change, and why each one is necessary
    • what you are explicitly not doing in this task
    • if a local refactor is needed, how you will show it did not change behavior

    A small, well-scoped change does not need this — do it directly.

    If the real scope turns out to be clearly larger than this, say so and why before continuing. Do not widen the change on your own.

  8. Understand the coding standards and patterns you need to follow, then proceed with your development plan.

This step is mandatory before writing any code.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free