before-dev

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

3.9k|339|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/zhukunpenglinyutong/desktop-cc-gui --skill before-dev-zhukunpenglinyutong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: before-dev
Source: https://github.com/zhukunpenglinyutong/desktop-cc-gui/tree/main/.agents/skills/before-dev
Command: npx skills add https://github.com/zhukunpenglinyutong/desktop-cc-gui --skill before-dev-zhukunpenglinyutong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.

Core Features & Use Cases

  • Discovers and injects guidelines from .trellis/spec/
  • Reads the spec index for relevant modules
  • Applies pre-development checklists and shared guides to ensure consistency
  • Use Case: When starting a new coding task across packages to refresh conventions

Quick Start

Begin a new task by running the discovery flow to load and apply the relevant project guidelines.

Frequently Asked Questions about 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 task?

You load project-specific coding guidelines by running a discovery flow that reads the .trellis/spec/ indexes. This injects relevant pre-development checklists and shared thinking guides directly into your task context.

What are pre-development checklists and when do I need them?

Pre-development checklists are project-specific coding standards read from .trellis/spec/ directories. You need them when starting new coding tasks, switching packages, or refreshing project conventions to ensure consistency.

How do I apply project standards when switching to a different package?

To apply project standards when switching packages, run the discovery flow to read spec indexes for the target package. This automatically aligns your new task work with existing shared thinking guides and conventions.

Does this coding standards discovery work without external dependencies?

Yes, the coding standards discovery works without external dependencies. It relies entirely on reading the existing .trellis/spec/ directory structure within your repository to extract project conventions.

What's the best way to refresh coding conventions across different packages?

The best way to refresh coding conventions is executing the discovery flow before writing any code. It reads spec indexes and pre-development guides for the target package, ensuring all subsequent implementation aligns with current standards.