Skip to content
Back to skills

Common Architecture Audit

ASecurity

Protocol for auditing structural debt, logic leakage, and fragmentation across Web, Mobile, and Backend. (triggers: package.json, pubspec.yaml, go.mod, pom.xml, nest-cli.json, architecture audit, code review, tech debt, logic leakage, refactor)

  • 43 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 30, 2026
developmentgojavabashreactvuenextjsspringapibackendperformance

Works with

  • cli
  • api

Security analysis

A100/100

Scanned May 30, 2026

npx -y skills add ComeOnOliver/skillshub --skill common-architecture-audit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Common Architecture Audit?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Common Architecture Audit
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/comeonoliver-common-architecture-audit/badge)](https://www.skillsdirectory.com/skills/comeonoliver-common-architecture-audit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: common-architecture-audit
description: "Protocol for auditing structural debt, logic leakage, and fragmentation across Web, Mobile, and Backend. (triggers: package.json, pubspec.yaml, go.mod, pom.xml, nest-cli.json, architecture audit, code review, tech debt, logic leakage, refactor)"
---

# Architecture Audit

## **Priority: P1 (STANDARD)**

## πŸ“‹ Audit Protocol

### 1. Structural Duplication Discovery (Universal)

Identify split sources of truth by searching for redundant directory patterns or naming conventions.

- **Services**: Compare `Service.ts` vs `ServiceNew.ts` vs `ServiceV2.ts`.
- **Versioning**: Check for `/v1`, `/v2` or "Refactor" folders.
- **Action**:
  ```bash
  # Identify potential duplicates or legacy files
  find . -type f -name "*New.*" | sed 's/New//'
  ```

### 2. Logic Leakage Analysis (Ecosystem Specific)

Detect business logic trapped in the wrong layer (e.g., UI layer in apps, Controller layer in APIs).

#### 🌐 Web (React/Next.js/Vue)

- **Action**: `grep -rE "useEffect|useState|useMemo" components --include="*.tsx" | wc -l`
- **Threshold**: If `components/` hook count > 20x `hooks/` folder, architecture is **Monolithic**.

#### πŸ“± Mobile (Flutter/React Native)

- **Action**: `grep -rE "http\.|dio\.|socket\." lib/widgets --include="*.dart" | wc -l`
- **Threshold**: I/O or state mutation > 5 lines in `build()` is 🟠 High Debt.

#### βš™οΈ Backend (NestJS/Go/Spring)

- **Action**: `grep -rE "Repository\.|Query\.|db\." src/controllers --include="*.ts" | wc -l`
- **Threshold**: Controllers must only handle request parsing and response formatting.

### 3. Monolith Detection (Ecosystem Specific)

Identify massive files violating Single Responsibility Principle.

- **Thresholds**:
  - **UI**: > 500 lines (🟑 Medium), > 1,000 lines (πŸ”΄ Critical).
  - **Backend Services**: > 1,500 lines indicate "God Class".
- **Action**:
  ```bash
  find . -type f \( -name "*.tsx" -o -name "*.dart" -o -name "*.go" -o -name "*.java" \) | xargs wc -l | awk '$1 > 1000'
  ```

### 4. Resource Performance Audit (Universal)

Check for large metadata or constants impacting IDE performance and binary size.

- **Threshold**: Resources > 1,000 lines require granulation.
- **Action**:
  ```bash
  find . -type f \( -name "*constants*" -o -name "*.graphql" -o -name "*strings*" \) | xargs wc -l | awk '$1 > 1000'
  ```

## βš–οΈ Scoring Impact

- **Layer Violation**: -15 per business logic instance in UI/Controller layer.
- **Structural Fragmentation**: -10 per duplicated legacy entity.
- **Monoliths**: -10 per unit > 1,000 lines.

## πŸ“š Reference Links

- [Architecture Patterns & Remediation Protocols](references/PATTERNS.md)


## 🚫 Anti-Patterns

- Do NOT use standard patterns if specific project rules exist.
- Do NOT ignore error handling or edge cases.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…