integrate-skill

To integrate reusable skills into project documentation, you map an existing skill to target guideline docs and templates. This process standardizes development practices by embedding skill descriptions directly into your project guidelines rather than altering code.

Embedding a skill into development guidelines requires a SKILL.md file containing a defined name and description. This serves as the source input for the integration workflow to accurately map the skill into your documentation targets.

To standardize skill application across multiple projects, generate reusable templates and example placements during integration. This ensures consistent guideline updates and provides standardized artifacts like docs sections and code example templates for every project.

The best way to update project guidelines with new workflows is through an on-demand artifact generation process. This method creates documentation sections, code example templates, and index references while maintaining an integration report for tracking.

Yes, you can generate and maintain an integration report when updating documentation guidelines. The workflow automatically produces this report alongside updated guideline docs and example templates to track the integration of the skill.

You should not use documentation integration for skills when your goal is to directly modify or embed logic into your project's source code. This approach is specifically designed for mapping skills to documentation targets and templates rather than code execution.