Component Flattening Analysis workflow skill. Use this skill when the user needs 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) and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Explorador de arquivos
5 arquivos
Exibindo SKILL.md
SKILL.md
Instruções da origem · Visualização somente leitura
name
component-flattening-analysis
description
Component Flattening Analysis workflow skill. Use this skill when the user needs 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) and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages packages/skills-catalog/skills/(architecture)/component-flattening-analysis from https://github.com/tech-leads-club/agent-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Component Flattening Analysis This skill identifies component hierarchy issues and ensures components exist only as leaf nodes in directory/namespace structures, removing orphaned classes from root namespaces.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How to Use, Core Concepts, Component Structure Map, Orphaned Classes Found, Flattening Options Analysis, Flattening Plan.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
After gathering common domain components (Pattern 2)
Before determining component dependencies (Pattern 4)
When components have nested structures
Finding orphaned classes in root namespaces
Preparing for domain grouping
Cleaning up component structure
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
QUICK-REFERENCE.md
Starts with the smallest copied file that materially changes execution
Supporting context
README.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Map Namespace Tree
Build tree of all namespaces
Identify parent-child relationships
Mark leaf nodes (components)
Identify Root Namespaces
Find namespaces that have been extended
Mark as root namespaces (subdomains)
Imported Workflow Notes
Imported: Analysis Process
Phase 1: Map Component Structure
Scan directory/namespace structure to identify hierarchy:
Map Namespace Tree
Build tree of all namespaces
Identify parent-child relationships
Mark leaf nodes (components)
Identify Root Namespaces
Find namespaces that have been extended
Mark as root namespaces (subdomains)
Note which namespaces extend them
Locate Source Files
Find all source files in each namespace
Map files to their namespace location
Identify files in root namespaces
Example Structure Mapping:
#### Imported: Next Steps
After flattening components:
1.**Apply Determine Component Dependencies Pattern** - Analyze coupling
2.**Create Component Domains** - Group components into domains
3.**Create Domain Services** - Extract domains to services
#### Imported: How to Use### Quick Start
Request analysis of your codebase:
-**"Find orphaned classes in root namespaces"**-**"Flatten component hierarchies"**-**"Identify components that need flattening"**-**"Analyze component structure for hierarchy issues"**### Usage Examples**Example 1: Find Orphaned Classes**
User: "Find orphaned classes in root namespaces"
The skill will:
Scan component namespaces for hierarchy issues
Identify orphaned classes in root namespaces
Detect components built on top of other components
Suggest flattening strategies
Create refactoring plan
**Example 2: Flatten Components**
User: "Flatten component hierarchies in this codebase"
The skill will:
Identify components with hierarchy issues
Analyze orphaned classes
Suggest consolidation or splitting strategies
Create refactoring plan
Estimate effort
**Example 3: Component Structure Analysis**
User: "Analyze component structure for hierarchy issues"
The skill will:
Map component namespace structure
Identify root namespaces with code
Find components built on components
Flag hierarchy violations
Provide recommendations
### Step-by-Step Process
1. **Scan Structure**: Map component namespace hierarchies
2. **Identify Issues**: Find orphaned classes and component nesting
3. **Analyze Options**: Determine flattening strategy (consolidate vs split)
4. **Create Plan**: Generate refactoring plan with steps
5. **Execute**: Refactor components to remove hierarchy
## Examples
### Example 1: Ask for the upstream workflow directly
```text
Use @component-flattening-analysis to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @component-flattening-analysis against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @component-flattening-analysis for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @component-flattening-analysis using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Ensure components exist only as leaf nodes
Remove orphaned classes from root namespaces
Choose flattening strategy based on functionality
Consolidate when functionality is related
Split when functionality is distinct
Extract shared code to .shared components
Update all references after flattening
Imported Operating Notes
Imported: Best Practices
Do's ✅
Ensure components exist only as leaf nodes
Remove orphaned classes from root namespaces
Choose flattening strategy based on functionality
Consolidate when functionality is related
Split when functionality is distinct
Extract shared code to .shared components
Update all references after flattening
Verify changes with tests
Don'ts ❌
Don't leave orphaned classes in root namespaces
Don't create components on top of other components
Don't skip updating imports after moving files
Don't flatten without analyzing impact
Don't mix flattening strategies inconsistently
Don't ignore shared code when flattening
Don't skip testing after refactoring
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in packages/skills-catalog/skills/(architecture)/component-flattening-analysis, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@accessibility - Use when the work is better handled by that native specialization after this imported skill establishes context.
@ai-cold-outreach - Use when the work is better handled by that native specialization after this imported skill establishes context.
@ai-pricing - Use when the work is better handled by that native specialization after this imported skill establishes context.
@ai-sdr - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
