Skip to content
Skills Library
Marketing & content · Writing

loop-brief

/loop-brief

Write or revise the production brief for a Soundlines genre loop (docs/loops/briefs/<slug>.json): genre-authentic tempo, meter, key, bar count, seeds and an ACE-Step prompt with the required loop-form, mix and originality clauses, linted by check-brief.mjs. Use when planning a loop for a new genre, when a review says a loop is not idiomatic, has vocals, an intro, a breakdown or a muffled mix, or before any ACE-Step loop render.

Repository
soundlines ↗
Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/check-brief.mjs

What it does and when to use it

Write or revise the production brief for a Soundlines genre loop (docs/loops/briefs/<slug>.json): genre-authentic tempo, meter, key, bar count, seeds and an ACE-Step prompt with the required loop-form, mix and originality clauses, linted by check-brief.mjs. Use when planning a loop for a new genre, when a review says a loop is not idiomatic, has vocals, an intro, a breakdown or a muffled mix, or before any ACE-Step loop render.

Arguments

/loop-brief Genre id or slug, e.g. "genre:amapiano", plus any review feedback to address
Original author description

Write or revise the production brief for a Soundlines genre loop (docs/loops/briefs/<slug>.json): genre-authentic tempo, meter, key, bar count, seeds and an ACE-Step prompt with the required loop-form, mix and originality clauses, linted by check-brief.mjs. Use when planning a loop for a new genre, when a review says a loop is not idiomatic, has vocals, an intro, a breakdown or a muffled mix, or before any ACE-Step loop render.

How it works

  1. Schema
  2. Procedure
  3. Revising after review
Original SKILL.md headings · 68 lines, 601 words
SKILL.md preview
---
name: loop-brief
description: 'Write or revise the production brief for a Soundlines genre loop (docs/loops/briefs/<slug>.json): genre-authentic tempo, meter, key, bar count, seeds and an ACE-Step prompt with the required loop-form, mix and originality clauses, linted by check-brief.mjs. Use when planning a loop for a new genre, when a review says a loop is not idiomatic, has vocals, an intro, a breakdown or a muffled mix, or before any ACE-Step loop render.'
argument-hint: 'Genre id or slug, e.g. "genre:amapiano", plus any review feedback to address'
---

# Write a loop brief

A brief is everything ACE-Step receives. It owns **what the loop should sound like**; rendering is
`loop-produce`, measurement is `loop-validate`, the ship decision is `loop-review`.
The reference is [docs/loops/briefs/turntable-hip-hop.json](../../../docs/loops/briefs/turntable-hip-hop.json): it
produced the shipped hip-hop loop, so copy its structure and density.

## Schema

```jsonc
{
  "slug": "amapiano",                 // file name, asset name
  "genre": "genre:amapiano",          // must exist in src/data/graph.json
  "asset": "public/loops/amapiano.wav", // optional; this is the default
  "bpm": 112,                         // integer felt-beat tempo, 60-180
  "meter": 4,                         // ACE-Step time signature: 2, 3, 4 or 6 (beats per bar)
  "key": "F minor",                   // "<A-G>[#|b] major|minor"
  "bars": 4,                          // 2, 4 or 8
  "duration": 36,                     // seconds rendered; ≥ loop + 14 s, ≤ 60
  "seeds": [ ... 5 unique ints ... ],
  "prompt": "...",                    // 400-1600 chars, see below
  "notes": "why these choices, with sources"
}
```

## Procedure

1. **Ground the genre.** `node .github/skills/graph-edit/scripts/lookup.mjs genre:<slug>` for the
   graph description, period and key artists (as context only). Check tempo range, meter, signature
   instruments and groove against a serious source (GRAPH.md §6 standards); cite it in `notes`.
   Reuse the catalogue brief in `docs/previews/briefs/*.json` as a starting point if one exists.
2. **Choose musical parameters.** A typical, central tempo (not the genre extreme); a key the genre
   commonly uses; `bpm` and `meter` count the *felt* beat, because the extractor's beat tracker follows
   it. Compound feels (6/8, 12/8) are written as `meter: 2` or `4` at the dotted-quarter BPM; waltzes
   are `meter: 3`. Only `meter: 4` is verified end to end, so draft first for anything else.
   Beatless genres (ambient, drone, free improvisation) are out of scope for beat-grid loops; say so
   and stop.
