trellis-before-dev

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

1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/sperictao/one-publish --skill trellis-before-dev-sperictao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/sperictao/one-publish/tree/main/.cursor/skills/trellis-before-dev
Command: npx skills add https://github.com/sperictao/one-publish --skill trellis-before-dev-sperictao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams align with project-specific coding guidelines before implementation, preventing misalignment and rework by surfacing standards and checklists upfront.

Core Features & Use Cases

  • Discover and load relevant guidelines from .trellis/spec indexes
  • Read pre-development checklists and design notes to establish scope and plan
  • Enforce conventions across packages before coding begins
  • Use Case: Start a new task in a repository, switch to a different package, or refresh conventions to align with current standards

Quick Start

Review current artifacts (prd.md, design.md, implement.md) and load the applicable Trellis guidelines before you begin coding.

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 standards before starting development?

Enforce coding standards by discovering and injecting project-specific guidelines from the .trellis/spec structure before implementation begins, preventing misalignment and rework by surfacing checklists upfront.

What are pre-development checklists and when do I need them?

Pre-development checklists ensure coding standards are met before starting a new task, switching packages, or refreshing conventions, establishing scope and aligning with current project standards upfront.

How do I load project-specific coding guidelines from spec indexes?

Load project-specific coding guidelines by reading task artifacts like prd.md and design.md, then loading applicable Trellis guidelines from spec indexes before you begin coding.

Can I use this to align with conventions when switching packages?

Yes, you can align with conventions when switching to a different package or starting a new task in a repository, enforcing standards across packages before coding begins.

What's the best way to prevent misalignment with project guidelines during implementation?

Prevent misalignment by reviewing current artifacts and loading applicable Trellis guidelines before coding, enforcing conventions across the repository and following the Pre-Development Checklist.

Do I need to review task artifacts before loading coding guidelines?

Yes, review task artifacts such as prd.md, design.md, and implement.md to establish scope and plan before loading the applicable Trellis guidelines for your coding task.