component-identification-sizing

Identify architectural components and quantify their size using statement counts.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/rodrigotoledo/trading-exchange --skill component-identification-sizing-rodrigotoledo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-identification-sizing
Source: https://github.com/rodrigotoledo/trading-exchange/tree/main/packages/skills-catalog/skills/%28architecture%29/component-identification-sizing
Command: npx skills add https://github.com/rodrigotoledo/trading-exchange --skill component-identification-sizing-rodrigotoledo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify the architectural components in a codebase and measure their size to guide decomposition decisions, enabling safer and more efficient refactoring planning.

Core Features & Use Cases

  • Detect leaf-node components in directory/namespace structures and generate a precise component inventory.
  • Compute size metrics using statements (not lines) and provide mean, standard deviation, and percentage of codebase.
  • Produce practical recommendations for splitting oversized components and consolidating undersized ones, with artifact outputs for migration planning.

Quick Start

Identify and size all components in your codebase.

Frequently Asked Questions about component-identification-sizing

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

FAQPage Schema
How do I identify architectural components in a large codebase for refactoring?

Identify architectural components by detecting leaf-node directories or namespaces to generate a precise inventory. This skill maps your codebase structure, enabling safer refactoring planning by highlighting logical boundaries for extraction or consolidation.

What is the best way to measure component size for decomposition decisions?

Measure component size by counting statements rather than lines of code. This approach computes the mean, standard deviation, and percentage of the total codebase, providing practical recommendations for splitting oversized components and consolidating undersized ones.

Can I use this component sizing approach for a monorepo with multiple large applications?

Yes, this component sizing approach is designed for monorepos or large apps. It detects oversized components, plans extractions, and generates a component inventory with artifact outputs to guide your migration planning across complex directory structures.

How does counting statements instead of lines of code improve decomposition planning?

Counting statements instead of lines provides a more accurate density metric for decomposition planning. It calculates the percentage of the codebase per component and uses standard deviation to pinpoint oversized components that need splitting.

What do I need to generate a component inventory and plan extractions?

You need a codebase with a directory or namespace structure. The skill detects leaf-node components, quantifies their size, and produces artifact outputs with recommended splits to guide your migration and extraction planning.