trellis-before-dev

Load and inject .trellis spec content before coding starts.

28|4|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/Hooolee/novel-splitter --skill trellis-before-dev-hooolee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/Hooolee/novel-splitter/tree/main/.agents/skills/trellis-before-dev
Command: npx skills add https://github.com/Hooolee/novel-splitter --skill trellis-before-dev-hooolee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Discover packages and their spec layers to identify applicable guidelines.
  • Identify which specs apply to the current task based on package scope (e.g., cli/, docs-site/).
  • Read the spec index for each relevant module to locate Pre-Development Checklists and guideline files.
  • Read the actual guideline files (e.g., error-handling.md, conventions.md, mock-strategies.md) referenced by the index.
  • Read shared guides from guides to align with overarching project standards.
  • Understand and apply coding standards before starting implementation.

Quick Start

Review the .trellis specs and read the pre-development checklists before starting any coding task.

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

To load project coding standards before development, discover and inject spec content from the .trellis/spec/ directory. This reads spec indexes, pre-development checklists, and shared thinking guides to align your implementation with project-wide conventions upfront.

What is a pre-development checklist for aligning with coding guidelines?

A pre-development checklist is a spec file within the .trellis directory that outlines required coding standards and conventions to review before implementation. It ensures developers reference shared guides and package-specific rules before writing any code.

When do I need to refresh project conventions and coding standards?

You need to refresh project conventions when starting a new coding task, switching to a different package like cli or docs-site, or needing to re-align with overarching project standards before implementation to ensure adherence to established guidelines.

How do I locate applicable specs when switching between packages?

To locate applicable specs when switching packages, discover the package layers within .trellis/spec/ and read the spec index for each relevant module. This identifies the correct pre-development checklists and guideline files for your current package scope.

Can I use this to read shared thinking guides for project-wide standards?

Yes, you can read shared thinking guides from the .trellis guides directory to align with overarching project standards. These guides are loaded alongside package-specific spec indexes and pre-development checklists before coding starts.

What types of guideline files can I reference from the spec index?

You can reference guideline files such as error-handling.md, conventions.md, and mock-strategies.md from the spec index. These files contain the actual coding standards and strategies referenced by the module's index before implementation.