trellis-before-dev

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

Load project-specific development guidelines before starting implementation work.

47|4|Updated Feb 4, 2026

Search Tags:#software engineering #development workflow #project conventions #pre-development #coding guidelines #repository standards

Ready to run

npx skills add https://github.com/hkslover/cs2-highlight-tool --skill trellis-before-dev-hkslover

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/hkslover/cs2-highlight-tool/tree/main/.agents/skills/trellis-before-dev
Command: npx skills add https://github.com/hkslover/cs2-highlight-tool --skill trellis-before-dev-hkslover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents development mistakes caused by missing project-specific conventions by ensuring coding guidelines are discovered and reviewed before implementation begins.

Core Features & Use Cases

Guideline Discovery: Identifies applicable project specification layers and package-specific rules before development work.
Standards Preparation: Reads shared guides, checklists, and relevant conventions to align implementation with repository expectations.
Use Case: When starting a feature or switching packages in a codebase, use this Skill to gather the required engineering standards before making changes.

Quick Start

Use the trellis-before-dev skill to load the relevant development guidelines for my current coding task before I write any code.

Frequently Asked Questions about trellis-before-dev

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

FAQPage Schema

How do I load project-specific coding guidelines before starting development work?▼

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.

What is a pre-development workflow for software engineering and when do I need it?▼

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.

How do I find package-specific conventions and repository standards before writing code?▼

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.

Do I need to read specification indexes to prepare for coding in a new package?▼

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.

What's the best way to prevent coding mistakes caused by missing project conventions?▼

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.

Can this development workflow skill work without any external dependencies?▼

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.