> For the complete documentation index, see [llms.txt](https://docs.midi-mixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.midi-mixer.com/plugins/create-a-plugin/creating-a-plugin.md).

# Creating a plugin

MIDI Mixer provides a template plugin repository on GitHub which can be used to quickly bootstrap a new plugin and get started on the functionality.

{% embed url="<https://github.com/midi-mixer/plugin-template>" %}
The MIDI Mixer Template Plugin
{% endembed %}

The template above guides you through the steps. Once you've cloned and built your plugin with `npm install` and `npm run build:watch`, you should be able to refresh your MIDI Mixer plugins list and see your new plugin!

![The MIDI Mixer Template Plugin, viewed in the UI](/files/Xy6WDXE52rV9svLimtX2)

Continue with the following pages to see some information about some of the key files within the template plugin.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.midi-mixer.com/plugins/create-a-plugin/creating-a-plugin.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.