Stats
Actions
Tags
From example-skills
Applies modular synthesis principles like signal flow, patch points, and CV/audio distinctions to software system design, workflows, architectures, and data pipelines.
How this skill is triggered — by the user, by Claude, or both
Slash command
/example-skills:modular-synthesis-philosophyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Translate the wisdom of modular synthesis into system design and conceptual frameworks.
Translate the wisdom of modular synthesis into system design and conceptual frameworks.
In modular synthesis, every function is a discrete, replaceable unit with defined inputs and outputs. Apply this to:
The power isn't in the modules—it's in how they connect. A simple oscillator becomes complex through routing.
System design equivalent: APIs, interfaces, data contracts, message passing.
Modular synthesis distinguishes between:
System equivalent:
Synthesis philosophy: there are no mistakes, only unexpected results. Patching a clock into an audio input creates something.
Design equivalent: Embrace emergence. Systems can be recombined in ways designers didn't anticipate.
| Synthesis | System Equivalent |
|---|---|
| VCO (voltage-controlled oscillator) | Data source, API endpoint, sensor |
| LFO (low-frequency oscillator) | Scheduler, cron job, heartbeat |
| Noise source | Random generator, entropy source |
| Sample & Hold | Cache, state capture, snapshot |
| Synthesis | System Equivalent |
|---|---|
| VCF (voltage-controlled filter) | Data transformer, query filter |
| Lowpass filter | Noise reduction, smoothing, aggregation |
| Highpass filter | Change detection, delta extraction |
| Bandpass filter | Specific extraction, search query |
| Synthesis | System Equivalent |
|---|---|
| Envelope (ADSR) | Lifecycle management (init, active, decay, cleanup) |
| Sequencer | Workflow orchestrator, state machine |
| Quantizer | Validator, normalizer, type coercer |
| Slew limiter | Rate limiter, gradual rollout |
| Synthesis | System Equivalent |
|---|---|
| Mixer | Aggregator, combiner, merge function |
| VCA (voltage-controlled amplifier) | Gain control, feature flag, throttle |
| Multiple/Splitter | Fan-out, broadcast, pub/sub |
| Switch | Router, conditional, A/B test |
| Attenuator | Scaler, normalizer, reducer |
[Source] → [Process A] → [Process B] → [Output]
Simple, predictable, easy to debug. Each stage transforms and passes on.
When to use: ETL pipelines, request processing, assembly lines.
┌→ [Process A] →┐
[Source] [Mixer] → [Output]
└→ [Process B] →┘
Process the same signal differently, combine results.
When to use: A/B testing, redundancy, multi-format output.
[Source] → [Process] → [Output]
↑____________|
Output feeds back into input. Creates complexity, can create instability.
When to use: Iteration, learning systems, self-regulation. Warning: Needs attenuation or the system oscillates out of control.
[Osc A] ←→ [Osc B]
↓ ↓
[Mix] → [Output]
Two modules modulate each other. Creates complex, evolving behavior.
When to use: Emergent systems, creative AI, market dynamics.
Standard approach: Follow established patterns, use popular frameworks, minimize surprise.
Synthesis approach: Experiment with unconventional signal paths. The "wrong" patch might create something novel.
What are the signal generators in your system?
What transforms signals?
What controls behavior?
How do signals flow?
How do multiple signals combine?
┌─────────────┐
│ MODULE │
│ │
│ ○ CV In │ ○ = Input
│ ● Audio In │ ● = Output (filled)
│ ● Out │
└─────────────┘
Patch cables: ──────── (audio)
········ (CV/control)
references/module-mappings.md - Extended module-to-system translationsreferences/patch-diagrams.md - Example system diagrams in synthesis stylenpx claudepluginhub a-organvm/a-i--skills --plugin document-skillsProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.