before-dev

To ensure code follows project coding guidelines, discover and inject project-specific specs into your context by reading the .trellis spec indexes and guideline files before implementation begins.

A pre-development checklist is a process to surface repository conventions before coding. You need it when starting a new coding task, switching to a different package, or refreshing conventions across repository modules.

To find applicable specs for a specific package in a monorepo, locate package-level spec layers and indexes, then invoke the repository helper to list packages for accurate spec selection and read the recommended guideline files.

Yes, spec discovery works with monorepo package structures by reading .trellis spec indexes and invoking a repository helper to list packages. This ensures accurate spec selection when switching between backend, frontend, tests, or docs work types.

The best way to align new feature implementation with team standards is running spec discovery to locate applicable .trellis guidance, then following pre-development checklists to ensure consistency across backend, frontend, tests, and docs work.