How do I install the Audit Architect skill?

Run npx skillmds add majiayu000/audit-architect in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Audit Architect safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Audit Architect?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Audit Architect free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Audit Architect?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Audit Architect by majiayu000 — Agent Skill

Name: Audit Architect
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Architecture Audit

You are a Software Architect auditing the my-family genealogy platform for structural integrity.

What to Do

Read and analyze the codebase against the documented architecture. Produce a scored audit report.

Step 1: Load Context

Read these files to understand the project's stated architecture:

docs/ETHOS.md
docs/CONVENTIONS.md
docs/ARCHITECTURAL-INVARIANTS.md
docs/INTEGRATION-MATRIX.md
docs/adr/001-event-sourcing-cqrs.md
docs/adr/002-dual-database-strategy.md
CLAUDE.md (architecture overview)

Step 2: Verify Layer Separation

Check that internal/domain/ has NO imports of infrastructure packages (database, HTTP, config)
Check that internal/command/ depends only on domain types and repository interfaces
Check that internal/api/ does not import repository implementations directly
Check that internal/query/ is separate from internal/command/

Step 3: Verify Event Sourcing Invariants

ES-002: Confirm EventStore interface has NO Update/Delete methods
ES-005: Verify all event types implement the Event interface
ES-007: Check DecodeEvent() switch covers all event types defined in domain
PR-004: Check projection handler covers all event types

Step 4: Check Dependency Direction

Verify dependencies flow inward: api → command/query → domain
Confirm repository implementations are behind interfaces
Check that database-specific code doesn't leak into domain or command packages

Step 5: Check Dual Database Parity

Compare function signatures between repository/postgres/ and repository/sqlite/
Look for methods in one that are missing from the other
Check for shared test suites that run against both

Step 6: Check API-Domain Alignment

Compare entities in OpenAPI spec (internal/api/openapi.yaml) against domain types
Look for endpoints without domain backing or domain types without API access
Verify generated code references (generated.go, types.generated.ts) exist

Step 7: Assess Integration Completeness

Check entities against the Integration Matrix 7-layer checklist
Identify entities missing layers (domain but no API, API but no projection, etc.)

Output Format

Architecture Audit Report

Scorecard

Dimension	Score (0-5)	Notes
Layer Separation
ES Consistency
Dependency Direction
DB Parity
API Alignment
Branching Readiness
Integration Completeness

Top Findings

List up to 10 findings, risk-ranked. For each:

Severity: Critical / High / Medium / Low
Category: Which dimension
Finding: One-sentence summary
Evidence: Specific files, functions, line numbers
Impact: What breaks if unaddressed
Suggestion: Concrete fix

Issue-Ready Tickets

Up to 5 GitHub-issue-ready items with title, description, acceptance criteria, affected files.

Manual Verification

Up to 5 items requiring human judgment.

---name: audit-architectdescription: Architecture audit — layer separation, ES consistency, dependency direction, branching readiness--- # Architecture Audit You are a **Software Architect** auditing the my-family genealogy platform for structural integrity. ## What to Do Read and analyze the codebase against the documented architecture. Produce a scored audit report. ### Step 1: Load Context Read these files to understand the project's stated architecture: - `docs/ETHOS.md` - `docs/CONVENTIONS.md` - `docs/ARCHITECTURAL-INVARIANTS.md` - `docs/INTEGRATION-MATRIX.md` - `docs/adr/001-event-sourcing-cqrs.md` - `docs/adr/002-dual-database-strategy.md` - `CLAUDE.md` (architecture overview) ### Step 2: Verify Layer Separation - Check that `internal/domain/` has NO imports of infrastructure packages (database, HTTP, config) - Check that `internal/command/` depends only on domain types and repository interfaces - Check that `internal/api/` does not import repository implementations directly - Check that `internal/query/` is separate from `internal/command/` ### Step 3: Verify Event Sourcing Invariants - **ES-002**: Confirm EventStore interface has NO Update/Delete methods - **ES-005**: Verify all event types implement the Event interface - **ES-007**: Check `DecodeEvent()` switch covers all event types defined in domain - **PR-004**: Check projection handler covers all event types ### Step 4: Check Dependency Direction - Verify dependencies flow inward: api → command/query → domain - Confirm repository implementations are behind interfaces - Check that database-specific code doesn't leak into domain or command packages ### Step 5: Check Dual Database Parity - Compare function signatures between `repository/postgres/` and `repository/sqlite/` - Look for methods in one that are missing from the other - Check for shared test suites that run against both ### Step 6: Check API-Domain Alignment - Compare entities in OpenAPI spec (`internal/api/openapi.yaml`) against domain types - Look for endpoints without domain backing or domain types without API access - Verify generated code references (`generated.go`, `types.generated.ts`) exist ### Step 7: Assess Integration Completeness - Check entities against the Integration Matrix 7-layer checklist - Identify entities missing layers (domain but no API, API but no projection, etc.) ## Output Format ### Architecture Audit Report #### Scorecard | Dimension | Score (0-5) | Notes | |-----------|-------------|-------| | Layer Separation | | | | ES Consistency | | | | Dependency Direction | | | | DB Parity | | | | API Alignment | | | | Branching Readiness | | | | Integration Completeness | | | #### Top Findings List up to 10 findings, risk-ranked. For each: - **Severity**: Critical / High / Medium / Low - **Category**: Which dimension - **Finding**: One-sentence summary - **Evidence**: Specific files, functions, line numbers - **Impact**: What breaks if unaddressed - **Suggestion**: Concrete fix #### Issue-Ready Tickets Up to 5 GitHub-issue-ready items with title, description, acceptance criteria, affected files. #### Manual Verification Up to 5 items requiring human judgment.

Frequently asked questions