before-dev

Load repository-specific coding guidelines from .trellis/spec/ before implementation.

92|8|Updated May 15, 2026
One-click install
npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill before-dev-lonelyherbivore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: before-dev
Source: https://github.com/LonelyHerbivore/Trellis-Herbivore/tree/main/packages/cli/src/templates/codex/skills/before-dev
Command: npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill before-dev-lonelyherbivore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents rework by ensuring you read and apply the repository’s task-specific and package-specific coding guidelines from .trellis/spec/ before starting implementation.

Core Features & Use Cases

  • Requirements-to-guidelines alignment: Reviews prd.md, and design.md/implement.md when present, to understand what “done” means before coding.
  • Package-scoped spec discovery: Uses package mode to discover which spec layers apply to the target package and work type.
  • Checklist-driven guideline ingestion: Reads the relevant module index.md “Pre-Development Checklist” and then loads the specific guideline files it points to, plus shared guides.

Quick Start

Use before-dev to refresh Trellis-spec conventions for your current coding task, by ensuring the correct package guidelines from .trellis/spec/ are loaded before you start writing code.

Frequently Asked Questions about before-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I align coding guidelines with task requirements before development?

Align coding guidelines by reading task artifacts like prd.md and design.md, then running a context discovery script to load repository-specific specs from .trellis/spec/ directories before writing code.

What is package-scoped spec discovery for repository standards?

Package-scoped spec discovery identifies and loads the specific coding guidelines and architecture constraints applicable to your target package and work type from module index.md files.

How do I prevent rework when starting a new coding task?

Prevent rework by ingesting referenced guideline documents and shared guides through a pre-development checklist, ensuring repository standards are applied before implementation begins.

Can I use this to refresh standards for backend, frontend, tests, or docs work?

Yes, you can refresh Trellis-spec conventions for backend, frontend, tests, or docs work by discovering and loading the correct package guidelines from .trellis/spec/ before coding.

Do I need prd.md and design.md files to discover applicable specs?

You need prd.md to understand requirements, while design.md and implement.md are optional task artifacts that provide further context for aligning implementation work with coding guidelines.

What's the best way to load architecture constraints before coding?

The best way to load architecture constraints is running context discovery scripts to locate relevant package layer index.md files, then ingesting the specific guideline files they reference.