home / skills / hubvue / skills / architecture-analysis

architecture-analysis skill

/fe-analysis/architecture-analysis

This skill analyzes frontend projects to identify frameworks, build tools, patterns, and quality metrics, delivering actionable insights for architecture

npx playbooks add skill hubvue/skills --skill architecture-analysis

Review the files below or copy the command above to add this skill to your agents.

Files (12)
SKILL.md
3.7 KB
---
name: architecture-analysis
description: Comprehensive frontend architecture analyzer that identifies technology stacks, build tools, and architectural patterns. Use when you need to quickly understand a project's structure, dependencies, and technical configuration. Provides analysis for Vue/React/Angular frameworks, Node.js environments, package managers, TypeScript usage, linters, and architecture patterns with multiple output formats including executive summaries and visualizations.
---

# Frontend Architecture Analyzer

This skill analyzes frontend project architecture and provides comprehensive insights about technology stacks, build tools, and architectural patterns.

## Quick Start

Analyze any frontend project with a single command:

```javascript
const result = await analyzeProject("/path/to/project", {
  format: "markdown",  // json, markdown, summary, scorecard
  includeRecommendations: true
});
```

## Core Capabilities

The analyzer detects:
- **Frameworks**: Vue, React, Angular, Svelte, Solid.js
- **Meta-frameworks**: Nuxt, Next.js, Remix, Gatsby, Astro
- **Build Tools**: Vite, Webpack, Rollup, Parcel, esbuild
- **Package Managers**: pnpm, yarn, npm
- **Architecture Patterns**: Monorepo, microservices, modular, layered
- **Quality Metrics**: TypeScript coverage, linters, code quality tools

## Output Formats

Choose the format that best suits your audience:

### Technical Analysis (JSON)
```json
{
  "success": true,
  "data": {
    "framework": { "name": "vue", "metaFramework": "nuxt" },
    "buildTool": { "name": "vite", "version": "5.0.0" },
    "architecturePatterns": ["modular", "layered"]
  }
}
```

### Markdown Report
Human-readable report with sections for stakeholders

### Executive Summary
High-level overview for decision makers

### Scorecard
Quantitative assessment with scores

## Usage Examples

### Basic Analysis
```bash
node scripts/analyze-project.js /path/to/project
```

### With Options
```bash
node scripts/analyze-project.js /path/to/project '{"format": "markdown", "depth": 2}'
```

### Generate Executive Summary
```javascript
const analyzer = new ProjectAnalyzer("./my-project");
const result = await analyzer.analyze();
const report = new ReportGenerator(result);
const summary = report.generate("summary");
```

## Advanced Features

### Pattern Recognition
- **Monorepo Detection**: Identifies workspace configurations
- **Microservices**: Service-based architecture detection
- **Modular Design**: Feature-based organization analysis
- **Layered Architecture**: Controller-service-repository patterns

### Quality Assessment
- TypeScript adoption and coverage calculation
- Code quality tool detection (ESLint, Prettier, Stylelint)
- Architectural complexity evaluation
- Maintainability scoring

### Recommendations Engine
Provides actionable recommendations based on:
- Missing tooling (testing, linting)
- Architecture improvements
- Best practice adoption
- Technology debt

## Implementation Details

### Detector Modules
- `framework-detector.js` - Framework and meta-framework detection
- `build-tool-detector.js` - Build tool and bundler identification
- `architecture-detector.js` - Pattern recognition and scoring

### Report Generator
Supports multiple output formats:
- Technical JSON for API integration
- Markdown for documentation
- Executive summaries for presentations
- Scorecards for metrics tracking

## Reference Documentation

Detailed implementation guides and patterns:

- **Framework Detection**: See [framework-patterns.md](references/framework-patterns.md)
- **Build Tools**: See [build-tool-patterns.md](references/build-tool-patterns.md)
- **Architecture Patterns**: See [architecture-patterns.md](references/architecture-patterns.md)
- **Output Formats**: See [output-formats.md](references/output-formats.md)

Overview

This skill is a comprehensive frontend architecture analyzer that identifies frameworks, meta-frameworks, build tools, package managers, and architectural patterns. It delivers actionable diagnostics, quality metrics, and targeted recommendations to rapidly understand a project’s technical configuration. Outputs include JSON, markdown, executive summaries, and scorecards for different audiences.

How this skill works

The analyzer scans project files, package manifests, and configuration files to detect frameworks (Vue/React/Angular/Svelte/Solid), meta-frameworks, and build systems like Vite or Webpack. It evaluates TypeScript adoption, linters, package manager workspaces, and folder organization to infer architecture patterns (monorepo, modular, layered, microservices). The tool produces structured reports and optional recommendations based on detected gaps and quality metrics.

When to use it

  • Onboarding new developers to a codebase to speed ramp-up
  • Preparing technical due diligence for acquisitions or audits
  • Planning migrations or upgrades of frameworks, build tools, or TypeScript adoption
  • Evaluating code quality and maintainability across frontend services
  • Generating stakeholder-friendly executive summaries and scorecards

Best practices

  • Run the analyzer from the project root and include node_modules if you need exact dependency versions
  • Choose JSON for automation and markdown or summary for stakeholder communication
  • Combine the analyzer with static analysis and test coverage tools for a fuller view
  • Use the recommendations output to prioritize low-effort, high-impact tooling improvements
  • Re-run analysis after major refactors or dependency updates to track architectural drift

Example use cases

  • Quickly detect whether a repo uses React+Next, Vue+Nuxt, or another stack and list versions
  • Produce an executive summary for leadership showing readiness for production or migration risk
  • Generate a scorecard comparing TypeScript coverage, linters, and build tool maturity across multiple projects
  • Identify monorepo workspaces and recommend modularization or build optimizations
  • Create a markdown audit that lists missing tooling (tests, linters) with prioritized recommendations

FAQ

What formats can I get the analysis in?

Outputs include JSON for automation, markdown for documentation, an executive summary for decision makers, and a numeric scorecard for tracking metrics.

Can it detect monorepos and workspace package managers?

Yes. It inspects package manifests and workspace configs to identify pnpm, yarn, npm workspaces and infer monorepo setups.