trellis-before-dev

To load project-specific coding guidelines before starting development, this Skill reads the .trellis/spec repository, identifying package-specific spec layers, pre-development checklists, and shared thinking guides to inject into your context. It ensures consistent standards by applying relevant guidelines based on the target package and work type.

Pre-development checklists are module-specific guidelines stored in the .trellis/spec repository that you should use before starting new coding tasks, switching packages, or refreshing project conventions. They ensure consistent standards by applying relevant guidelines based on the target package and work type.

To apply backend or frontend coding standards to a specific package, the Skill identifies applicable specs from the .trellis/spec directory based on the target package and work type. It then loads these guidelines, along with shared thinking guides, into your context to ensure consistent standards.

Yes, you need a .trellis/spec directory containing spec indexes, pre-development checklists, and shared thinking guides to ingest coding guidelines. The Skill locates and loads these project-specific guidelines from that repository to inject them into your context before implementation.

The best way to ensure consistent coding standards across different packages is to ingest project-specific guidelines from the .trellis/spec repository before switching packages. The Skill discovers applicable specs, reads the guides index, and loads overarching standards into your context.

Your code might violate project conventions because guidelines were not loaded into context before implementation. This Skill prevents misalignment by reading the .trellis/spec indexes, pre-development checklists, and shared thinking guides to inject project-specific guidelines before you start coding.