trellis-before-dev

To enforce coding guidelines before development, you can use a context discovery tool to automatically inject project-specific checklists and standards from a local directory. This prevents architectural drift by aligning developers with mandatory conventions prior to writing code.

Applying package-specific coding standards to a new feature involves retrieving relevant architectural layers and error-handling patterns. This ensures consistency across the codebase by guiding developers through mandatory pre-development checklists tailored to that specific module.

Preventing technical debt and architectural drift requires ensuring developers align with project-specific coding guidelines and checklists before writing any code. Automated context discovery helps retrieve exact mock strategies and shared conventions mandatory for the package.

Yes, local file system access is required to retrieve project-specific development checklists. The process executes Python-based context discovery scripts to read Markdown-based specification files directly from the local .trellis directory structure.

Yes, you can use Python scripts to discover architectural layers and coding conventions. The discovery process automatically identifies relevant package specifications and injects shared conventions by reading local Markdown specification files.

Pre-development checklists for coding standards might not be necessary for standalone scripts or projects without shared conventions. This approach is designed for software workflows where adherence to package-specific standards and architectural layers is strictly mandatory.