ai-master-architect

Audit architectural documents for inconsistencies and enforce constitutional invariants.

Updated Nov 8, 2025
One-click install
npx skills add https://github.com/wade56754/AI_ad_spend02 --skill ai-master-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-master-architect
Source: https://github.com/wade56754/AI_ad_spend02/tree/main/.claude/skills/ai-master-architect
Command: npx skills add https://github.com/wade56754/AI_ad_spend02 --skill ai-master-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves?

Ensuring architectural integrity and constitutional compliance in a complex system's documentation is critical, especially when dealing with conflicting definitions or ambiguous terminology. This Skill acts as a supreme architectural judge, reviewing, arbitrating, and structurally refactoring documents to enforce core invariants and eliminate risks.

Core Features & Use Cases

  • Constitutional Invariants Enforcement: Strictly verifies that no document violates core, unchangeable system principles (e.g., ledger balance rules).
  • Cross-Document Consistency Arbitration: Resolves conflicts and ensures consistency across entities, fields, states, and terminology in different documents.
  • Term Domain Firewall: Prevents ambiguous or multi-meaning terms from entering the system, flagging them as P0 issues.
  • Use Case: When a new STATE_MACHINE.md draft conflicts with the MASTER.md's constitutional invariants, use this Skill to identify the exact conflict, arbitrate the issue, and guide the necessary revisions to ensure compliance, preventing critical system failures.

Quick Start

Use ai-master-architect to review 'MASTER.md' for any constitutional invariant conflicts or terminology ambiguities.

Frequently Asked Questions about ai-master-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit architectural documents for compliance and consistency across MASTER.md, STATE_MACHINE.md, and related files?

Architectural auditing enforces compliance by reviewing documents for constitutional invariant violations and cross-document inconsistencies. This Skill identifies exact conflicts between state machines, ledgers, data schemas, and business rules, then guides necessary revisions to eliminate risks and ensure system integrity.

What does architectural invariant enforcement mean, and why does it matter for system design?

Constitutional invariants are unchangeable core principles that prevent critical system failures—like ledger balance violations. Invariant enforcement verifies every document respects these principles, catching conflicts early before they cascade through dependent systems.

How do I resolve terminology conflicts and ambiguity across multiple architecture documents?

Term domain firewall prevents ambiguous multi-meaning terms from entering the system by flagging them as P0 issues across all documents. This ensures strict terminology discipline, making causal chains auditable and preventing speculative logic from compromising data lineage.

Can I use architectural auditing to validate a new STATE_MACHINE.md against existing MASTER.md rules?

Yes. This Skill arbitrates conflicts between drafts and existing constitutional rules, identifying exact violations in your new state machine, then structurally refactoring it to comply with core invariants without breaking downstream business logic.

What output and evidence does architectural auditing produce for compliance validation?

Auditable outputs include exact conflict locations, violated invariants, terminology violations, and structural refactoring guidance. Results document immutable data lineage and provide evidence for governance review and risk containment.