analyze-component-structure

Extract Nuxt UI component specifications into structured JSON for xTweak UI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fodurrr/xTweak --skill analyze-component-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-component-structure
Source: https://github.com/fodurrr/xTweak/tree/main/.claude/skills/nuxt-ui-port/analyze-component-structure
Command: npx skills add https://github.com/fodurrr/xTweak --skill analyze-component-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual extraction of complete Nuxt UI component specifications is time-consuming and error-prone; this skill automates that process by using MCP tools to fetch structured metadata.

Core Features & Use Cases

  • Extracts props, slots, events, variants, examples, and dependencies from Nuxt UI components.
  • Outputs a ready-to-use JSON spec suitable for porting to xTweak UI.
  • Ideal for porting workflows when starting a new component or refreshing docs after Nuxt UI updates.

Quick Start

Analyze a Nuxt UI component by name to produce a complete JSON spec ready for porting to xTweak UI.

Frequently Asked Questions about analyze-component-structure

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

FAQPage Schema
How do I extract a complete Nuxt UI component specification for porting?

To extract a Nuxt UI component specification for porting, use this Skill to fetch metadata via MCP tools and generate a structured JSON including props, slots, events, variants, examples, and dependencies ready for xTweak UI.

What is included in a structured Nuxt UI component spec for porting to xTweak UI?

A structured Nuxt UI component spec for porting to xTweak UI includes complete metadata for props, slots, events, variants, examples, and dependencies, output as a ready-to-consume JSON data structure.

How do I automate fetching Nuxt UI component props, slots, and events metadata?

Automate fetching Nuxt UI component props, slots, and events metadata by using this Skill's MCP tools to analyze components by name, replacing time-consuming manual extraction with a structured JSON output.

Does this component analysis approach require manual configuration for each Nuxt UI component?

This component analysis approach does not require manual configuration for each Nuxt UI component; simply analyze the component by name to automatically produce the complete JSON specification on demand.

When should I use an automated component analyzer instead of manual extraction for Nuxt UI?

Use an automated component analyzer instead of manual extraction for Nuxt UI when porting workflows to xTweak UI or refreshing documentation after Nuxt UI updates, to avoid error-prone manual metadata collection.

Can I get a ready-to-use JSON spec from a Nuxt UI component for xTweak UI porting?

You can get a ready-to-use JSON spec from a Nuxt UI component for xTweak UI porting by analyzing the component name, which returns props, slots, events, variants, and examples as a structured data structure.