component-identification-sizing
About
This skill analyzes a codebase to map its architectural components and measure their size, helping developers identify which modules are too large and should be extracted first. It's used for planning monolith decomposition, answering questions like "what components do I have?" and "which service is too large?". It focuses on static code structure for refactoring, not for runtime performance or infrastructure sizing.
Quick Install
Claude Code
Recommendednpx skills add tech-leads-club/agent-skills -a claude-code/plugin add https://github.com/tech-leads-club/agent-skillsgit clone https://github.com/tech-leads-club/agent-skills.git ~/.claude/skills/component-identification-sizingCopy and paste this command in Claude Code to install this skill
GitHub Repository
Frequently asked questions
What is the component-identification-sizing skill?
component-identification-sizing is a Claude Skill by tech-leads-club. Skills package instructions and resources that Claude loads on demand, so Claude can perform component-identification-sizing-related tasks without extra prompting.
How do I install component-identification-sizing?
Use the install commands on this page: add component-identification-sizing to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does component-identification-sizing belong to?
component-identification-sizing is in the Design category, tagged general.
Is component-identification-sizing free to use?
Yes. component-identification-sizing is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.
Related Skills
Use the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
This skill dispatches a code-reviewer subagent to analyze code changes against requirements before proceeding. It should be used after completing tasks, implementing major features, or before merging to main. The review helps catch issues early by comparing the current implementation with the original plan.
This skill provides a comprehensive guide for developers to connect MCP servers to Claude Code using HTTP, stdio, or SSE transports. It covers installation, configuration, authentication, and security for integrating external services like GitHub, Notion, and custom APIs. Use it when setting up MCP integrations, configuring external tools, or working with Claude's Model Context Protocol.
This skill helps developers choose between Claude Code Web and CLI interfaces based on task analysis, then enables seamless session teleportation between these environments. It optimizes workflow by managing session state and context when switching between web, CLI, or mobile. Use it for complex projects requiring different tools at various stages.