components

Document Svelte component APIs with YAML frontmatter and Markdown.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/gzp79/shine-web-v2 --skill components-gzp79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: components
Source: https://github.com/gzp79/shine-web-v2/tree/main/.claude/skills/svelte-component
Command: npx skills add https://github.com/gzp79/shine-web-v2 --skill components-gzp79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reference for Svelte component APIs in this project to speed UI development and ensure correct usage.

Core Features & Use Cases

  • Provides a centralized guide to common components like Stack, Box, Card, Separator, Typography, and Input, with prop patterns and examples.
  • Supports consistent UI implementation across the codebase and accelerates onboarding for new developers.
  • Use cases include learning component props, verifying usage before writing new components, and solving UI consistency questions quickly.

Quick Start

Open the UI Component Reference to review Stack and Box props before building a new component.

Frequently Asked Questions about components

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

FAQPage Schema
How do I check Svelte UI component props before building a new layout?

Use a Svelte UI component reference guide to verify prop usage and patterns for Stack and Box components. It provides detailed API documentation in Markdown with YAML frontmatter to ensure correct UI implementation.

What is the best way to maintain UI consistency across a Svelte project?

Maintain UI consistency by referencing a shared guide for Svelte UI components like Card, Separator, and Typography. It enforces consistent usage patterns and accelerates onboarding for new developers across the codebase.

Does this Svelte component reference cover typography and input components?

Yes, this Svelte component reference covers Typography and Input components alongside Stack, Box, Card, and Separator. It provides centralized API documentation to support consistent UI implementation and solve component usage questions quickly.

How do I document Svelte component APIs for faster developer onboarding?

Document Svelte component APIs using YAML frontmatter with name and description, followed by detailed Markdown body content. This reference structure provides prop patterns and examples to accelerate onboarding for new developers.

What are the limitations of using a basic Svelte component reference guide?

A basic Svelte component reference guide provides quick API lookups for common components like Stack, Box, and Card but does not cover advanced component design or complex frontend development patterns beyond the documented set.