Component Identification Sizing

by tech-leads-club120b67676388No licenseListed Oct 8, 2026Updated Oct 8, 2026

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.

Instructions onlySoftware Development
  1. 120b67676388Currentcommit 120b676Published Oct 8, 2026

Source and attribution

Source:tech-leads-club/agent-skillsinpackages/skills-catalog/skills/(architecture)/component-identification-sizingat commit120b676

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal