architecture-analysis
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.
What this skill does
# 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)
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.