skills.rest
RamonsDka
RamonsDkaCOMMUNITY
Explore all skills by this author →
GitHub

component-identification-sizing

Identify architectural components and calculate size metrics from codebase structures.

1|1|Updated Apr 19, 2026
Search Tags:#architecture-patterns#codebase-analysis#standard-deviation#monolith-decomposition#identify-components#component-sizing
One-click install
npx skills add https://github.com/RamonsDka/the-architect-overlay --skill component-identification-sizing-ramonsdka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: component-identification-sizing
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/component-identification-sizing
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill component-identification-sizing-ramonsdka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify architectural components in a codebase and measure their size to support effective decomposition planning and governance.

Core Features & Use Cases

  • Identify leaf-node components from directory/namespace structures
  • Calculate size metrics (statements, files, percent) and derive mean and standard deviation
  • Flag oversized and undersized components and generate a component inventory with recommendations
  • Support monolith decomposition planning and architectural governance across languages and frameworks

Quick Start

Identify all components and their sizes 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 components and calculate size metrics for a monolithic codebase?▼

To identify components and calculate size metrics for a monolithic codebase, this skill analyzes directory or package structures to isolate leaf-node components and computes statement, file, and percent distributions, generating an actionable inventory for decomposition planning.

What is the best way to measure component sizing for architecture reviews?▼

Measuring component sizing for architecture reviews is done by calculating statements, files, and percentages per component, then deriving the mean and standard deviation to flag oversized or undersized elements for governance recommendations.

Does component identification work with codebases across different programming languages?▼

Yes, component identification works across different programming languages and frameworks, provided the codebase maintains a clear directory or namespace structure to analyze for architectural governance and decomposition planning.

How do I flag oversized components when planning a monolith decomposition?▼

To flag oversized components during monolith decomposition, the skill calculates size metrics for each component and compares them against the mean and standard deviation, highlighting outliers that require splitting or refactoring.

What codebase structure is required to perform a component size analysis?▼

Performing a component size analysis requires a codebase with a clear directory or package structure, allowing the tool to accurately identify leaf-node components and calculate architectural metrics.

Related Skills

Explore More Software Engineering Skills→
agentjidoagentjido
48

builder-package-review

Analyze package architecture boundaries, dependencies, and documentation gaps.

Official
Advanced
rafael-hcrafael-hc

component-identification-sizing

Map architectural components and measure size using executable statements and file counts.

Community
Intermediate
opensage-agentopensage-agent
113

get-caller

Identify direct and indirect callers of functions using Neo4j callgraph data.

Official
Intermediate
Gabrielloopes33Gabrielloopes33

component-identification-sizing

Identify architectural components and calculate size metrics for decomposition planning.

Community
Intermediate