trellis-before-dev

Loads project-specific coding guidelines from .trellis/spec before writing code.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/elebirds/panoptes --skill trellis-before-dev-elebirds
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/elebirds/panoptes/tree/main/.opencode/skills/trellis-before-dev
Command: npx skills add https://github.com/elebirds/panoptes --skill trellis-before-dev-elebirds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers and AI agents often start coding without reviewing project-specific conventions, leading to inconsistent code that violates established standards. This Skill ensures relevant development guidelines are discovered and read before any implementation begins. ## Core Features & Use Cases - Spec Discovery: Runs a Python script to enumerate packages and their spec layers, then identifies which guidelines apply to the current task. - Checklist-Driven Reading: Follows Pre-Development Checklists in spec index files to locate concrete guideline documents like error-handling and conventions files. - Use Case: Before modifying a backend package, an agent runs the discovery script, reads the package's spec index and shared guides, then writes code that follows the project's established patterns. ## Quick Start Before writing any code, load the relevant Trellis spec guidelines for the package I am about to modify.

Frequently Asked Questions about trellis-before-dev

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

FAQPage Schema
How do I load project coding guidelines before writing code?▼

Run the get_context.py script with the packages mode to list available spec layers, then read the relevant package's spec index and follow its Pre-Development Checklist to the actual guideline files.

What is a pre-development checklist for coding standards?▼

It is a section inside each package's spec index file that lists the specific guideline documents to read before implementation, such as error-handling, conventions, and mock-strategies files.

When should I refresh project conventions during a task?▼

Refresh conventions when starting a new coding task, switching to a different package, or changing work type such as moving from backend to frontend or unit tests.

Does this guideline loading require any external tools?▼

It requires Python 3 to execute the get_context.py discovery script and standard shell tools like cat to read the markdown spec files. No third-party packages are needed.

What happens if I skip reading the spec index?▼

Skipping the index means missing the Pre-Development Checklist pointers to concrete guideline files, which risks writing code that violates project standards for error handling, conventions, and testing strategies.