integrate-skill

Integrating external skills into project guidelines involves importing third-party patterns into your Trellis specs. The skill updates `.trellis/spec/{target}/doc.md` with a dedicated guide section and stores reusable code example templates under `.trellis/spec/{target}/examples/skills/`.

The best way to add external skill patterns to frontend development guidelines is by running the integration command with the target skill. It imports external best practices directly into your project-specific documentation and generates matching template files for your workflow.

When adapting external skill workflows, code example templates are stored under `.trellis/spec/{target}/examples/skills/<skill-name>/`. The files use the `.template` suffix to prevent IDE issues while keeping the integrated patterns accessible for reuse.

Yes, integrating a new skill updates the spec index navigation. The process inserts new entries into `.trellis/spec/{target}/index.md` so the integrated third-party skill becomes discoverable within your existing documentation workflow.

Yes, you can use this to incorporate skill best practices into backend documentation workflows. It adapts third-party skill workflows into project-specific conventions for frontend, backend, or documentation targets without losing the original guideline structure.

Template files are saved with a `.template` suffix in Trellis specs to avoid IDE issues. This prevents the IDE from indexing or validating raw example templates as actual source code, while keeping the external skill patterns available for reference.