trellis-before-dev

Loads project-specific coding guidelines from .trellis/spec before writing code.

2|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/42team-ru/teampilot --skill trellis-before-dev-42team-ru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-before-dev
Source: https://github.com/42team-ru/teampilot/tree/main/.cursor/skills/trellis-before-dev
Command: npx skills add https://github.com/42team-ru/teampilot --skill trellis-before-dev-42team-ru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers and AI agents often start coding without reviewing project-specific conventions, leading to inconsistent patterns, rejected reviews, and rework. This Skill enforces a mandatory pre-development step that discovers and injects the relevant coding guidelines from the .trellis/spec directory before any implementation begins. ## Core Features & Use Cases - Spec Discovery: Runs get_context.py to list packages and their spec layers, then identifies which specs apply based on the target package and work type (backend, frontend, tests, docs). - Pre-Development Checklists: Reads each relevant spec index and follows its Pre-Development Checklist to locate concrete guideline files such as error-handling.md, conventions.md, and mock-strategies.md. - Shared Guides: Always loads the shared thinking guides at .trellis/spec/guides/index.md so cross-cutting standards are never missed. - Use Case: Before modifying the cli/ package, run this Skill to surface the package's backend conventions and error-handling rules, then write code that matches the project's established patterns on the first attempt. ## Quick Start Before writing any code for this task, use the trellis-before-dev skill to load the relevant project guidelines from .trellis/spec.

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 coding guidelines before writing code?

Run python3 ./.trellis/scripts/get_context.py --mode packages to discover packages and spec layers, then read the relevant spec index files under .trellis/spec/<package>/<layer>/index.md and follow their Pre-Development Checklists to the concrete guideline files.

What is the .trellis/spec directory structure?

The .trellis/spec directory organizes guidelines by package (e.g., cli/, docs-site/) and layer (backend, frontend, unit-test, docs). Each layer has an index.md pointing to specific guideline files, plus a shared guides/index.md for cross-cutting standards.

When should I run the pre-development checklist?

Run it before writing any code for a new task, when switching to a different package, or when you need to refresh project conventions. The step is mandatory before implementation begins.

Does this skill work without the get_context.py script?

No, package discovery depends on .trellis/scripts/get_context.py being present in the repository. Without it, you would need to manually browse the .trellis/spec directory tree to find applicable indexes.

What are the limitations of spec index files?

An index file is only a pointer, not the guideline itself. You must follow its Pre-Development Checklist to the actual files like error-handling.md or conventions.md to understand the real coding standards.