Learn by building. Every snippet runs.

Three paths

Start where you are.

C++ developer

A native app, a tool or a processor

Build the framework, wire your first composition root, then process audio headless.

1. Install and first build
2. Your first app
3. Headless DSP
4. Choose backends

Web and front-end

The interface in HTML, CSS and JavaScript

Drive the engine from a web page over the UI bridge: commands in, snapshots out.

1. Install and first build
2. A set list with a GO button
3. Read state
4. Theme your UI

With an AI assistant

Let a coding agent write it

Give it the map, ask in the framework's own terms, and let the checks catch its mistakes.

1. Building with an AI assistant
2. Add a command
3. Specs and requirement IDs

What is inside

Tutorials, how-to guides, concepts, reference.

TutorialsLearn by doing, from nothing to a working program.→How-to guidesGet one task done: a command, MIDI learn, plugins, sync, loudness, mobile.→ConceptsWhy the framework is shaped this way: cores, ports, commands, threads, time.→ReferenceModules, ports, specifications, decision records and the glossary.→

Start a project · build · test

# A compiling project, generated
cmake -D NAME=MyShow -D DIR=MyShow -P cmake/ShuffleEngineNewProject.cmake

# The pure cores alone, on any host
cmake --preset core-only
cmake --build --preset core-only
ctest --preset core-only

# With the adapters that need no JUCE
cmake --preset windows-msvc        # or macos, linux, ios, android
cmake --build --preset windows-msvc
ctest --preset windows-msvc

For coding agents too

A map before the territory.

• AGENTS.mdThe working rules, read first by people and agents alike.
• llms.txtEvery document, one line each.
• specs/<domain>.mdNumbered requirements with examples as data; tests cite their IDs.
• examples/Small programs CI builds and runs: copy the closest one.