trellis-before-dev

To load coding guidelines before implementation, read task artifacts, resolve relevant package spec layers, and follow shared guide indexes to align code changes with repository standards in .trellis-managed repositories.

Spec discovery is the process of identifying the relevant package and spec layers for software work before coding starts, preventing implementation drift by surfacing project-specific conventions, checklists, and shared guidance.

Yes, you can use this to review conventions for frontend refactoring and test updates, as it applies across backend, frontend, testing, and documentation tasks to ensure coding follows repository standards.

To resolve package spec layers when starting a new package, read task artifacts and follow the shared guide indexes within .trellis-managed repositories to align your code with repository standards.

Implementation drift happens when coding begins without surfacing the right project-specific conventions, checklists, and shared guidance, causing code changes to misalign with established repository standards.

Yes, you need a .trellis-managed repository, because the skill resolves relevant package spec layers and follows shared guide indexes specifically within .trellis-managed environments to load conventions.