Common Architecture Audit Agent Skill

Audit structural debt, logic leakage, and monolithic components across Web, Mobile, and Backend codebases. Use when reviewing architecture, assessing tech debt, detecting logic in wrong layers, or identifying God classes.

3k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

536

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill common-architecture-audit

What comes with it

7 584 bytes besides the instruction

evals/evals.json

references/PATTERNS.md

references/detection.md

references/implementation.md

The instruction itself

9 sections, as written by the author

Architecture Audit

Priority: P1 (HIGH)

1. Discover Structural Duplication

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

Compare Service.ts vs ServiceNew.ts vs ServiceV2.ts.
Check for /v1, /v2 or "Refactor" folders.

See implementation examples for detection scripts.

2. Detect Logic Leakage (by Ecosystem)

Find business logic trapped in wrong layer.

Web (React/Next.js/Vue): grep -rE "useEffect|useState|useMemo" components --include="*.tsx" | wc -l — if components/ hook count > 20x hooks/ folder, architecture monolithic.
Mobile (Flutter/React Native): grep -rE "http\.|dio\.|socket\." lib/widgets --include="*.dart" | wc -l — I/O or state mutation > 5 lines in build() High Debt.
Backend (NestJS/Go/Spring): grep -rE "Repository\.|Query\.|db\." src/controllers --include="*.ts" | wc -l — Controllers must only handle request parsing and response formatting.

3. Identify Monoliths

Flag massive files violating Single Responsibility Principle.

UI: > 500 lines (Medium), > 1,000 lines (Critical).
Backend Services: > 1,500 lines indicates "God Class".

See implementation examples for monolith detection scripts.

4. Audit Resource Performance

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

Resources > 1,000 lines require granulation.

See implementation examples for resource audit scripts.

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.

Anti-Patterns

No applying generic patterns over project-specific rules: Respect existing architecture constraints.
No ignoring error handling or edge cases: Audit must cover boundary conditions.

References

Architecture Patterns & Remediation Protocols

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take hoangnguyen0403/common-architecture-audit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.