trellis-before-dev

To enforce project coding standards before development begins, you can discover and load repository-specific guidelines from the .trellis spec indexes. This applies pre-development checklists to your target package, injecting consistent conventions into your task context prior to coding.

Pre-development checklists are shared thinking guides that verify alignment with package type and enforce standard development patterns. You need them when starting a new task to ensure every implementation begins with a clear, shared set of project conventions from your spec indexes.

To load project-specific guidelines from .trellis spec indexes, run the context discovery process at the start of a new task. This automatically discovers and reads relevant spec layers and index files for the target package, pulling the guidelines into your active context.

Yes, the pre-development process works without external dependencies. It relies entirely on discovering and reading the existing .trellis spec indexes and guidelines within your own repository to verify alignment with your package type and apply standard development patterns.

Your team has inconsistent coding conventions across tasks because development starts without loading shared guidelines. Applying pre-development checklists and injecting repository .trellis guidelines into the task context before implementation ensures every task follows the same standard patterns.