trellis-before-dev

Parse project spec layers and guides to apply coding standards before development.

Updated May 2, 2026

Search Tags:#coding conventions #project standards #coding guidelines #pre-development checklist #spec layers analysis

Ready to run

npx skills add https://github.com/WASIDJ/git-demo --skill trellis-before-dev-wasidj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/WASIDJ/git-demo/tree/main/.opencode/skills/trellis-before-dev
Command: npx skills add https://github.com/WASIDJ/git-demo --skill trellis-before-dev-wasidj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps ensure that all developers adhere to project-specific coding guidelines and standards, reducing the time spent on debugging and code quality issues.

Core Features & Use Cases

Pre-Development Guidelines: Discovers and injects coding guidelines from a project's .trellis directory before any code is written.
Spec Layers Analysis: Reads spec indexes and pre-development checklists to apply the correct coding standards.
Shared Guides: Provides access to shared guides for consistent coding practices.
Use Case: When starting a new coding task, switching to a different package, or needing to refresh project conventions and standards.

Quick Start

Before writing any code for your new task, use the 'trellis-before-dev' skill to ensure you're following all relevant coding guidelines.

Frequently Asked Questions about trellis-before-dev

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

FAQPage Schema

How do I enforce coding conventions before starting development on a new package?▼

To enforce coding conventions before development, you can parse project-specific spec layers and guides from a .trellis directory. This injects relevant guidelines directly into your workflow, ensuring coding standards are met before any code is written.

What are pre-development guidelines and how do they work with spec layers analysis?▼

Pre-development guidelines are project-specific coding standards applied before writing new code. Spec layers analysis works by reading spec indexes and checklists from a .trellis directory to discover and apply the correct coding standards for your package modifications.

Do I need a .trellis directory to apply project-specific coding standards?▼

Yes, you need a .trellis directory to apply project-specific coding standards. Accessing this directory is required to parse spec indexes, shared guides, and pre-development checklists to inject the correct coding guidelines.

When should I review project standards using a pre-development checklist?▼

You should review project standards using a pre-development checklist when starting a new coding task, switching to a different package, or needing to refresh project conventions. This ensures all package modifications and new code implementations adhere to guidelines.

Can I use shared guides for consistent coding practices across different packages?▼

Yes, you can use shared guides for consistent coding practices across different packages. The Skill provides access to shared guides located in the project's .trellis directory to maintain uniform coding standards during new code implementation and package modifications.

What is the best way to reduce debugging time caused by inconsistent coding guidelines?▼

The best way to reduce debugging time from inconsistent coding guidelines is to inject project-specific standards before writing code. Parsing spec layers and shared guides ensures developers adhere to conventions, preventing code quality issues proactively.