trellis-before-dev

Enforcing coding standards before development involves reading a spec index and following a pre-development checklist to inject project-specific guidelines. This ensures alignment with conventions before any implementation begins.

A pre-development checklist for coding conventions is a structured process that reads guideline files such as error-handling.md and conventions.md to aggregate project-specific rules. It reduces misalignment by ensuring developers follow vetted standards.

Applying project-specific guidelines when switching packages requires reading the spec index for the new relevant package and consulting shared guides. This refreshes your alignment with the active package's coding standards and conventions.

Yes, a spec directory structured as .trellis/spec/ is required to store project-specific guidelines. The pre-development process reads files from this directory to inject conventions and shared thinking resources into your workflow.

Before implementation, you should read guideline files such as error-handling.md, conventions.md, and mock-strategies.md. Consulting the shared guides index at .trellis/spec/guides/index.md ensures full coverage of project standards.