Software Development
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.
- Publisher / source
- tech-leads-club/agent-skills (found on GitHub top repositories)
- Upstream record
- tech-leads-club/agent-skills
- Version
- Version 1
- Published
- Publication review
- Approved for publication
- Content fingerprint
af483380e38eaf9e57f12e599b77eda9488835c5616f5ee84d8e97b8199e0f4b