trellis-spec-bootstarp

Bootstrap Trellis specification guidelines from a real codebase.

2|Updated May 22, 2026

Search Tags:#architecture #specification #codebase analysis #coding guidelines #trellis #repository documentation

Ready to run

npx skills add https://github.com/lihaoze123/educoder-cli --skill trellis-spec-bootstarp-lihaoze123

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-spec-bootstarp
Source: https://github.com/lihaoze123/educoder-cli/tree/main/.agents/skills/trellis-spec-bootstarp
Command: npx skills add https://github.com/lihaoze123/educoder-cli --skill trellis-spec-bootstarp-lihaoze123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns an unfamiliar or evolving codebase into accurate, maintainable Trellis specification guidelines instead of leaving agents with generic templates or placeholder documentation.

Core Features & Use Cases

Repository Analysis: Inspect project structure, packages, source files, tests, and architecture relationships before writing specifications.
Spec Decomposition: Organize guidance by real package, layer, or cross-cutting ownership boundaries.
Evidence-Based Writing: Create practical rules with source references, implementation patterns, anti-patterns, and verification steps.
Use Case: Use it when initializing or refreshing a project’s .trellis/spec directory so future coding agents can follow conventions grounded in the repository’s actual implementation.

Quick Start

Use the trellis-spec-bootstarp skill to analyze this repository and create or refresh its codebase-backed Trellis specifications.

Frequently Asked Questions about trellis-spec-bootstarp

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

FAQPage Schema

How do I generate codebase-backed Trellis specifications from an existing repository?▼

To generate codebase-backed Trellis specifications, inspect the repository structure, packages, and source files to create evidence-based guidelines with implementation patterns. This produces accurate .trellis/spec documentation grounded in your actual architecture.

What are coding guidelines in Trellis spec documentation?▼

Trellis spec documentation provides coding guidelines organized by real package, layer, or cross-cutting ownership boundaries. It includes source-backed conventions, anti-patterns, and verification steps to help coding agents follow repository-specific implementation patterns.

Can I refresh .trellis/spec directories across multiple packages and layers?▼

Yes, you can refresh .trellis/spec directories across multiple packages, layers, CLI workflows, and shared architecture boundaries. It decomposes guidance by real ownership boundaries and verifies that placeholder content is removed.

How do I remove placeholder content when initializing architecture specifications?▼

To remove placeholder content when initializing architecture specifications, inspect the codebase source files and replace generic templates with source-backed conventions. Verification ensures template-only documentation is eliminated from the spec indexes.

What is the best way to document repository architecture boundaries for coding agents?▼

The best way to document repository architecture boundaries is through codebase analysis that maps source files and tests into coherent spec indexes. This creates practical rules grounded in the repository's actual implementation rather than generic templates.