
Workspace Performance Audit
- 137 installs
- 31 repo stars
- Updated August 2, 2026
- shipshitdev/library
Diagnose slow IDE or agent workspaces—indexing, extensions, large repos—and recommend fixes to restore developer throughput.
About
Audits developer workspace performance for Cursor, VS Code, or agent environments: indexing bottlenecks, extension load, monorepo scope, git and search settings, and concrete tuning so coding and AI assistance stay fast at scale.
- Index and watcher analysis
- Extension impact review
- Repo size hotspots
- Cache and ignore tuning
- Throughput recovery plan
Workspace Performance Audit by the numbers
- 137 all-time installs (skills.sh)
- +3 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #1,225 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/shipshitdev/library --skill workspace-performance-auditAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 137 |
|---|---|
| repo stars | ★ 31 |
| Last updated | August 2, 2026 |
| Repository | shipshitdev/library ↗ |
What it does
Diagnose slow IDE or agent workspaces—indexing, extensions, large repos—and recommend fixes to restore developer throughput.
Files
Workspace Performance Audit
Contract
Inputs:
- Monorepo root path (defaults to current working directory)
- Optional: target domain(s) to focus on (frontend, backend, database, extension)
- Optional: audit mode (quick or full)
Outputs:
- Consolidated performance audit report
- Prioritized recommendations with severity ratings
Creates/Modifies:
.agents/memory/performance-audit-YYYY-MM-DD.md— writes the audit report
External Side Effects:
- None. Read-only analysis only; does not deploy, modify, or install anything.
Confirmation Required:
- Before writing the output report if the target path is outside the current workspace
Delegates To:
performance-expertfor metrics and optimizationdesign-consistency-auditorfor UI/UX consistencyqa-reviewerfor validation and prioritization
Overview
Orchestrates comprehensive performance audits across entire monorepo workspaces. Coordinates multiple specialized skills to analyze frontend (Next.js), backend (NestJS), database (MongoDB), browser extensions (Plasmo), and shared packages—delivering consolidated reports with prioritized recommendations.
When to Use
- Full workspace performance review
- Audit a monorepo
- "audit performance", "check workspace performance"
- Identify bottlenecks across frontend, backend, extensions
- Consolidated performance metrics needed
Skills Orchestrated
| Skill | Focus Area | Phase |
|---|---|---|
performance-expert | Performance metrics & optimization | 1-4 |
design-consistency-auditor | UI/UX consistency & design debt | 1 |
accessibility | WCAG 2.1 AA compliance | 1 |
security-expert | Security validation | 2 |
qa-reviewer | Validation & prioritization | 5 |
Orchestration Flow
Phase 0: Workspace Discovery
→ Identify apps, packages, tech stacks
Phase 1: Frontend Audit (Next.js)
→ Core Web Vitals, Bundle Analysis, Design, A11y
Phase 2: Backend Audit (NestJS)
→ API Response Times, N+1 Queries, Security
Phase 3: Database Audit (MongoDB)
→ Query Performance, Index Analysis
Phase 4: Extension & Packages
→ Bundle Sizes, Memory, Dependencies
Phase 5: Consolidation
→ Aggregate, Score, Prioritize, ReportKey Metrics by Domain
| Domain | Key Metrics | Targets |
|---|---|---|
| Frontend | LCP, FID, CLS | <2.5s, <100ms, <0.1 |
| Backend | p50, p95 response | <100ms, <200ms |
| Database | Query p95, Index hit | <50ms, >95% |
| Extension | Content script size | <50KB |
Usage Modes
Quick Audit: Essential checks only → 1-page summary Full Audit: All phases → Complete report Domain-Specific: Single domain focus
Integration
Produces reports in .agents/memory/performance-audit-YYYY-MM-DD.md
---
For detailed phase execution, metric collection commands, report templates, best practices, and example interactions: load ${CLAUDE_SKILL_DIR}/references/full-guide.md when starting a full audit or when a specific phase requires detailed guidance.
{
"name": "workspace-performance-audit",
"version": "1.0.0",
"description": "Orchestrates comprehensive performance audits across full-stack monorepos. Coordinates performance-e",
"author": {
"name": "Ship Shit Dev",
"email": "hello@shipshit.dev",
"url": "https://shipshit.dev"
},
"license": "MIT",
"skills": "."
}
Workspace Performance Audit - Full Guide
Orchestration Flow
┌─────────────────────────────────────────────────────────────┐
│ WORKSPACE PERFORMANCE AUDIT ORCHESTRATOR │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 0: WORKSPACE DISCOVERY │
│ • Identify monorepo structure │
│ • Detect apps: web, api, mobile, extension │
│ • Detect packages: shared, ui, types │
│ • Identify tech stack per app │
│ • Check for existing metrics/monitoring │
└─────────────────────────────────────────────────────────────┘
│
┌────────────────┼────────────────┐
▼ ▼ ▼
┌─────────────────┐ ┌─────────────┐ ┌─────────────────┐
│ PHASE 1: │ │ PHASE 2: │ │ PHASE 3: │
│ FRONTEND │ │ BACKEND │ │ DATABASE │
│ AUDIT │ │ AUDIT │ │ AUDIT │
└─────────────────┘ └─────────────┘ └─────────────────┘
│ │ │
└────────────────┼────────────────┘
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 4: EXTENSION & SHARED PACKAGES AUDIT │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 5: CONSOLIDATION & PRIORITIZATION │
│ • Aggregate findings from all phases │
│ • Calculate impact scores │
│ • Prioritize by ROI (impact / effort) │
│ • Generate consolidated report │
└─────────────────────────────────────────────────────────────┘Phase Details
Phase 0: Workspace Discovery
Goal: Map the monorepo structure and identify audit targets.
Actions:
# Discover monorepo structure
ls -la apps/
ls -la packages/
# Check package.json for workspace config
cat package.json | grep -A 10 "workspaces"
# Identify tech stacks
cat apps/web/package.json # Next.js
cat apps/api/package.json # NestJS
cat apps/extension/package.json # PlasmoOutput:
Workspace: GenFeedAI
├── apps/
│ ├── web (Next.js 14, React 18)
│ ├── api (NestJS 10, MongoDB)
│ ├── mobile (Expo 50, React Native)
│ └── extension (Plasmo, Chrome MV3)
├── packages/
│ ├── ui (@genfeedai/ui)
│ ├── shared (@genfeedai/shared)
│ └── types (@genfeedai/types)---
Phase 1: Frontend Audit (Next.js)
Skills Invoked:
performance-expert(primary)design-consistency-auditoraccessibility
Metrics to Collect:
| Metric | Target | Tool |
|---|---|---|
| LCP (Largest Contentful Paint) | < 2.5s | Lighthouse |
| FID (First Input Delay) | < 100ms | Lighthouse |
| CLS (Cumulative Layout Shift) | < 0.1 | Lighthouse |
| Initial Bundle Size | < 200KB | webpack-bundle-analyzer |
| Total Bundle Size | < 500KB | webpack-bundle-analyzer |
| Image Optimization | WebP/AVIF | Manual check |
| Code Splitting | Dynamic imports | Manual check |
Checks:
// Bundle Analysis
// Run: npx @next/bundle-analyzer
// Core Web Vitals
// Run: npx lighthouse https://app.example.com --output=json
// Design Consistency Checks (via design-consistency-auditor)
// - Color palette consistency
// - Typography scale adherence
// - Spacing system compliance
// - Component pattern consistency
// Accessibility Checks (via accessibility skill)
// - WCAG 2.1 AA compliance
// - Keyboard navigation
// - Screen reader compatibility
// - Color contrast ratios (≥ 4.5:1)Report Template:
## Frontend Performance Report
### Core Web Vitals
| Metric | Current | Target | Status |
|--------|---------|--------|--------|
| LCP | X.Xs | <2.5s | ✓/✗ |
| FID | Xms | <100ms | ✓/✗ |
| CLS | X.XX | <0.1 | ✓/✗ |
### Bundle Analysis
- Initial bundle: XXX KB (target: <200KB)
- Largest chunks: [list]
- Unused code: XX KB
### Design Consistency
- Color violations: X
- Spacing inconsistencies: X
- Component pattern issues: X
### Accessibility
- Critical issues: X
- WCAG violations: [list]
### Recommendations
1. [High Impact] ...
2. [Medium Impact] ...---
Phase 2: Backend Audit (NestJS)
Skills Invoked:
performance-expert(primary)security-expert
Metrics to Collect:
| Metric | Target | Tool |
|---|---|---|
| API Response Time (p50) | < 100ms | APM/Logs |
| API Response Time (p95) | < 200ms | APM/Logs |
| Throughput | > 1000 req/s | Load test |
| Error Rate | < 0.1% | Logs |
| Memory Usage | < 512MB | Process metrics |
| CPU Usage | < 70% | Process metrics |
Checks:
// API Performance Analysis
// - Identify slow endpoints
// - Check N+1 query patterns
// - Validate caching strategy
// - Review connection pooling
// Security Checks (via security-expert)
// - Authentication patterns
// - Rate limiting configuration
// - Input validation
// - CORS configuration
// - Security headers
// Code Quality
// - Async/await patterns
// - Error handling
// - Logging patterns
// - Memory leak potentialReport Template:
## Backend Performance Report
### API Response Times
| Endpoint | p50 | p95 | Target | Status |
|----------|-----|-----|--------|--------|
| GET /api/posts | Xms | Xms | <200ms | ✓/✗ |
| POST /api/posts | Xms | Xms | <200ms | ✓/✗ |
### Resource Usage
- Memory: XXX MB (target: <512MB)
- CPU: XX% (target: <70%)
- Connections: XX active
### Security
- Rate limiting: ✓/✗
- Auth validation: ✓/✗
- Input sanitization: ✓/✗
### N+1 Queries Detected
1. [endpoint]: [query pattern]
### Recommendations
1. [High Impact] ...
2. [Medium Impact] ...---
Phase 3: Database Audit (MongoDB)
Skills Invoked:
performance-expert(primary)
Metrics to Collect:
| Metric | Target | Tool |
|---|---|---|
| Query Time (p95) | < 50ms | MongoDB Profiler |
| Index Hit Ratio | > 95% | db.serverStatus() |
| Connection Pool Usage | < 80% | Connection metrics |
| Slow Queries (>100ms) | 0 | Slow query log |
Checks:
// Index Analysis
db.collection.getIndexes()
db.collection.aggregate([{$indexStats: {}}])
// Slow Query Analysis
db.setProfilingLevel(1, { slowms: 100 })
db.system.profile.find().sort({ts: -1}).limit(10)
// Collection Stats
db.collection.stats()
// Connection Pool
db.serverStatus().connectionsReport Template:
## Database Performance Report
### Query Performance
| Collection | Avg Query Time | Index Usage | Status |
|------------|----------------|-------------|--------|
| posts | Xms | XX% | ✓/✗ |
| users | Xms | XX% | ✓/✗ |
### Index Analysis
- Total indexes: X
- Unused indexes: X
- Missing indexes: [list suggested]
### Slow Queries (>100ms)
1. [query pattern]: Xms
2. [query pattern]: Xms
### Recommendations
1. [High Impact] Add index on...
2. [Medium Impact] Optimize aggregation...---
Phase 4: Extension & Shared Packages
Skills Invoked:
performance-expert(primary)design-consistency-auditor(for extension UI)
Browser Extension Audit
Metrics:
| Metric | Target | Tool |
|---|---|---|
| Content Script Size | < 50KB | Bundle analysis |
| Background Script Size | < 100KB | Bundle analysis |
| Memory Usage | < 50MB | Chrome DevTools |
| Message Latency | < 10ms | Performance.now() |
Checks:
// Bundle size
// Check: apps/extension/build/
// Memory profiling
// Chrome DevTools → Memory tab → Heap snapshot
// Message passing performance
// Measure chrome.runtime.sendMessage latency
// Storage efficiency
// Check chrome.storage.local usageShared Packages Audit
Checks:
# Dependency duplication
npx depcheck
# Bundle contribution analysis
# Check how much each package adds to final bundles
# Tree-shaking effectiveness
# Verify unused exports are eliminated
# Version consistency
# Check for version mismatches across appsReport Template:
## Extension & Packages Report
### Browser Extension
- Content script: XX KB (target: <50KB)
- Background script: XX KB (target: <100KB)
- Memory usage: XX MB (target: <50MB)
### Shared Packages
| Package | Size | Used By | Tree-Shakeable |
|---------|------|---------|----------------|
| @org/ui | XX KB | web, extension | ✓/✗ |
| @org/shared | XX KB | all | ✓/✗ |
### Dependency Issues
- Duplicates: [list]
- Version conflicts: [list]
- Unused: [list]
### Recommendations
1. [High Impact] ...---
Phase 5: Consolidation & Prioritization
Skills Invoked:
qa-reviewer(validation)
Actions:
1. Aggregate all findings from Phases 1-4 2. Calculate impact scores (1-10) 3. Estimate effort (hours/days) 4. Calculate ROI = Impact / Effort 5. Prioritize recommendations
Final Report Template:
# Workspace Performance Audit Report
**Project:** [Name]
**Date:** YYYY-MM-DD
**Auditor:** Claude
## Executive Summary
- Overall Health Score: X/10
- Critical Issues: X
- High Priority Items: X
- Quick Wins Identified: X
## Health by Domain
| Domain | Score | Critical | High | Medium | Low |
|--------|-------|----------|------|--------|-----|
| Frontend | X/10 | X | X | X | X |
| Backend | X/10 | X | X | X | X |
| Database | X/10 | X | X | X | X |
| Extension | X/10 | X | X | X | X |
| Packages | X/10 | X | X | X | X |
## Prioritized Recommendations
### Quick Wins (High Impact, Low Effort)
1. **[Domain]** Issue description
- Impact: X/10
- Effort: X hours
- Action: ...
### High Priority (High Impact, Medium Effort)
1. **[Domain]** Issue description
- Impact: X/10
- Effort: X days
- Action: ...
### Technical Debt (Medium Impact, Variable Effort)
1. **[Domain]** Issue description
- Impact: X/10
- Effort: X days
- Action: ...
## Next Steps
1. Address critical issues immediately
2. Schedule quick wins for next sprint
3. Add high priority items to backlog
4. Review technical debt quarterlyBest Practices
Before Audit
- Ensure all apps are buildable
- Have access to production metrics if available
- Clear any local caches for accurate bundle analysis
During Audit
- Document current state before changes
- Take screenshots of metrics
- Note any anomalies or edge cases
After Audit
- Create tickets for each recommendation
- Establish baseline metrics
- Schedule follow-up audit (quarterly recommended)
Example Interaction
User: "Run a performance audit on the GenFeedAI monorepo"
Orchestrator:
Starting Workspace Performance Audit...
Phase 0: Workspace Discovery
✓ Found monorepo structure
✓ Detected apps: web, api, extension
✓ Detected packages: ui, shared, types
Phase 1: Frontend Audit (apps/web)
✓ Core Web Vitals collected
✓ Bundle analysis complete
✓ Design consistency checked
✓ Accessibility validated
Phase 2: Backend Audit (apps/api)
✓ API response times measured
✓ N+1 queries detected: 3
✓ Security configuration reviewed
Phase 3: Database Audit
✓ Query performance analyzed
✓ Index usage reviewed
✓ Slow queries identified: 2
Phase 4: Extension & Packages
✓ Extension bundle analyzed
✓ Shared package sizes measured
✓ Dependency audit complete
Phase 5: Consolidation
✓ Findings aggregated
✓ Recommendations prioritized
═══════════════════════════════════════
AUDIT COMPLETE
Overall Health: 7.2/10
Top 3 Quick Wins:
1. Add index on posts.userId (Database) - 2x query improvement
2. Enable Next.js image optimization (Frontend) - 40% LCP improvement
3. Implement response caching (Backend) - 50% latency reduction
Critical Issues: 1
- N+1 query in /api/feed endpoint
Full report generated at: .agents/memory/performance-audit-2025-01-XX.md
═══════════════════════════════════════