agentleFS
aleolidevaleolidev/claude-react-kit/.claude/skills/audit-architecture/SKILL.md

audit-architecture

Skill2 starsChanged 9 months agoMITView on GitHub

Audit the codebase for architecture violations and organizational issues

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. ChariereFiedler/ronce-racine★ 9same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search for any feature importing from another feature:

    line 14
  2. Distinctive:

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

    line 28
  3. Distinctive:

    Check if design-system/ has business logic imports:

    line 35
  4. Distinctive:

    Search for potential duplicate folders/files with different casings.

    line 55
  5. Distinctive:

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

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.