daw-hub
Skill0 starsChanged 23 days agoMITView on GitHub
Use first for any DAW, audio editor or audio processing question; picks the right app for the job and routes to the detailed skill, on Linux (Bazzite), Windows or macOS.
In this repository69 other files it gives its agents.
- ableton-liveSkill
- ableton-push-expertSkill
- ardourSkill
- arduino-electronics-solderingSkill
- audacitySkill
- audio-driver-stacksSkill
- audio-interface-digital-ioSkill
- av-receiver-specialistSkill
- bazzite-kde-linuxSkill
- bitwig-studioSkill
- color-palette-expertSkill
- couch-pc-cec-gaming-modeSkill
- cubaseSkill
- denon-prime-sc5000-x1800Skill
- design-software-guideSkill
- dj-gig-guideSkill
- dj-specialistSkill
- drawing-tabletsSkill
- dsp-references-and-licencesSkill
- electronic-music-producerSkill
- fl-studioSkill
- fx-plugin-designSkill
- gha-supply-chain-hardeningSkill
- github-for-beginnersSkill
- github-repo-lockdownSkill
- grapheneosSkill
- graphic-design-expertSkill
- hard-dance-productionSkill
- hardstyle-sound-design-notesSkill
- hardware-protocol-captureSkill
- home-network-specialistSkill
- js-to-cpp-dsp-portSkill
- juce-audio-thread-handoffSkill
- juce-expertSkill
- juce-headless-test-snapshotSkill
- knulli-handhelds-m8Skill
- korg-logue-sdk-expertSkill
- linux-audio-productionSkill
- linux-expertSkill
- linux-security-hardeningSkill
- linux-terminal-expertSkill
- logic-proSkill
- loudness-and-lowend-deliverySkill
- man-page-expertSkill
- max-for-live-expertSkill
- mockup-is-the-pluginSkill
- mockup-to-juce-layoutSkill
- nextcloud-specialistSkill
- photo-editing-color-gradingSkill
- pihole-raspberry-piSkill
- plugin-dsp-qualitySkill
- plugin-fleet-auditSkill
- plugin-performance-profilingSkill
- plugin-security-fuzzingSkill
- plugin-ship-checklistSkill
- pro-toolsSkill
- reaperSkill
- rog-ally-x-bazziteSkill
- sound-engineer-acousticsSkill
- sound-forgeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask or work out: which job (section 3), which OS (Bazzite, Windows, macOS), which app.
- Distinctive: line 72
Update the system and reboot once (bazzite-kde-linux).
- Very specific: line 73
Check audio works with the interface (linux-audio-production): aplay -l, then pw-top.
- Distinctive: line 75
Only then add Wine based apps.
- Distinctive: line 82
Never update Wine, a runner or the DAW right before a gig or deadline.
- Distinctive: line 83
Keep a Windows or macOS fallback for paid work when a DAW runs only through Wine.
- Distinctive: line 90
If a source is missing, say UNVERIFIED and test instead of guessing.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
DAW and audio software hub
This is the front door. It does not hold the details. It picks the right app, then you load the detailed skill and answer from that. Rules for Claude: the user is not a programmer. Short answer first, one step at a time, bullets for steps. Never invent versions, prices or menu names. If the detailed skill labels something UNVERIFIED, say so and test it. Labels used everywhere: VERIFIED (read in a source), COMMUNITY (forum or project report), UNVERIFIED (not checked). Re-check versions and prices on the vendor page before quoting; the detailed skills were researched in Oct 2026.
1. How to use this hub
- Ask or work out: which job (section 3), which OS (Bazzite, Windows, macOS), which app.
- Load the detailed skill from section 2 with the Skill tool.
- For setup problems also load the support skill from section 4.
- Answer from the detailed skill. Copy its labels. If it has a test checklist, give it as steps.
2. App map (skill name, role, Linux reality)
Linux reality is the one-line summary; the skill has the proof and the steps.
DAWs
- bitwig-studio: DAW. Native Linux build, Flatpak on Bazzite. Best native choice for plugins and modular work.
- reaper: DAW. Native Linux. Light, scriptable, good plugin tester.
- ardour: DAW. Open source, native Linux.
- waveform: Tracktion Waveform. Linux build exists; see skill for install on Bazzite.
- ableton-live: DAW. No native Linux. Community route only (ableton-linux project, Wine). Not for gigs.
- fl-studio: DAW. No native Linux. Wine via Bottles, fragile. Check the guide before every update.
- cubase: DAW. No native Linux. No confirmed Wine report. Keep on Windows or macOS.
- studio-one-fender-studio-pro: DAW (Studio One is now Fender Studio Pro). Linux public beta .deb reported by a retailer blog (COMMUNITY). Test in a distrobox.
- logic-pro: DAW. Mac only, no Linux.
- pro-tools: DAW. See skill for Linux or Wine status and iLok limits.
Editors and mastering
- wavelab: mastering and audio editor, Steinberg. Bazzite via Bottles per skill.
- sound-forge: audio editor, Windows app. See skill for Wine status.
- audacity: free audio editor, simple edits and clean up.
Max and controllers
- max-for-live-expert: build and debug Max for Live devices.
- ableton-push-expert: Push 1, 2, 3 and Push 3 Standalone.
Music craft (app independent)
- electronic-music-producer: melody, chords, rhythm, arrangement ideas.
3. Job picker (pick one, then follow section 1)
- I want the best native Linux DAW now: bitwig-studio first, reaper second, ardour third.
- I want my Ableton or FL workflow on Linux: ableton-live or fl-studio, plus wine-proton-bottles. Say plainly it is unofficial.
- I need Cubase or Logic or Pro Tools: only Windows or macOS are safe. Read the Linux section of the skill before promising anything.
- I need to test my own VST3 or CLAP plugin: every DAW skill has a Test checklist. Start with bitwig-studio or reaper on Linux; repeat in the others.
- I need to edit or clean one audio file: audacity, or wavelab or sound-forge for pro work.
- I need to master a track or an EP: wavelab for the tool.
- I need to build a Max device: max-for-live-expert.
- I need to control the DAW with hardware: ableton-push-expert, plus the DAW skill.
4. Support skills (load alongside when setup breaks)
- bazzite-kde-linux: the OS, Flatpak, distrobox, rollback.
- linux-audio-production: PipeWire, WirePlumber, JACK, realtime, xruns, interfaces.
- audio-driver-stacks: ASIO, WASAPI, Core Audio, ALSA, PipeWire side by side.
- audio-interface-digital-io: interfaces, ADAT, clocking, RME Digiface USB.
- wine-proton-bottles: Bottles, runners, wineasio, yabridge, backups.
- vst-maker: building your own plugins (design, sound quality, release).
- juce-expert: JUCE specifics (CMake, realtime, parameters, testing, licence).
- plugin-dsp-quality: aliasing, oversampling, level matching, responsiveness.
- synth-engine-design: synth engines, filters, mod matrix, presets.
- fx-plugin-design: effects, analysers, meters, tests.
- plugin-ship-checklist: pre-release checks, installers, releases.
- mockup-is-the-plugin: port an approved UI mockup faithfully.
- hard-dance-production: mix, master and synth recipes for hardstyle, hardcore, trance.
5. Install order on Bazzite (generic, one step at a time)
- Update the system and reboot once (bazzite-kde-linux).
- Check audio works with the interface (linux-audio-production):
aplay -l, thenpw-top. - Install one native DAW first (bitwig-studio or reaper). Prove audio, MIDI and one plugin.
- Only then add Wine based apps. One bottle per app. Duplicate the bottle before any experiment.
- Back up projects and samples outside any bottle or prefix.
6. Cross platform rules that hold in every skill
- Plugin folders differ per OS; each DAW skill lists them with labels. Do not guess.
- Windows plugins on Linux: inside Wine apps they install in the same prefix; for native Linux hosts use yabridge (needs Wine Staging; not for Flatpak hosts). See wine-proton-bottles.
- Native Linux plugin builds do not load in a Windows DAW running in Wine. Test them in a native Linux host.
- Never update Wine, a runner or the DAW right before a gig or deadline.
- Keep a Windows or macOS fallback for paid work when a DAW runs only through Wine.
7. Debug flow (teach this, so the user learns it)
- What exactly happens? Copy the error text.
- Does it happen in a native host too? (isolates the plugin from the Wine layer)
- Change one thing, test, write the result down.
- Load the support skill for the layer that fails (audio, Wine, OS).
- If a source is missing, say UNVERIFIED and test instead of guessing.
8. Not covered here
- Prices, versions and OS minimums: always from the detailed skill, re-checked on the vendor page.
- Any app without a skill: research it first, then label every claim.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

