Component Identification Sizing
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning where to start decomposing. Do NOT use for runtime performance sizing or infrastructure capacity planning.
Install
/plugin marketplace add tech-leads-club/agent-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tech-leads-club/agent-skills --skill component-identification-sizinggit clone --depth 1 https://github.com/tech-leads-club/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/packages/skills-catalog/skills/(architecture)/component-identification-sizing ~/.claude/skills/component-identification-sizingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Component Identification and Sizing This skill identifies architectural components (logical building blocks) in a codebase and calculates size metrics to assess decomposition feasibility and identify oversized components. ## How to Use ### Quick Start Request analysis of your codebase: - **"Identify and size all components in this codebase"** - **"Find oversized components that need splitting"** - **"Create a component inventory for decomposition planning"** - **"Analyze component size distribution"** ### Usage Examples **Example 1: Complete Analysis** ``` User: "Identify and size all components in this codebase" The skill will: 1. Map directory/namespace structures 2. Identify all components (leaf nodes) 3. Calculate size metrics (statements, files, percentages) 4. Generate component inventory table 5. Flag oversized/undersized components 6. Provide recommendations ``` **Example 2: Find Oversized Components** ``` User: "Which components are too large?" The skill will: 1. Calculate mean and standard deviation 2. Identify components >2 std dev or >10% threshold 3. Analyze functional areas within large components 4. Suggest specific splits with estimated sizes ``` **Example 3: Component Size Analysis** ``` User: "Analyze component sizes and distribution" The skill will: 1. Calculate all size metrics 2. Generate size distribution summary 3. Identify outliers 4. Provide statistics and recommendations ``` ### Step-by-Step Process
Details
- Skill name
component-identification-sizing- Repository
- tech-leads-club/agent-skills
- Path
packages/skills-catalog/skills/(architecture)/component-identification-sizing/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Component Identification Sizing skill do?
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning where to start decomposing. Do NOT use for runtime performance sizing or infrastructure capacity planning.
How do I install the Component Identification Sizing skill?
Claude Code plugin: /plugin marketplace add tech-leads-club/agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Component Identification Sizing popular?
It lives in tech-leads-club/agent-skills, which has 7,177 GitHub stars and 568 forks.
Related skills
Frontend Design
7.2ktech-leads-club/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics. Do NOT use for design review or audit (use web-design-guidelines or web-quality-audit).
Web Design Guidelines
7.2ktech-leads-club/agent-skills
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit).
AI Cold Outreach
7.2ktech-leads-club/agent-skills
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture.
Figma Implement Design
7.2ktech-leads-club/agent-skills
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Use when the user provides Figma URLs or node IDs and asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection. Do NOT use for general Figma data fetching, variable exploration, or MCP troubleshooting (use figma instead).
Component Flattening Analysis
7.2ktech-leads-club/agent-skills
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking "clean up component structure", "find orphaned classes", "fix module hierarchy", "flatten nested components", or analyzing why namespaces have misplaced code. Do NOT use for dependency analysis (use coupling-analysis) or domain grouping (use domain-identification-grouping).
Frontend Blueprint
7.2ktech-leads-club/agent-skills
AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code. Collects visual references, design tokens, typography, icons, layout preferences, and brand guidelines to ensure the final output matches the user's vision with high fidelity. Use when the user asks to build, design, create, or improve any frontend interface — websites, landing pages, dashboards, components, apps, emails, forms, modals, or any UI element. Also triggers on "build me a UI", "design a page", "create a component", "improve this layout", "make this look
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.