integrate-skill

Integrating external skills into project guidelines requires parsing a SKILL.md definition, mapping it to a target spec directory, and updating documentation indexes with consistent templates and code samples to ensure standardized team adoption without modifying source code.

The .trellis spec directory is used to store standardized guideline documents, templates, and code examples for newly integrated skills. It separates frontend and backend targets to maintain organized project standards and reproducible adoption workflows.

You standardize external skill documentation by applying a consistent workflow that reads SKILL.md definitions and populates target spec directories. This ensures both frontend and backend teams follow unified project standards for templates and code examples.

Yes, a clear SKILL.md definition is required to add new skills to a spec index. This file dictates how the skill is documented, templated, and mapped to the correct target directory within your project guidelines.

Yes, you can update documentation indexes and quick-navigation entries without modifying source code. The integration process standardizes how new skills are templated and added to spec indexes, ensuring consistency without touching application logic.

The best way to structure code examples and templates for project standards is to place them under designated .trellis/spec/{target}/ directories. This ensures reproducible adoption and aligns with the skill's defined SKILL.md structure.