validate-component

What problem does it solve?

It prevents broken or non-compliant components from slipping into the codebase by validating linting, TypeScript correctness, type coverage, generated .d.ts output, and Storybook build health.

Core Features & Use Cases

• Run deterministic CI-like validation: executes the project's pnpm checks in a fixed order (lint → type-check → type-coverage → dts build → storybook build) and reports the first failing step.
• Strict failure surfacing: stops immediately on the first failure without attempting auto-fixes, and includes the last output lines to speed up debugging.
• Safety guardrails: never runs pnpm install, never mutates the working tree, and supports timeouts and missing-script detection to avoid hanging or unclear states.

Use case example: After scaffolding a new Vue component, run this validation to ensure it meets the project’s TypeScript thresholds (including type coverage) and that the added Storybook stories don’t break the documentation build.

Quick Start

Run the validate-component skill using the current component files written in this run to produce a pass/fail table and, if needed, the failing command output tail.