document-feature

Generate VitePress feature documentation with correct directory placement and sidebar ordering.

9|2|Updated Nov 29, 2024
One-click install
npx skills add https://github.com/bbvch-ai/aihub-core --skill document-feature-bbvch-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-feature
Source: https://github.com/bbvch-ai/aihub-core/tree/main/.claude/skills/document-feature
Command: npx skills add https://github.com/bbvch-ai/aihub-core --skill document-feature-bbvch-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating consistent, properly structured user-facing feature documentation for a VitePress docs site is slow, error-prone, and often fails to match existing doc standards, directory structure, and tone guidelines.

Core Features & Use Cases

  • Codebase Analysis: Automatically scans relevant packages (core, agent, api, pipeline, process, web) to understand feature functionality and user value.
  • Correct Doc Placement: Identifies the appropriate docs directory with the correct numeric prefix for sidebar ordering, following existing site structure.
  • Style Alignment: Matches generated docs to the tone, structure, and formatting conventions of existing feature docs like MCP, Memory, and Cost Control guides.
  • Use Case: When a new platform feature like a unified LLM gateway is added to the Swiss AI Hub stack, this skill generates matching user-facing docs in the correct location without manual formatting work.

Quick Start

Use the document-feature skill to create user-facing documentation for the new memory feature.

Frequently Asked Questions about document-feature

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

FAQPage Schema
How do I generate user-facing feature docs for a VitePress site?▼

You can automate VitePress feature docs generation by scanning your codebase for feature context and placing output in the correct directory with proper sidebar ordering and style alignment.

What is the best way to match new VitePress documentation to existing site conventions?▼

The best way to match new VitePress documentation to existing conventions is to analyze established feature docs to replicate their tone, structure, and formatting guidelines automatically.

How does codebase analysis work for automated docs generation?▼

Automated docs generation uses codebase analysis to scan relevant packages like core, agent, api, and web to understand feature functionality and user value before writing content.

Can I automatically place new feature docs in the correct VitePress sidebar order?▼

Yes, you can place new feature docs in the correct VitePress sidebar order by identifying the appropriate docs directory and applying the correct numeric prefix during generation.

Does automated VitePress docs generation require manual formatting afterwards?▼

No, automated VitePress docs generation does not require manual formatting afterwards because it aligns content with established doc style guidelines and directory structure automatically during creation.

When do I need to scan packages for technical writing context?▼

You need to scan packages for technical writing context when new platform or SDK features require documentation that matches existing site structure, tone, and formatting conventions.