trellis-before-dev

To ensure coding compliance before development, you can use a pre-development workflow skill that discovers and injects project-specific conventions, error-handling patterns, and mock strategies from a designated directory. This enforces standards prior to implementation.

A pre-development checklist for software engineering standards is a mandatory review process of spec indexes and shared thinking guides. It prevents technical debt by aligning coding tasks with established conventions before any implementation begins.

To apply project-specific error-handling and mock strategies to a new feature, run a context discovery process that retrieves relevant package specifications and layers. This guides the developer through mandatory coding guides for the specific package.

You need a .trellis directory containing project-specific coding guidelines to enforce coding standards in your workflow. The skill automatically discovers and reads these specifications to inject conventions before implementation begins.

You should run a pre-development compliance check for software engineering before starting any new feature or coding task. It ensures alignment with package specifications and prevents development errors by reviewing shared coding guides beforehand.