generate-port-diff

Compare Nuxt UI component specs with xTweak implementations to detect missing features.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compare Nuxt UI component specs with xTweak implementations to detect missing features and ensure parity during porting.

Core Features & Use Cases

  • Gap analysis between Nuxt UI specs and xTweak code to identify missing props, slots, events, and variants.
  • Deterministic diff outputs in JSON, Markdown, or checklist formats for integration into workflows.
  • Port planning guidance by highlighting incomplete features and recommended next steps for porting.

Quick Start

Provide the component name and optional parameters to generate-port-diff to produce a structured diff for porting assessment.

Frequently Asked Questions about generate-port-diff

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

FAQPage Schema
How do I identify missing features when porting Nuxt UI components?

Perform a gap analysis by diffing Nuxt UI component specs against your target implementation to detect missing props, slots, events, and variants. This reveals feature gaps to ensure parity during porting.

Can I output component diff results in a checklist format for porting workflows?

Yes, component diff results can be output in JSON, Markdown, or checklist formats. These deterministic outputs integrate directly into porting workflows to track incomplete features and guide next steps.

What is the best way to prioritize missing props and slots during a UI port?

The best way to prioritize missing props and slots is to generate a structured diff that highlights incomplete features and provides recommended next steps. This guides porting efforts systematically toward full feature parity.

Does the gap analysis require a specific component name format?

Yes, the gap analysis requires the component name in PascalCase. You can also supply optional flags like --source-spec, --target-path, and --output-format to refine the diffing scope and output structure.

How do I compare Nuxt UI specs with an xTweak implementation automatically?

You can compare Nuxt UI specs with an xTweak implementation automatically by applying a diffing workflow across analysis and prioritization stages. This identifies exact gaps between spec and code to guide porting.