# Build an instrument or effect

> Create a musical tool with an agent, shape its sound and controls, and bring it to your audience.

Canonical: https://maruaudio.com/help/building-instruments-and-effects
Documentation index: https://maruaudio.com/help/llms.txt

Decide what the player should be able to do, where they will use it and what you need to deliver. A playable bank, an editable module and an installed plugin require different work. Use this guide to choose a starting point before asking an agent to build.

## Choose the right starting point

An **instrument** makes sound from notes or other controls. An **effect** processes incoming audio. A **MIDI tool** changes musical events. A **sampler bank** organizes recordings, while a **rack** connects existing modules.

Use a bank when recordings and mappings are the product. Use a module when you need its own musical behavior or interface. [Racks and patches](https://maruaudio.com/help/racks-and-patches.md) can combine existing tools without turning each connection into a new instrument.

## Shape the sound and interface

In [Studio](https://maruaudio.com/help/studio-quick-start.md), work with an agent specialized in audio to build the instrument or effect you have in mind. Begin with your own idea or remix an existing module. Describe the character of the sound, the controls the player needs and where you want them to use it.

Refine the experience with concrete feedback: “keep the bass full when I turn up the drive” or “put the performance controls together.” Play the sound when playback is available and try the controls you are changing. The result remains an editable project that a developer can extend when you need a custom integration.

## Decide what happens online

A product can play prepared sounds without generating anything during a performance. It can also offer optional account-connected services.

[Creator apps](https://maruaudio.com/help/creator-apps.md) let you plan Maru sign-in and permitted account actions. [Generation in your products](https://maruaudio.com/help/generation-in-your-products.md) explains prepared sounds, user-funded generation and server integrations. Plan what the instrument does when the service is unavailable.

## Prepare a destination

Choose a browser experience, a supported native plugin or another agreed host. Check controls, saved settings, assets and playback in that destination. Native builds and delivery remain part of the selected-developer beta.

Continue with [publishing plugins](https://maruaudio.com/help/publishing-plugins.md), then [selling on Maru](https://maruaudio.com/help/selling-on-maru.md) if it will be a paid product. Developers can use the [capability map](https://maruaudio.com/docs/what-you-can-build.md) and the [local quickstart](https://maruaudio.com/docs/quickstart.md).