component-identification-sizing

SKILLWorkflowcommunity
v0.0.0tech-leads-clubNOASSERTIONUpdated 1mo agoSource →

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 decompo

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
5kRepo stars
1Clients
1Formats
1mo agoLast update
Skill
Authortech-leads-club
Version0.0.0
LicenseNOASSERTION
CategoryWorkflow
Formatsskill.md
PromptOpen (see Prompt tab)
Compatibility
Claude✓ Supported
Cursor—
Copilot—
ChatGPT—
Gemini—
About

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.

Keywords
skillclaude

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.