trellis-before-dev

Discover and inject project-specific coding guidelines from the .trellis directory.

Updated Apr 30, 2026

Search Tags:#development #architecture #checklist #standards #coding #guidelines

Ready to run

npx skills add https://github.com/znc15/Open-Design --skill trellis-before-dev-znc15

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/znc15/Open-Design/tree/main/.cursor/skills/trellis-before-dev
Command: npx skills add https://github.com/znc15/Open-Design --skill trellis-before-dev-znc15

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents technical debt and architectural drift by ensuring developers align with project-specific coding guidelines and checklists before writing any code.

Core Features & Use Cases

Context Discovery: Automatically identifies relevant package specifications and architectural layers.
Standard Enforcement: Guides the developer through mandatory pre-development checklists and shared coding conventions.
Use Case: When starting a new feature in a specific package, use this Skill to retrieve the exact error-handling patterns and mock strategies required for that module, ensuring consistency across the codebase.

Quick Start

Use the trellis-before-dev skill to discover and read the required development guidelines for the current package before you start your coding task.

Frequently Asked Questions about trellis-before-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce coding guidelines before starting development?▼

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.

What is the best way to apply package-specific coding standards to a new feature?▼

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.

How do I prevent technical debt and architectural drift in a software project?▼

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.

Do I need local file system access to retrieve project-specific development checklists?▼

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.

Can I use Python scripts to discover architectural layers and coding conventions?▼

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.

When should I not use pre-development checklists for coding standards?▼

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.