trellis-before-dev

To enforce coding standards before development, you need a pre-development checklist that reads and aggregates project-specific guidelines. This process ensures teams understand and follow shared specs prior to writing any code.

A pre-development checklist for coding conventions is a process that discovers and injects project-specific guidelines from spec indexes before implementation begins. It forms a unified development brief to ensure consistency across packages.

To align coding tasks across frontend and backend, you reference shared guides and spec indexes tailored to the target package and work type. This ensures adherence to shared standards during implementation.

Yes, you need a spec index within your project to apply pre-development guidelines effectively. The system reads these spec indexes and shared thinking guides to identify applicable standards for your specific package.

You need to run a pre-development checklist before writing any code for a new task. It is required to load relevant specs and guides, ensuring that project-specific coding guidelines are understood prior to implementation.