claude-react-kit: Skill for Claude Code

.claude/skills/audit-architecture/SKILL.md

audit-architecture is a skill for Claude Code from aleolidev/claude-react-kit. It costs 14 tokens per session (490 once invoked), scanned A, original, MIT.

A codebase audit that checks whether the project follows its intended architecture, including allowed dependencies and file organization.

In plain words
What is it for?
Use it to inspect architecture boundaries, design-system purity, file sizes, empty directories, and naming consistency.
Why use it?
It reveals structural problems such as features importing each other, core code depending on features, oversized files, empty folders, and duplicate names.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is aleolidev/claude-react-kit's own configuration. It tells Claude Code how to work on claude-react-kit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-react-kit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to aleolidev/claude-react-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/aleolidev/claude-react-kit/main/.claude/skills/audit-architecture/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/aleolidev/claude-react-kit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for audit-architecture

README.md
[![agentmods](https://agentmods.dev/badge/skills/aleolidev/claude-react-kit/audit-architecture/github.svg)](https://agentmods.dev/skills/aleolidev/claude-react-kit/audit-architecture)
Your own site
<a href="https://agentmods.dev/skills/aleolidev/claude-react-kit/audit-architecture"><img src="https://agentmods.dev/badge/skills/aleolidev/claude-react-kit/audit-architecture/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for audit-architecture

Your own site · 80×15
<a href="https://agentmods.dev/skills/aleolidev/claude-react-kit/audit-architecture"><img src="https://agentmods.dev/badge/skills/aleolidev/claude-react-kit/audit-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 490 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00490
Opus 5.5 $0.00006 $0.00196
Sonnet 5.5 $0.00003 $0.00098
Haiku 4.5 $0.00001 $0.00049

Measured 1mo ago against content hash e641bf905ad8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

audit-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/audit-architecture/SKILL.md · 65 lines

What it actually says

Architecture Audit

Perform a comprehensive audit of the codebase architecture. Check for:

1. Cross-Feature Imports

Search for any feature importing from another feature:

grep -rn "from.*@/features/" src/features/ --include="*.ts" --include="*.tsx" | while read line; do
  FILE=$(echo "$line" | cut -d: -f1)
  FEATURE=$(echo "$FILE" | sed -n 's|.*/features/\([^/]*\)/.*|\1|p')
  IMPORT=$(echo "$line" | grep -o "@/features/[^/]*" | sed 's|@/features/||')
  if [ "$FEATURE" != "$IMPORT" ]; then
    echo "VIOLATION: $line"
  fi
done

2. Core Domain Leakage

Check if core/ imports from features/ or shared/:

grep -rn "from.*@/features/\|from.*@/shared/" src/core/ --include="*.ts" --include="*.tsx"

3. Design System Purity

Check if design-system/ has business logic imports:

grep -rn "from.*@/features/\|from.*@/shared/" src/design-system/ --include="*.ts" --include="*.tsx"

4. Oversized Files

Find files exceeding 200 lines:

find src/ -name "*.tsx" -o -name "*.ts" | xargs wc -l | sort -rn | head -20

5. Empty Directories

find src/ -type d -empty

6. Duplicate Naming

Search for potential duplicate folders/files with different casings.

7. Components Fetching Data

Search for useQuery/useMutation inside component directories (not pages):

grep -rn "useQuery\|useMutation" src/features/*/components/ src/shared/components/ src/design-system/ --include="*.tsx"

Report all violations found with specific file paths and recommended fixes.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 65 lines · 14 tokens per session scan A e641bf905ad8

Subscribe to this mod's changes

audit-architecture is a skill published in the GitHub repository aleolidev/claude-react-kit (2 stars, last pushed 8mo ago), licensed MIT. It adds 14 tokens to every session and 490 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

code-quality-principles

Applies KISS, YAGNI, and SOLID principles for clean code with reduced complexity. Use when refactoring or reviewing code for over-engineering.

athola/claude-night-market · 38 tokens

readiness

Use when the user wants to analyze, audit, or assess their codebase for AI agent readiness. Also use for "readiness report", "how ready is my project", "analyze my codebase", "audit my repo", "check my setup", or "what should I improve".

jrenaldi79/harness-engineering · 62 tokens

compact-guard-clauses

Refactor deeply nested conditions into early-return guard clauses when doing so improves readability and preserves behavior.

alivirgo/Major-AI-Skills · 26 tokens

refactor

Automated iterative code refactoring with swarm-orchestrated specialist agents including deep codebase discovery, confidence-scored code review, and security analysis. Use this skill when the user wants to improve existing code quality, clean up messy code, restructure, simplify, reduce tech debt, or perform…

zircote-plugins/refactor · 112 tokens

design-patterns

Design Patterns, SOLID & Clean Architecture: Reference guide and advisor for software design patterns, SOLID principles, Clean Code practices, and Clean Architecture. Use whenever the user asks about design patterns, SOLID principles, Clean Code, Clean Architecture, DDD, refactoring, code organization, coupling…

camilooscargbaptista/cto-toolkit · 138 tokens

go-testing

Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.

Gentleman-Programming/gentle-ai · 26 tokens