agentsclimarketplace

Trellis before dev

Skill lifan-builds/context-harness/.agents/skills/trellis-before-dev

Lightweight durable context for AI coding agents: 4 files, 9 rules, companion skills, and scripts that let agents self-iterate inside your workflow.

Install
npx -y skills add lifan-builds/context-harness --skill trellis-before-dev

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.8 KB, 343 tokens by cl100k_base, as published. Nobody here has run it

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. Understand the coding standards and patterns you need to follow, then proceed with your development plan.

This step is mandatory before writing any code.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.