componentize

Audit React/Tailwind codebases for duplicated UI patterns and plan shared component extraction.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/howells/skills --skill componentize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: componentize
Source: https://github.com/howells/skills/tree/main/componentize
Command: npx skills add https://github.com/howells/skills --skill componentize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces UI duplication in a codebase by locating repeated patterns and extracting canonical, reusable shared components instead of continuing to copy-and-tweak implementations across apps or packages.

Core Features & Use Cases

  • Reuse-first audits: inventories existing shared UI surfaces and highlights duplicated markup, repeated Tailwind class patterns, and drift-prone component variants.
  • Canonical component planning: selects extraction targets, defines component APIs (props/slots/variants), and recommends whether to reuse, adapt, extract, move, or keep code app-local.
  • Controlled migration guidance: provides a stepwise plan to migrate call sites and validate the result without broad redesign.

Quick Start

Use the componentize skill to audit the repository for duplicated UI, propose the highest-value shared components to extract, and outline a migration plan for updating call sites.

Frequently Asked Questions about componentize

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

FAQPage Schema
How do I find and extract duplicated React UI patterns into shared components?

To extract duplicated React UI patterns, audit the codebase for repeated Tailwind class combinations and markup, then define a canonical component API with clear props, slots, variants, and accessibility contracts before migrating call sites stepwise.

What is the best way to deduplicate Tailwind UI components across a Turborepo monorepo?

UI deduplication across a Turborepo monorepo requires identifying repeated Tailwind class patterns across apps and packages, establishing architecture boundaries, and extracting shared primitives or surfaces that can be safely imported without broad redesign.

Can I migrate shared React components across package boundaries without breaking existing call sites?

Migrating shared React components across package boundaries requires a stepwise plan that adapts existing code before extraction, updates call sites incrementally, and validates results through typecheck, lint, and relevant build or smoke tests.

When should I adapt an existing React component instead of extracting a new shared primitive?

Adapt existing React components before extracting new shared primitives when the duplicated UI pattern is a minor variation, because reuse-first decisioning prevents unnecessary API surface expansion and reduces drift-prone component variants in the codebase.

How do I audit a React codebase for missed UI component reuse opportunities?

Auditing a React codebase for missed reuse opportunities involves inventorying existing shared UI surfaces, locating repeated markup and Tailwind class patterns, and resolving visible UI targets to their source to recommend whether to reuse, adapt, extract, move, or keep code app-local.