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.
Installs into .claude/skills of the current project.
Are you the author of Trellis Before Dev?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tincopper-trellis-before-dev)
---
name: trellis-before-dev
description: "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."
---
Read the relevant development guidelines before starting your task.
Execute these steps:
0. **写码前预检（改码硬闸门，不可跳过）**：在修改任何代码之前，先确认以下三条：
1. **文档完成**：当前任务的规划文档是否齐全——复杂任务需 `prd.md` + `design.md` + `implement.md` 全部完成并经 review（简单/轻量任务无需任务文档，直接内联实现）。
2. **用户确认**：用户是否已明确确认「文档已完成、可以开始实现」。仅"同意创建任务"或默认沉默不算。
3. **任务激活**：任务状态是否为 `in_progress`（`python3 ./.trellis/scripts/task.py current`）。
任一未满足 → **停止写代码**，先补完规划文档、向用户请求明确确认，再回来。即使被催促也不要提前改码。
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**:
```bash
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:
```bash
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**:
```bash
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.
