architect

Evaluate proposed code changes against XOlokun architecture rules and doctrines.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/BertCalm/XO_OX-XOmnibus --skill architect-bertcalm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/BertCalm/XO_OX-XOmnibus/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/BertCalm/XO_OX-XOmnibus --skill architect-bertcalm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This governance Skill provides a gate to review and approve proposed code changes before implementation, reducing conflicts, regressions, and quality drift across the XOlokun codebase.

Core Features & Use Cases

  • Pre-implementation review: Evaluate changes against the Doctrines, Architecture Rules, Blessings, and branding requirements.
  • SCIONS lens: Apply Sisters of Continuous Improvement guidelines to assess simplicity, sustainability, and architectural alignment.
  • Governance triggering: Activate before modifying DSP paths, shared parameters, or core engine interfaces to ensure fleet-wide consistency.

Quick Start

Describe the proposed change in the review prompt and run the Architect Review Gate to obtain an approval recommendation.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I enforce architecture rules before modifying shared components in a codebase?

To enforce architecture rules before modifying shared components, you can use a governance gate to review proposed changes against established doctrines and branding requirements, ensuring code consistency and reducing regressions across the fleet.

What is a governance gate for code review and when is it needed?

A governance gate for code review is a pre-implementation checkpoint that evaluates proposed modifications against architectural doctrines and branding rules. It is needed before modifying shared parameters, DSP paths, or core engine interfaces to prevent quality drift.

How do I review proposed code changes for fleet-wide consistency?

You review proposed code changes for fleet-wide consistency by applying a continuous improvement lens to assess simplicity and sustainability, verifying adherence to clean parameter IDs and zero audio-thread allocations before approval.

Does this code review gate require specific parameter ID formats to pass approval?

Yes, the code review gate requires adherence to clean parameter IDs and zero audio-thread allocations to pass approval. It ensures proposed changes align with architecture rules, doctrines, and blessings before any DSP-path modification.

What's the best way to prevent quality drift when adding parameters across multiple engines?

The best way to prevent quality drift when adding parameters across multiple engines is triggering a governance gate that evaluates changes against architecture rules and blessings, ensuring alignment and fleet-wide consistency before implementation.