before-dev

Returns JSON containing title, URL, and summary for each item.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/alleneee/topsport-agent --skill before-dev-alleneee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: before-dev
Source: https://github.com/alleneee/topsport-agent/tree/main/.agents/skills/before-dev
Command: npx skills add https://github.com/alleneee/topsport-agent --skill before-dev-alleneee

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

  • Discover and read guidelines from the .trellis/spec repository to align new work with project standards.
  • Identify and apply relevant pre-development checklists and shared thinking guides to the current task.
  • Inject guidelines into the task context to ensure consistent practices across packages and projects.

Quick Start

Consult the Pre-Development Checklist in the relevant spec index and apply the listed guidelines before starting implementation.

Frequently Asked Questions about before-dev

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

FAQPage Schema
How do I enforce coding guidelines before starting development on a new package?

To incorporate project guidelines before coding, this Skill discovers and injects project-specific standards from the .trellis/spec/ directory into your task context. It reads spec indexes and pre-development checklists to align new work with conventions.

What is the best way to load project conventions and shared thinking guides for a new coding task?

The best way to load project conventions is by reading spec indexes, pre-development checklists, and shared thinking guides from the .trellis/spec/ repository. This injects relevant guidelines directly into your current task context.

When do I need to refresh project standards during software development?

You need to refresh project standards when starting a new coding task, before writing any code, or switching to a different package. This ensures you apply the most relevant pre-development checklists and shared guides to maintain consistency.

Does this approach require a specific directory structure to apply pre-development checklists?

Yes, applying pre-development checklists requires a .trellis/spec/ directory structure. The process discovers and reads project-specific coding guidelines, spec indexes, and shared guides from this repository to inject into the task context.

How do I keep coding practices consistent across multiple packages in a project?

To keep coding practices consistent across multiple packages, inject project-specific guidelines from the .trellis/spec/ directory into the task context. This enforces standards by applying shared thinking guides and pre-development checklists to each package.