What problem does it solve? Teams need coding guidelines in .trellis/spec/ that reflect their actual repository, but template specs are full of placeholders and generic advice that mislead future agents and developers. ## Core Features & Use Cases - Repository-Backed Analysis: Inspects the real codebase using GitNexus code graphs, ABCoder AST parsing, and direct source reads before writing any rule. - Spec Decomposition and Writing: Splits spec work by package or layer only when the codebase justifies it, then writes concrete rules with real file paths, examples, and anti-patterns. - Placeholder-Free Verification: Runs a final pass to remove template boilerplate, fix index files, and confirm every claim is backed by source or tests. - Use Case: After adopting Trellis in a monorepo, run this Skill to analyze each package and produce .trellis/spec/ guidance that documents actual command handler patterns, error handling conventions, and test styles. ## Quick Start Analyze this repository and write project-specific Trellis spec files under .trellis/spec based on the real code patterns you find.
