new-xo-project

Scaffold JUCE 8 audio plugin projects with CMake and XO_OX Designs architecture.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/BertCalm/xo-ox-claude-config --skill new-xo-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-xo-project
Source: https://github.com/BertCalm/xo-ox-claude-config/tree/main/skills/new-xo-project
Command: npx skills add https://github.com/BertCalm/xo-ox-claude-config --skill new-xo-project

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of new audio plugin projects using the JUCE framework, ensuring a consistent and robust architecture based on XO_OX Designs' best practices.

Core Features & Use Cases

  • Project Scaffolding: Generates a complete project structure with CMake, essential source files, and configuration.
  • Architecture Enforcement: Implements the proven XO_OX Designs architecture, including specific patterns and rules.
  • Use Case: A developer needs to start a new synthesizer plugin project. They can use this Skill to quickly set up a project that adheres to established coding standards and includes a solid foundation for audio processing and UI.

Quick Start

Use the new-xo-project skill to scaffold a new plugin named 'MySynth' with identity 'A versatile character synth' and code 'Mys'.

Frequently Asked Questions about new-xo-project

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

FAQPage Schema
How do I scaffold a new JUCE audio plugin project with CMake?

Scaffolding a new JUCE audio plugin project with CMake involves generating a complete directory structure, essential source files, and build configurations enforcing specific patterns like canonical parameter IDs.

Does this project scaffolding tool support AU and Standalone plugin formats?

Yes, this scaffolding tool supports creating AU and Standalone plugin formats, providing specific build configurations targeting C++17 and a macOS deployment target of 12.0.

What architecture rules are enforced for JUCE synth development?

Enforced architecture rules for JUCE synth development mandate canonical parameter IDs and prohibit heap allocation, mutex usage, and file I/O operations on the audio thread.

Can I use this to set up a synthesizer plugin with a specific project identity?

Yes, you can use this to set up a synthesizer plugin with a specific project identity by providing a plugin name, character description, and code prefix during the quick start scaffolding process.

What C++ standard and deployment target are configured for new JUCE CMake projects?

New JUCE CMake projects are configured with a C++17 standard and a macOS deployment target of 12.0 to ensure consistent environment compatibility and robust audio processing.