trellis-before-dev

To enforce coding conventions before development, you can parse project-specific spec layers and guides from a .trellis directory. This injects relevant guidelines directly into your workflow, ensuring coding standards are met before any code is written.

Pre-development guidelines are project-specific coding standards applied before writing new code. Spec layers analysis works by reading spec indexes and checklists from a .trellis directory to discover and apply the correct coding standards for your package modifications.

Yes, you need a .trellis directory to apply project-specific coding standards. Accessing this directory is required to parse spec indexes, shared guides, and pre-development checklists to inject the correct coding guidelines.

You should review project standards using a pre-development checklist when starting a new coding task, switching to a different package, or needing to refresh project conventions. This ensures all package modifications and new code implementations adhere to guidelines.

Yes, you can use shared guides for consistent coding practices across different packages. The Skill provides access to shared guides located in the project's .trellis directory to maintain uniform coding standards during new code implementation and package modifications.

The best way to reduce debugging time from inconsistent coding guidelines is to inject project-specific standards before writing code. Parsing spec layers and shared guides ensures developers adhere to conventions, preventing code quality issues proactively.