Integrate Claude Skill into Project Guidelines

To integrate development guidelines without changing source code, this skill transforms external concepts into structured documentation sections within docs/specs directories, routing content by category like frontend or backend, and saving code examples using a .template suffix to prevent IDE errors.

Adding a frontend skill to your specs index involves mapping the skill category to target paths like docs/specs/frontend, writing an @@section:skill-<skill-name> block into doc.md, and updating the specs index.md file to register the new guidelines.

Documenting backend best practices from an external skill is best handled by converting the skill's patterns into a structured section inside docs/specs/backend documentation, optionally organizing available code snippets into an examples directory using .template suffixes.

Integrating an external skill does not create implementation code in your project. It performs a guideline-first integration that converts concepts and patterns into structured documentation, while saving any code examples as .template files to avoid polluting source code.

You can automatically route skill documentation to different directories based on category. The integration process targets paths like docs/specs/frontend or docs/specs/backend by reading the skill content and mapping its category to the corresponding specs directory.

Example code files are saved with a .template suffix during skill integration to reduce IDE errors and prevent direct execution. This safety mechanism ensures external code snippets remain reference materials rather than active project source code.