trellis-before-dev

Name: trellis-before-dev
Availability: InStock
Author: tecnb

Read .trellis spec indexes and checklists before coding.

2|Updated Apr 8, 2026

Search Tags:#development #checklist #spec #guidelines #coding-standards #trellis #shared-guides

Ready to run

npx skills add https://github.com/TECNB/MediaNexus --skill trellis-before-dev-tecnb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/TECNB/MediaNexus/tree/main/.agents/skills/trellis-before-dev
Command: npx skills add https://github.com/TECNB/MediaNexus --skill trellis-before-dev-tecnb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates and communicates project-specific coding guidelines from .trellis/spec/ before you begin work, helping teams align on conventions and reduce rework.

Core Features & Use Cases

Discover packages and their spec layers using the trellis tooling (e.g., ./.trellis/scripts/get_context.py --mode packages).
Identify which specs apply to your task based on the target package and work type.
Read the spec index for relevant modules and then the actual guideline files (e.g., error-handling.md, conventions.md, mock-strategies.md).
Read shared guides to ensure alignment with broader project conventions.

Quick Start

Load the relevant .trellis spec and shared guides for your target package, then follow the Pre-Development Checklist before coding.

Frequently Asked Questions about trellis-before-dev

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

FAQPage Schema

How do I review project coding guidelines before starting development?▼

To review coding guidelines before starting development, discover packages and spec layers using trellis tooling, read the spec index for your target module, and consult shared guides to align conventions before writing code.

What is the best way to prevent inconsistent coding practices across packages?▼

Preventing inconsistent coding practices involves surfacing .trellis guidelines before coding begins. You must identify applicable specs based on the target package and work type, ensuring error-handling and conventions are reviewed.

How do I find which spec layers apply to my target package?▼

To find applicable spec layers for your target package, use trellis tooling like get_context.py to discover packages and identify the relevant spec indexes and guideline files for your specific task.

Do I need to read shared guides for every new task across packages?▼

Reading shared guides is required for new tasks across packages to ensure alignment with broader project conventions. You must follow the Pre-Development Checklist before writing any code to guarantee compliance.

What specific guideline files should I check before coding?▼

Before coding, you should check specific guideline files like error-handling.md, conventions.md, and mock-strategies.md. You read the spec index for relevant modules first, then consult the actual guideline files.