integrate-skill

Integrate named Claude skills into project-specific guideline documents.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/LinXueyuanStdio/viben --skill integrate-skill-linxueyuanstdio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integrate-skill
Source: https://github.com/LinXueyuanStdio/viben/tree/main/packages/core/templates/kiro/skills/integrate-skill
Command: npx skills add https://github.com/LinXueyuanStdio/viben --skill integrate-skill-linxueyuanstdio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning an existing Claude skill into consistent, project-specific development guidelines without accidentally generating or modifying application code directly.

Core Features & Use Cases

  • Guideline-first integration: Integrates a skill by updating docs/specs/{target}/doc.md with a dedicated section for the target (frontend or backend).
  • Best-practice extraction: Converts a skill’s core concepts, recommended patterns, caveats, and usage steps into actionable documentation for your team.
  • Optional code examples workflow: When the skill includes code patterns, creates example files under docs/specs/{target}/examples/skills/<skill-name>/ using .template suffix to avoid IDE errors.

Quick Start

Tell the AI to integrate a specific skill into your project guidelines by running the command: /viben:integrate-skill frontend-design

Frequently Asked Questions about integrate-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate Claude skills into project development guidelines?

To integrate Claude skills into project development guidelines, this skill reads target skill content, maps it to docs/specs/{target}/, and writes a dedicated @@/section:skill-<name> block into your documentation without generating application code.

What is the best way to convert a skill into team documentation?

The best way to convert a skill into team documentation is extracting its core concepts, recommended patterns, and caveats into actionable guideline files. This skill formats them into a new section within your project specs.

Can I use template files for skill code patterns without triggering IDE errors?

Yes, you can use template files for skill code patterns without triggering IDE errors. This skill creates example files under docs/specs/{target}/examples/skills/ using a .template suffix to prevent compilation.

Does guideline integration work for both frontend and backend specs?

Yes, guideline integration works for both frontend and backend specs. The process applies to onboarding, consistency improvements, and repeatable engineering workflows across frontend, backend, and related documentation areas.

Why does integrating a skill not directly modify my application code?

Integrating a skill does not directly modify application code because it is designed strictly for guideline-first integration. It updates project documentation and creates optional template examples to ensure consistent engineering workflows.