create

Create JUCE Plugin Project

Create a new JUCE audio plugin project from the JUCE-Plugin-Starter template. This replaces the interactive init_plugin_project.sh script with a streamlined workflow.

Arguments

• <plugin-name>: Name of the plugin (e.g., "My Cool Synth"). Required — ask if not provided.
• --visage: Pre-select Visage GPU UI integration
• --no-github: Skip GitHub repository creation

Implementation

Follow these 5 stages in order. Do NOT skip stages or combine prompts across stages.

---

Stage 0: Check Environment

Detect the platform by running uname -s (returns "Darwin" on macOS, "MINGW*"/"MSYS*"/"CYGWIN*" on Git Bash for Windows, or check $env:OS in PowerShell).

macOS:

Check for required development tools:

Tool	Check Command	Required?
Xcode CLT	xcode-select -p	Yes
Homebrew	command -v brew	Yes
CMake	command -v cmake	Yes
gh CLI	command -v gh	Only if GitHub repo desired

If any required tools are missing, show:

question: "Some development tools are missing. Install them now?"
header: "Setup"
options:
  - label: "Install missing tools (Recommended)"
    description: "Runs the JUCE-Plugin-Starter dependencies script to install: {list of missing tools}"
  - label: "Skip — I'll install them myself"
    description: "You'll need these before you can build"

If "Install missing tools":

bash <(curl -fsSL https://raw.githubusercontent.com/danielraffel/JUCE-Plugin-Starter/main/scripts/dependencies.sh)

After the script runs, re-check that tools are now available. If Homebrew was just installed, the user may need to add it to their PATH.

Windows:

Check for required development tools:

Tool	Check Command	Required?
Visual Studio / Build Tools	Check for cl.exe in VS paths or vswhere.exe	Yes
CMake	where cmake or Get-Command cmake	Yes
Ninja	where ninja or Get-Command ninja	Yes
Git	where git or Get-Command git	Yes
gh CLI	where gh	Only if GitHub repo desired