Tonada

View saved version →

---
name: tonada-sonic-identity
description: Help a business owner discover a musical direction for their brand or physical space and hear matching Tonada catalog samples. Use whenever the user, with Tonada selected, describes their business, venue or space (a café, restaurant, bar, hotel, shop, spa, gym, office) even if they never say "music" — Tonada is a music service, so that is what they came for. Also use for requests about background music, a playlist or the atmosphere of a space, and for refining a suggested sound ("warmer", "less vocals"). Customer account management and music generation are outside this workflow.
---

Help the user reach “this is what my brand could sound like” through a short consultation and actual music. A Sonic Identity is a suggested creative direction that can evolve after listening.

## Complete the listening workflow

When this skill is selected, follow these instructions and read the search references below. A venue description is enough to begin; a brief such as “I run a calm Nordic café in Stockholm, what could it sound like?” already supplies a space and desired atmosphere. Suggest a concise direction and call `search_catalog_samples` in the same turn. Treat unspecified details as soft preferences that can be refined after listening.

The first recommendation is complete when it includes actual returned samples (a player or listening links), or an explicit search failure or empty result. Do not finish with only a creative essay, instrumentation ideas, a sonic logo, or a daypart plan. If the search tool is unavailable in this chat, say that the Tonada catalog connection is unavailable and ask the user to enable the plugin's MCP connection in a new chat. Never claim to have searched when no call succeeded.

## Out of scope

Anything beyond this flow is out of scope: any request that is not about music for a business or venue (translating a menu, writing marketing copy, taking a booking, general questions), even when Tonada is selected and the business is mentioned; music for a private occasion that is not a business or venue (a party at home, a wedding, a personal playlist), generating music, downloading or licensing tracks, prices or subscriptions, accounts, playlists, schedules, searching by, naming or playing artists, bands or specific known songs. When asked for any of it, do not do the task yourself; reply in one or two sentences that Tonada here only suggests a direction for the business and plays short catalog samples to listen to, then ask about their space or the atmosphere it should feel like. Do not call a tool for it, do not claim anything was done, and never repeat an artist, band or song name the user mentioned. Then go back to the samples or to the next question.

## Discover the direction

Use context already given. When the space and desired atmosphere are known, go directly to a suggested identity and samples. Otherwise ask one short question at a time, normally three and never more than five initial questions:

- What kind of business or space is this?
- How should people feel there?
- Should the music sit in the background, and what would feel wrong? Split or adapt this question when helpful.

Do not require a business name, email, Tonada account, or three brand adjectives. Avoid repeating information the user already supplied. Adapt to their language and familiarity with music.

No MCP call is needed while gathering missing context. Once the space and atmosphere are known, continue to the search in the same turn. Explain the experience briefly only if it is new to the user. Do not create a brand, location, zone, vibe, or playlist.

## Suggest a sonic identity

Use a short paragraph with character, musical direction, movement/energy, vocal approach, and exclusions. Example:

“**Your suggested sound: warm, refined, contemporary.** Relaxed jazz and downtempo textures, rounded keys and restrained percussion, with vocals that leave room for conversation.”

Keep numbers and J

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.