trellis-before-dev

To load project-specific coding guidelines before development work, you can use a pre-development workflow skill that reads repository specification indexes and shared guidance documents to surface package conventions and coding standards.

A pre-development workflow in software engineering is the process of discovering and reviewing repository-specific rules before writing code. You need it when starting a feature or switching packages to prevent convention violations.

You find package-specific conventions and repository standards by identifying applicable project specification layers and reading shared guides, checklists, and relevant conventions to align implementation with repository expectations.

Yes, reading specification indexes is required to satisfy pre-development workflow requirements, ensuring you gather the necessary engineering standards and package-specific rules before making any code changes.

The best way to prevent mistakes from missing project conventions is to discover and review coding guidelines before implementation begins, ensuring all repository standards and package-specific rules are loaded beforehand.

Yes, this pre-development workflow skill operates without external dependencies, relying solely on reading existing specification indexes and shared guidance documents within your repository to gather coding standards.