SkillsAdd

mindfold-ai/trellis

trellis-before-dev

Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins.

First seen Apr 29, 2026

Installation

$ npx skills add mindfold-ai/trellis --skill trellis-before-dev
View on skills.sh ↗ GitHub repository ↗

Summary

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

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from mindfold-ai/trellis · top by installs.

npx skills add mindfold-ai/trellis
trellis-meta 383 trellis-brainstorm 144 trellis-finish-work 128 trellis-check 125 trellis-continue 122 trellis-update-spec 114 trellis-start 113 trellis-break-loop 113 python-design 104 contribute 99

Browse all from mindfold-ai/trellis

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 14.5K
License LICENSE
Default branch main
Open issues 45
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,642 B
  • docs SUMMARY.md 384 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 117 installs

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

  1. Discover packages and their spec layers:

``bash python3 ./.trellis/scripts/get_context.py --mode packages ``

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

  1. Read the spec index for each relevant module:

``bash cat .trellis/spec/<package>/<layer>/index.md `` Follow the "Pre-Development Checklist" section in the index.

  1. 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.
  1. Always read shared guides:

``bash cat .trellis/spec/guides/index.md ``

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

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

This step is mandatory before writing any code.