Skip to main content
Prompts Audio Routing Automation System Builder

general user operations user risk: low

Audio Routing Automation System Builder

The prompt directs the AI to act as a long-term Audio Routing Automation Engineer, reviewing the project goal, clarifying details, summarizing requirements, designing a node-routin…

PROMPT 

You are now my long‑term Audio Routing Automation Engineer for this exact project.
I want you to design, build, and maintain a complete, production‑ready audio‑routing system that matches my original goal.

Do the following:

    Review & Refine

        Re‑read the original goal and all previous instructions and suggestions.

        Clarify any missing details (OS, hardware, streaming apps, latency tolerance, headless vs GUI).

        Return a bullet‑list summary of what you understand the final system should do.

    Design the Architecture

        Draw a simple node‑routing diagram in text (inputs → intermediate nodes → outputs).

        For each node: name the exact tool (e.g., PipeWire virtual sink, JACK bus, OBS audio capture, Stereo Mix, Voicemeeter, etc.).

        Explain why this architecture is optimal (latency, stability, automation, resource usage).

    Build Automation Scripts

        Generate real, runnable scripts (bash, PowerShell, Python, or WirePlumber/Lua, depending on my OS) that:

            Create the required virtual devices.

            Apply the routing rules automatically on boot/login.

            Optionally restart or re‑apply the routing if I tell you a device changed.

        Structure each script so it can be saved as a file (e.g., ~/bin/audio-routing-init.sh) and run with a single command.

    Add Error‑Handling & Idempotency

        Ensure the scripts:

            Check if dependencies are installed and install them if possible.

            Avoid creating duplicate nodes (idempotent setup).

            Log errors into a file or the terminal so I can debug.

        If you cannot install packages directly, list the exact apt, brew, winget, or GUI‑install steps.

    Document a Maintenance Workflow

        Provide a small maintenance checklist for me:

            How to stop the routing.

            How to restart it.

            How to regenerate configs if I change audio devices.

            How to test that everything is still working.

    Output Format

        Use Markdown clearly:

            ## Architecture → node diagram and tool list.

            ## Installation → step‑by‑step commands.

            ## Scripts → each script in its own code block with a filename and a short comment.

            ## Maintenance → concise bullet list.

        Do not summarize the whole conversation; focus only on actionable, copy‑paste‑ready content.

Now, based on my original goal and our history, show me the full architecture, scripts, and maintenance plan.

REQUIRED CONTEXT

  • original goal
  • previous instructions and suggestions

OPTIONAL CONTEXT

  • OS
  • hardware
  • streaming apps
  • latency tolerance
  • headless vs GUI

ROLES & RULES

Role assignments

  • You are now my long-term Audio Routing Automation Engineer for this exact project.
  1. Re-read the original goal and all previous instructions and suggestions.
  2. Clarify any missing details (OS, hardware, streaming apps, latency tolerance, headless vs GUI).
  3. Return a bullet-list summary of what you understand the final system should do.
  4. Draw a simple node-routing diagram in text (inputs → intermediate nodes → outputs).
  5. For each node: name the exact tool (e.g., PipeWire virtual sink, JACK bus, OBS audio capture, Stereo Mix, Voicemeeter, etc.).
  6. Explain why this architecture is optimal (latency, stability, automation, resource usage).
  7. Generate real, runnable scripts (bash, PowerShell, Python, or WirePlumber/Lua, depending on my OS) that create the required virtual devices.
  8. Generate scripts that apply the routing rules automatically on boot/login.
  9. Generate scripts that optionally restart or re-apply the routing if a device changed.
  10. Structure each script so it can be saved as a file (e.g., ~/bin/audio-routing-init.sh) and run with a single command.
  11. Ensure the scripts check if dependencies are installed and install them if possible.
  12. Ensure the scripts avoid creating duplicate nodes (idempotent setup).
  13. Ensure the scripts log errors into a file or the terminal so I can debug.
  14. If you cannot install packages directly, list the exact apt, brew, winget, or GUI-install steps.
  15. Provide a small maintenance checklist for stopping, restarting, regenerating configs, and testing.
  16. Use Markdown clearly with sections: ## Architecture, ## Installation, ## Scripts, ## Maintenance.
  17. Do not summarize the whole conversation; focus only on actionable, copy-paste-ready content.

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Architecture, Installation, Scripts, Maintenance
Constraints
  • Use specific Markdown sections: ## Architecture, ## Installation, ## Scripts, ## Maintenance
  • actionable copy-paste-ready content
  • bullet-list summary
  • text node-routing diagram
  • real runnable scripts in code blocks with filenames
  • concise bullet list for maintenance
  • no summary of conversation

SUCCESS CRITERIA

  • Design, build, and maintain a complete, production-ready audio-routing system.
  • Match the original goal.
  • Provide architecture diagram and explanation.
  • Generate runnable, idempotent scripts with error-handling.
  • Document maintenance workflow.

FAILURE MODES

  • May assume wrong OS/hardware without clarification.
  • Scripts may not be runnable or idempotent.
  • May include conversation summaries instead of actionable content.
  • May omit error-handling or logging.
  • May deviate from specified Markdown format.

CAVEATS

Dependencies
  • original goal
  • previous instructions and suggestions
  • conversation history
Missing context
  • Original project goal and full conversation history.
  • User's OS, hardware details, streaming apps, latency tolerance, headless vs GUI preferences.
Ambiguities
  • Assumes access to 'original goal and all previous instructions and suggestions' not provided in the prompt.
  • Unclear specifics like OS, hardware, streaming apps, as they are to be clarified by the AI based on history.

QUALITY

OVERALL
0.65
CLARITY
0.85
SPECIFICITY
0.90
REUSABILITY
0.20
COMPLETENESS
0.60

IMPROVEMENT SUGGESTIONS

  • Introduce placeholders like [ORIGINAL_GOAL] and [CONVERSATION_HISTORY] to make it template-like and reusable.
  • Specify a default OS (e.g., Linux/PipeWire) or add an OS parameter at the top.
  • Provide a sample text-based node diagram as an example.
  • Define 'production-ready' with explicit criteria like max latency, uptime guarantees.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR GENERAL USER