trellis-before-dev

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

Inject project-specific coding guidelines from .trellis/spec before implementation.

371|93|Updated Jan 22, 2026

Search Tags:#spec #guidelines #coding-standards #workflows #pre-development #context-injection #trellis

Ready to run

npx skills add https://github.com/Xeron2000/openOii --skill trellis-before-dev-xeron2000

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/Xeron2000/openOii/tree/main/.pi/skills/trellis-before-dev
Command: npx skills add https://github.com/Xeron2000/openOii --skill trellis-before-dev-xeron2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover and inject project-specific coding guidelines from .trellis/spec before implementation begins, ensuring consistent standards across tasks.

Core Features & Use Cases

Discover packages and their spec layers using the provided context tool.
Identify relevant specs based on the target package and task type (backend, frontend, docs, tests).
Read the spec index and individual guideline files, then apply shared guides to your workflow.

Quick Start

Run the pre-development context discovery to inject Trellis guidelines into your task context.

Frequently Asked Questions about trellis-before-dev

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

FAQPage Schema

How do I inject project-specific coding guidelines before implementation begins?▼

To inject coding guidelines before implementation, this Skill discovers and reads project-specific standards from the .trellis/spec directory, reading the index and guideline files like error-handling.md to establish context before you start coding.

What is the best way to apply coding standards across different packages?▼

Applying coding standards across packages is handled by discovering relevant spec layers based on the target package and task type, then consulting shared guides and the Pre-Development Checklist to ensure consistent conventions.

When do I need to refresh project conventions during development?▼

You need to refresh project conventions when switching packages or starting new coding tasks, ensuring that the correct backend, frontend, docs, or tests guidelines are injected into your current workflow context.

How does pre-development context discovery work for new coding tasks?▼

Pre-development context discovery works by identifying the target package and task type, reading the spec index and individual guideline files, and applying those shared guides to establish coding standards before implementation begins.

Do I need a .trellis/spec directory to use pre-development context injection?▼

Yes, a .trellis/spec directory is required because the Skill reads the Pre-Development Checklist, index, and individual guideline files such as conventions.md from that location to inject the correct standards.

Can I use this for frontend and backend coding standards separately?▼

Yes, you can use this for frontend and backend standards separately because it identifies relevant specs based on the target package and task type, applying the correct guidelines to your specific workflow.