/mod-matrix-builder

Implement an 8-slot modulation matrix template for XO_OX engines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This template provides a reusable, doctrine-compliant 8-slot modulation matrix for XO_OX engines, eliminating boilerplate and ensuring consistent modulation routing across projects.

Core Features & Use Cases

  • Standardizes 8 modulation routes mapping LFOs, envelopes, velocity, and expression inputs to core destinations (filter, pitch, and timbre).
  • Accelerates engine development, code reuse, and doctrine compliance during new engine creation or refactors.
  • Use Case: when adding modulation depth, breathing, or expression support to a new engine, apply this matrix to satisfy D002, D005, and D006 in one pass.

Quick Start

Instantiate the mod-matrix-builder in your engine to wire the eight routes and verify D001–D006 compliance.

Frequently Asked Questions about /mod-matrix-builder

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

FAQPage Schema
How do I standardize modulation routing for LFOs and envelopes across multiple synthesizer engines?

You can standardize modulation routing by applying a reusable 8-slot modulation matrix template, ensuring LFOs, envelopes, velocity, and aftertouch map consistently to core destinations like filter, pitch, and timbre across projects.

What is an 8-slot modulation matrix and when do I need it for engine development?

An 8-slot modulation matrix is a standardized routing template mapping expression inputs to core destinations. You need it when creating or refactoring engines to eliminate boilerplate and ensure consistent modulation depth, breathing, and expression.

How do I implement a modulation matrix that satisfies D001 through D006 doctrine requirements?

To satisfy D001 through D006 doctrine requirements, instantiate an 8-slot modulation matrix template that maps LFOs, envelopes, velocity, mod wheel, and aftertouch to core destinations while providing Parameters.h and DSP integration templates.

Does this modulation matrix template support aftertouch and mod wheel routing for synthesis parameters?

Yes, the modulation matrix template supports aftertouch and mod wheel routing alongside LFOs, envelopes, and velocity, mapping these expression inputs directly to core synthesis destinations to ensure modulation depth and breathing.

Can I use this matrix template to refactor existing engines without breaking DSP integration?

Yes, you can use this template during engine refactors to standardize modulation routing and verify D001–D006 compliance, ensuring the DSP integration and Parameters.h templates remain consistent across your updated projects.

Why does my new engine lack consistent modulation depth and breathing across projects?

Your engine lacks consistency because it lacks a standardized 8-slot modulation matrix template to map expression inputs to core destinations, causing boilerplate and non-compliant routing across D001–D006 doctrine requirements.