Audit Domain 02 Architecture
Audit the architecture and code quality domain — module boundaries, abstraction layers, code organization, naming, documentation. Run as part of /audit Phase E.
Install
npx skills add wolverin0/claude-skills --skill audit-domain-02-architecturegit clone --depth 1 https://github.com/wolverin0/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/audit/audit-domain-02-architecture ~/.claude/skills/audit-domain-02-architecturePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Skill: Audit Domain 2 — Architecture & Code Quality This skill audits one specific domain. It runs in an isolated subagent context spawned by the audit-orchestrator. The subagent loads this skill and the audit rules, runs against the audit scope, and returns a ~2K-token findings report. ## Pre-flight ``` view @.claude/context/audit-rules.md ``` If you have findings from previous audit phases (hard stops, Tambon, blind spots), the orchestrator passes them as input. Use them — don't re-discover findings other phases already produced. Specifically: - Hard stops related to this domain: (none — this domain has no hard-stop classes routing to it) - Blind spots that route to this domain: B12 If the orchestrator didn't pass you these inputs, do NOT re-run the hard-stops or blind-spots walks. Audit your domain only and trust the orchestrator to stitch. ## Scope Module boundaries, layering, separation of concerns, dependency direction, abstraction quality, naming consistency, documentation, technical debt indicators. ## Key questions to answer For each, find the evidence and report it. The questions are the audit's spine — every finding maps back to one of them. 1. Do modules have clear single responsibilities, or are concerns mixed? 2. Is business logic separated from HTTP handling? 3. Is the dependency direction sane (UI → service → repo → DB), or does it cycle? 4. Are similar concerns (e.g., 'utility') consolidated, or scattered across utils/helpers/lib?
Details
- Skill name
audit-domain-02-architecture- Repository
- wolverin0/claude-skills
- Path
skills/audit/audit-domain-02-architecture/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the Audit Domain 02 Architecture skill do?
Audit the architecture and code quality domain — module boundaries, abstraction layers, code organization, naming, documentation. Run as part of /audit Phase E.
How do I install the Audit Domain 02 Architecture skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add wolverin0/claude-skills --skill audit-domain-02-architecture. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Audit Domain 02 Architecture popular?
It lives in wolverin0/claude-skills, which has 41 GitHub stars and 1 forks.
Related skills
UI UX Pro Max
41wolverin0/claude-skills
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism,
Audit Blind Spots
41wolverin0/claude-skills
Walk the B1-B19 AI-to-AI blind-spot catalog systematically. Use during the audit pipeline AFTER hard-stops and Tambon hunt and BEFORE the 13 domain audits. Output: PRESENT / NOT PRESENT for each B-class with evidence. Findings flow into the appropriate domains.
Audit Decisions
41wolverin0/claude-skills
Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.
Audit Domain 13 Code Integrity
41wolverin0/claude-skills
Audit code integrity and coherence — duplication, hallucinated references, Tambon signatures, spec drift, Frankenstein patterns, mystery code. THIS DOMAIN incorporates findings from the Tambon hunt and blind spots B9, B12, B13, B14. Run as part of /audit Phase E.
Athanor
45pjt222/agent-almanac
Four-stage alchemical code transmutation — nigredo (decomposition), albedo (purification), citrinitas (illumination), rubedo (synthesis) — with meditate and heal checkpoints between stages. Transforms tangled or legacy code into optimized, well-structured output through systematic material analysis. Use when transforming legacy code into modern equivalents, refactoring deeply tangled modules where incremental fixes keep failing, converting a codebase between paradigms, or when simpler refactoring approaches have stalled and a full-cycle transformation is needed.
Audit Method
41wolverin0/claude-skills
Run the methodology setup phase of a technical audit — fingerprint the stack, inventory the repository, and produce a system map. Use this BEFORE running any audit domains. Output: detected stack, repo summary, and high-level architecture in 3-5 paragraphs. No findings yet.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.