trellis-before-dev

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

Inject project coding guidelines from .trellis/spec into task context.

52|7|Updated Apr 29, 2026

Search Tags:#conventions #guidelines #coding-standards #pre-development #development-workflow #trellis #spec-index

Ready to run

npx skills add https://github.com/RebornQ/fl_api_hub --skill trellis-before-dev-rebornq

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure coding guidelines and project conventions from the Trellis specification are loaded and applied before starting work, reducing drift and misalignment.

Core Features & Use Cases

Guideline discovery: reads .trellis/spec indexes and pre-development checklists to surface relevant standards for the target package.
Context injection: injects the applicable guidelines into the task context so developers follow approved conventions.
Cross-package refresh: supports starting work on a new package or switching packages to refresh project standards.

Quick Start

Run this skill before starting a task to load the current guidelines from .trellis/spec for the target package.

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 a new development task?▼

You can refresh project conventions by running the pre-development workflow skill when switching packages. This action re-reads the .trellis/spec indexes and updates your task context with the target package's specific coding standards and checklists.

What are pre-development checklists and how do they enforce coding standards?▼

Injecting coding guidelines into task context prevents convention drift by surfacing relevant standards before you write any code. This ensures developers immediately follow approved project-specific conventions, reducing misalignment across the development workflow.

Do I need a .trellis/spec repository to apply pre-development coding conventions?▼

Yes, this approach supports cross-package development workflows by allowing you to run the skill when switching packages. This refreshes the spec indexes and injects the correct package-specific guidelines into your new task context.

What is the best way to ensure developers follow project conventions across different packages?▼

Without a spec repository, the skill cannot discover or inject project-specific guidelines. You must manually define and communicate your coding standards, which increases the risk of convention drift and misalignment during development.