3. **Write the prompt as one paragraph with five parts**, in this order (see the reference):
   1. *Identity*: `Original instrumental <era/region> <genre>, <bpm> BPM, <time signature>, <key>.`
   2. *Groove and parts*: drums/percussion pattern, bass relation to the kick, one memorable original
      motif and its instrument, and where space is left. Concrete performance verbs, not adjectives.
   3. *Loop form*: `Repeat a coherent four-bar groove with subtle variations, keep the rhythm section
      fully present from the opening beat through the middle, no intro, no breakdown, no fade-out.`
   4. *Mix*: transients, low end (controlled, mono-compatible), stereo image, saturation, "not muffled".
   5. *Originality*: `Entirely instrumental: no singing, no speech, no vocal samples. All melodies and
      performances newly composed.` Add genre-specific bans (e.g. "no pre-recorded scratching", "no MC").
4. **Never** name artists, tracks, labels' signature records, or write "in the style of"; describe the
   musical traits instead. The linter blocks graph artist/track names.
5. **Pick five fresh seeds** for a new brief. When revising a brief after review, keep the seeds that
   produced good takes and replace the bad ones.
6. **Lint**: `node .github/skills/loop-brief/scripts/check-brief.mjs docs/loops/briefs/<slug>.json`
   must PASS. Any prompt or meta change invalidates planned codes (by design).

## Revising after review

For a source-conditioned arrangement of an existing original Soundlines loop, add
`arrangement: { source: "public/loops/<slug>.wav", strength: 0.75 }`.
Keep the source tempo, key, melody, bar count and phrase position explicit in the prompt.
The arrangement pipeline preserves the source's fitted duration exactly rather than cutting
an independently timed loop. Cite the original source and intended instrumentation changes in
`notes`; source conditioning is not a guarantee of melody preservation.

Map each review finding to one prompt change and record it in `notes`: vocals → stronger bans and
remove vocal-associated words ("soulful", "hook", "chant"); intro/breakdown → loop-form sentence earlier
and "from the opening beat"; muffled → mix paragraph; wrong groove → name the pattern placement
(beats, offbeats, swing). Change one thing at a time when possible so the next take isolates it.
Files in this package (2)
  • SKILL.md 5 KB
  • scripts/check-brief.mjs 4 KB

Versions

The database has no other skills named loop-brief.

Database snapshot: 13.11.2026 · package version 146779ca2142 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100loop-produce
    Render a pro-quality seamless genre loop with the local ACE-Step 1.5 install from an approved brief (docs/loops/briefs/<slug>.json): server lifecycle, two-phase 4B-LM planning + XL SFT DiT rendering at 80 steps, take screening, grid-snapped loop extraction and export to…
  • 90loop-review
    Gate a Soundlines genre loop before it ships: judges genre authenticity against the brief, musical quality, hidden vocals or artefacts from spectrograms, originality and imitation risk, loop feel and provenance consistency, on top of the loop-validate result, then requests a…
  • 100genre-creator
    Create new genre documentation files for the bitwize-music genre library. Use when the user wants to add a genre, says "/genre-creator", "neues Genre erstellen", "Genre hinzufuegen", "add genre", or asks to create genre documentation. Takes a genre name as argument.
  • 100ace-step
    Generate, inpaint, and outpaint music with ACE Step on RunComfy via the `runcomfy` CLI. ACE Step is StepFun-AI's open-weights music foundation model — tag-driven composition (genre, mood, instruments), multilingual lyrics with section markers, 5 s to 4 min stereo output,…
  • 95local-song
    Co-write and produce an original full song with sung vocals entirely on the user's own machine — no API keys, no cost — with ACE-Step 1.5 (acestep.cpp), then clean up the vocal, master it and render a karaoke lyric video. The user shapes the song (genre, mood, story, voice,…
  • 100scenario-ace-step
    Use when creating or editing music with ACE-Step models on Scenario via MCP: text-to-music songs with sung vocals from a lyric sheet, instrumental tracks, covering or restyling an existing song, repainting one section in place, changing sung lyrics, adding an instrument layer,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.