noizefield
28 verified skills6,720 total stars
.kilocode/skills/skill_implementation
# SKILL: DSP IMPLEMENTATION **Goal:** Implement audio processing where parameters control DSP **Focus:** PluginProcessor.h, PluginProcessor.cpp **Output Location:** `plugins/[Name]/Source/` --- ## 📊 PHASE 4: CODE (DSP Implementation) **Trigger:** `/impl [Name]` (after DESIGN phase complete) **Input:** Reads `plugins/[Name]/status.json` and `.ideas/parameter-spec.md` **Prerequisites:** Architecture plan complete, UI framework selected **State Validation:** ```powershell # Import state manage
tools240
.claude/skills/debug
--- name: skill_debug description: Autonomous Debugging Instructions for Visual Studio Code: for [plugin]. --- ## Purpose This document defines a **self-directed debugging workflow** for a Large Language Model (LLM) operating inside or alongside **Visual Studio Code: (VS Code:)**. The goal is for the LLM to: 1. Inspect a codebase without human intervention 2. Identify likely failure points 3. Insert breakpoints programmatically 4. Generate a valid VS Code: `launch.json` debugging configuratio
tools240
skill_design
Create the Visual Interface for audio plugins. Use when user mentions UI design, mockup, WebView interface, or requests 'design UI for [plugin]'.
tools240
.claude/skills/dream
# SKILL: IDEATION & DREAMING **Goal:** Define the plugin concept and initialize the project state. **Trigger:** `/dream [Name]` **Output Location:** `plugins/[Name]/` ## ⛔ OUTPUT RESTRICTIONS (MANDATORY) * **NO C++ Code.** * **NO Build Scripts.** * **NO CMake configurations.** ## STEP 1: THE INTERVIEW **Do NOT generate files yet.** If the user prompt is vague, ask 3 clarifying questions: 1. **Sonic Goal:** What is the character? (e.g., "Dirty Tape Delay", "Clean EQ") 2. **Controls:**
tools240
.claude/skills/plan
# SKILL: ARCHITECTURE & PLANNING **Goal:** Define DSP architecture, complexity assessment, and implementation strategy **Trigger:** `/plan [Name]` **Input:** Reads `plugins/[Name]/.ideas/creative-brief.md` and `parameter-spec.md` **Output Location:** `plugins/[Name]/.ideas/` --- ## 🎯 PHASE 2: PLAN (Architecture & Strategy) **Prerequisites:** - `plugins/[Name]/.ideas/creative-brief.md` exists - `plugins/[Name]/.ideas/parameter-spec.md` exists - Phase 1 (DREAM) complete **Output Files:** - `p
tools240
.claude/skills/ship
# SKILL: PACKAGING (Cross-Platform) **Goal:** Create professional, cross-platform plugin installers for Windows, macOS, and Linux **Trigger:** `/ship [Name]` or "Ship [Name]" **Prerequisites:** Phase 4 (CODE) complete, audio engine working, all tests passed **Output Location:** `dist/[Name]_v[version]/` --- ## Overview This skill handles the complete packaging and distribution process for APC plugins. It supports: - **Local builds** (current platform only) - **GitHub Actions builds** (cross
tools240
.agent/skills/skill_debug
--- name: skill_debug description: Autonomous Debugging Instructions for Visual Studio Code: for [plugin]. --- ## Purpose This document defines a **self-directed debugging workflow** for a Large Language Model (LLM) operating inside or alongside **Visual Studio Code: (VS Code:)**. The goal is for the LLM to: 1. Inspect a codebase without human intervention 2. Identify likely failure points 3. Insert breakpoints programmatically 4. Generate a valid VS Code: `launch.json` debugging configuratio
tools240
.kilocode/skills/skill_debug
--- name: skill_debug description: Autonomous Debugging Instructions for Visual Studio Code: for [plugin]. --- ## Purpose This document defines a **self-directed debugging workflow** for a Large Language Model (LLM) operating inside or alongside **Visual Studio Code: (VS Code:)**. The goal is for the LLM to: 1. Inspect a codebase without human intervention 2. Identify likely failure points 3. Insert breakpoints programmatically 4. Generate a valid VS Code: `launch.json` debugging configuratio
tools240
juce-webview-windows
Quick-start guide for building JUCE 8 audio plugins with WebView2 UIs on Windows. Covers essential setup, critical member ordering, and step-by-step implementation workflow.
tools240
juce-webview-windows
Quick-start guide for building JUCE 8 audio plugins with WebView2 UIs on Windows. Covers essential setup, critical member ordering, and step-by-step implementation workflow.
tools240
.kilocode/skills/skill_ideation
# SKILL: IDEATION & DREAMING **Goal:** Define the plugin concept and initialize the project state. **Trigger:** `/dream [Name]` **Output Location:** `plugins/[Name]/` ## ⛔ OUTPUT RESTRICTIONS (MANDATORY) * **NO C++ Code.** * **NO Build Scripts.** * **NO CMake configurations.** ## STEP 1: THE INTERVIEW **Do NOT generate files yet.** If the user prompt is vague, ask 3 clarifying questions: 1. **Sonic Goal:** What is the character? (e.g., "Dirty Tape Delay", "Clean EQ") 2. **Controls:**
tools240
.agent/skills/skill_packaging
# SKILL: PACKAGING (Cross-Platform) **Goal:** Create professional, cross-platform plugin installers for Windows, macOS, and Linux **Trigger:** `/ship [Name]` or "Ship [Name]" **Prerequisites:** Phase 4 (CODE) complete, audio engine working, all tests passed **Output Location:** `dist/[Name]_v[version]/` --- ## Overview This skill handles the complete packaging and distribution process for APC plugins. It supports: - **Local builds** (current platform only) - **GitHub Actions builds** (cross
tools240
.agent/skills/skill_planning
# SKILL: ARCHITECTURE & PLANNING **Goal:** Define DSP architecture, complexity assessment, and implementation strategy **Trigger:** `/plan [Name]` **Input:** Reads `plugins/[Name]/.ideas/creative-brief.md` and `parameter-spec.md` **Output Location:** `plugins/[Name]/.ideas/` --- ## 🎯 PHASE 2: PLAN (Architecture & Strategy) **Prerequisites:** - `plugins/[Name]/.ideas/creative-brief.md` exists - `plugins/[Name]/.ideas/parameter-spec.md` exists - Phase 1 (DREAM) complete **Output Files:** - `p
tools240
.kilocode/skills/skill_planning
# SKILL: ARCHITECTURE & PLANNING **Goal:** Define DSP architecture, complexity assessment, and implementation strategy **Trigger:** `/plan [Name]` **Input:** Reads `plugins/[Name]/.ideas/creative-brief.md` and `parameter-spec.md` **Output Location:** `plugins/[Name]/.ideas/` --- ## 🎯 PHASE 2: PLAN (Architecture & Strategy) **Prerequisites:** - `plugins/[Name]/.ideas/creative-brief.md` exists - `plugins/[Name]/.ideas/parameter-spec.md` exists - Phase 1 (DREAM) complete **Output Files:** - `p
tools240
.agent/skills/skill_testing
# SKILL: TESTING **Goal:** Stability Check. ## TASKS 1. **Pluginval:** Run validation script. 2. **Crash Analysis:** If crash reported, read Documents/APC_CRASH_REPORT.txt. 3. **Manual Check:** Ask user to load in DAW and move knobs.
tools240
.kilocode/skills/skill_testing
# SKILL: TESTING **Goal:** Stability Check. ## TASKS 1. **Pluginval:** Run validation script. 2. **Crash Analysis:** If crash reported, read Documents/APC_CRASH_REPORT.txt. 3. **Manual Check:** Ask user to load in DAW and move knobs.
tools240
.claude/skills/skill_troubleshooting
# SKILL: TROUBLESHOOTING & ISSUE RESOLUTION ## STEP 1: CHECK KNOWN ISSUES FIRST **Before trying random solutions:** ```powershell # Search known issues database $errorPattern = "duplicate target juce" $knownIssues = Get-Content ..claude\troubleshooting\known-issues.yaml | ConvertFrom-Yaml $matches = $knownIssues.issues | Where-Object { $_.error_patterns -match $errorPattern } if ($matches) { Write-Host "✓ Known issue found: $($matches.title)" Write-Host "Resolution: $($matches.re
testing240
.agent/skills/skill_ideation
# SKILL: IDEATION & DREAMING **Goal:** Define the plugin concept and initialize the project state. **Trigger:** `/dream [Name]` **Output Location:** `plugins/[Name]/` ## ⛔ OUTPUT RESTRICTIONS (MANDATORY) * **NO C++ Code.** * **NO Build Scripts.** * **NO CMake configurations.** ## STEP 1: THE INTERVIEW **Do NOT generate files yet.** If the user prompt is vague, ask 3 clarifying questions: 1. **Sonic Goal:** What is the character? (e.g., "Dirty Tape Delay", "Clean EQ") 2. **Controls:**
tools240
.agent/skills/skill_troubleshooting
# SKILL: TROUBLESHOOTING & ISSUE RESOLUTION ## STEP 1: CHECK KNOWN ISSUES FIRST **Before trying random solutions:** ```powershell # Search known issues database $errorPattern = "duplicate target juce" $knownIssues = Get-Content ...agent\troubleshooting\known-issues.yaml | ConvertFrom-Yaml $matches = $knownIssues.issues | Where-Object { $_.error_patterns -match $errorPattern } if ($matches) { Write-Host "✓ Known issue found: $($matches.title)" Write-Host "Resolution: $($matches.re
testing240
.claude/skills/impl
# SKILL: DSP IMPLEMENTATION **Goal:** Implement audio processing where parameters control DSP **Focus:** PluginProcessor.h, PluginProcessor.cpp **Output Location:** `plugins/[Name]/Source/` --- ## 📊 PHASE 4: CODE (DSP Implementation) **Trigger:** `/impl [Name]` (after DESIGN phase complete) **Input:** Reads `plugins/[Name]/status.json` and `.ideas/parameter-spec.md` **Prerequisites:** Architecture plan complete, UI framework selected **State Validation:** ```powershell # Import state manage
tools240
skill_design
Create the Visual Interface for audio plugins. Use when user mentions UI design, mockup, WebView interface, or requests 'design UI for [plugin]'.
tools240
juce-webview-windows
Quick-start guide for building JUCE 8 audio plugins with WebView2 UIs on Windows. Covers essential setup, critical member ordering, and step-by-step implementation workflow.
tools240
.agent/skills/skill_implementation
# SKILL: DSP IMPLEMENTATION **Goal:** Implement audio processing where parameters control DSP **Focus:** PluginProcessor.h, PluginProcessor.cpp **Output Location:** `plugins/[Name]/Source/` --- ## 📊 PHASE 4: CODE (DSP Implementation) **Trigger:** `/impl [Name]` (after DESIGN phase complete) **Input:** Reads `plugins/[Name]/status.json` and `.ideas/parameter-spec.md` **Prerequisites:** Architecture plan complete, UI framework selected **State Validation:** ```powershell # Import state manage
tools240
.claude/skills/test
# Test - Plugin Testing & Validation **Trigger:** `/test [PluginName]` **Phase:** Testing (can run after Implementation) **Primary Skill:** `.claude\skills\skill_testing\SKILL.md` --- ## EXECUTION When invoked, execute the complete workflow from: **`.claude\skills\skill_testing\SKILL.md`** ## WORKFLOW GATES See `.claude\workflows\test.md` for: - Prerequisites (requires completed Implementation phase) - Test procedures - Validation criteria ## PARAMETERS - `PluginName` - Name of existing
tools240
.kilocode/skills/skill_troubleshooting
# SKILL: TROUBLESHOOTING & ISSUE RESOLUTION ## STEP 1: CHECK KNOWN ISSUES FIRST **Before trying random solutions:** ```powershell # Search known issues database $errorPattern = "duplicate target juce" $knownIssues = Get-Content ...kilocode\troubleshooting\known-issues.yaml | ConvertFrom-Yaml $matches = $knownIssues.issues | Where-Object { $_.error_patterns -match $errorPattern } if ($matches) { Write-Host "✓ Known issue found: $($matches.title)" Write-Host "Resolution: $($matches
development240
.kilocode/skills/skill_packaging
# SKILL: PACKAGING (Cross-Platform) **Goal:** Create professional, cross-platform plugin installers for Windows, macOS, and Linux **Trigger:** `/ship [Name]` or "Ship [Name]" **Prerequisites:** Phase 4 (CODE) complete, audio engine working, all tests passed **Output Location:** `dist/[Name]_v[version]/` --- ## Overview This skill handles the complete packaging and distribution process for APC plugins. It supports: - **Local builds** (current platform only) - **GitHub Actions builds** (cross
tools240
.claude/skills/skill_testing
# SKILL: TESTING **Goal:** Stability Check. ## TASKS 1. **Pluginval:** Run validation script. 2. **Crash Analysis:** If crash reported, read Documents/APC_CRASH_REPORT.txt. 3. **Manual Check:** Ask user to load in DAW and move knobs.
tools240
skill_design
Create the Visual Interface for audio plugins. Use when user mentions UI design, mockup, WebView interface, or requests 'design UI for [plugin]'.
tools240