before-dev

To apply project-specific coding guidelines, read the .trellis/spec index and guideline files for your target package before writing any code. You must run the repository helper script to enumerate packages and determine the applicable spec layers for your development workflow.

Pre-development specs are project-specific coding guidelines stored under .trellis/spec. You need them when starting a new feature, switching to a different package, or preparing to write tests and documentation to prevent rework and maintain consistency with existing standards.

To enforce a pre-development checklist, read the spec index and specific guideline documents referenced by the checklist for your target package. This ensures compliance with repository-wide guides, common patterns, and package-specific conventions before any coding begins.

Yes, the spec discovery process works with multi-package repositories by running a repository helper script to enumerate packages and determine applicable layers. It directs developers to the correct .trellis/spec index and guideline files for the specific package being modified.

You should read .trellis spec files before switching packages because new tasks or context switches can lead developers to unknowingly violate project conventions. Reading the spec indexes and guideline files ensures your work starts aligned with existing repository-specific patterns.

The primary limitation is that this process only works if the repository contains a .trellis/spec directory with valid index and guideline files. It relies on existing documentation and a helper script to enumerate packages, meaning undocumented conventions will not be discovered.