trellis-before-dev

To align coding standards before development, you can run a pre-development discovery process that reads .trellis spec indexes and parses project-specific checklists to enforce conventions. This ensures consistent patterns across tasks by referencing shared guides before you write code.

A pre-development checklist for coding conventions is a structured set of project guidelines parsed before implementation begins. It works by reading spec indexes and shared guides to discover package-specific standards, ensuring developers apply consistent patterns when starting new tasks or switching packages.

Discover project-specific coding guidelines across a repository by reading .trellis spec indexes to identify packages and their spec layers. This process parses pre-development checklists and references shared guides to refresh conventions and align development with established standards mid-project.

You need pre-development context discovery when starting a new task, switching packages, or refreshing standards mid-project. It reads .trellis spec indexes and pre-development checklists to apply project-specific conventions, ensuring your implementation aligns with established coding patterns before coding begins.

Yes, you can use .trellis spec indexes to enforce consistent coding patterns across different packages. The discovery process identifies package spec layers and parses shared guides, allowing developers to align with project-wide conventions before starting implementation in a new package.

Pre-development checklists for coding standards rely on reading .trellis spec indexes and shared guides, limiting their effectiveness to repositories with these files configured. If a repository lacks spec layers or pre-development checklists, the tool cannot discover or enforce project-specific conventions.