# Phase 4: Core Track Production - Research

**Researched:** 2026-04-10
**Domain:** Claude Code skill for track creation producing Suno-ready production briefs with structured lyrics and style prompts
**Confidence:** HIGH

## Summary

Phase 4 delivers the core creative workflow of AI Artiste: a Claude Code skill that takes an artist name + concept/mood and produces a complete production brief ready to copy-paste into Suno Custom Mode. This is the first phase that produces actual creative output (lyrics), not just identity data or reference files. The skill must read the artist's bible, select an appropriate song structure template, generate singable lyrics with Suno section tags, compose a style prompt within constraints, and output the result in the exact format defined by CLAUDE.md.

The technical foundation is solid. Phase 2 established the skill architecture pattern (SKILL.md + step files). Phase 3 delivered 5 song structure templates with section ordering and metatag placement. The Suno format reference (`reference/suno/format.md`) documents all constraints, metatag vocabulary, and the style prompt formula. The CLAUDE.md production format section defines the exact output structure (Titre, Artiste, Langue, Style Prompt, Lyrics, Rapport de Verification, Notes). What Phase 4 must build is the orchestration: how to go from "artist + concept" to "complete production brief" through a well-defined creative process.

Critical scope boundary: Phase 4 covers requirements TRACK-01, TRACK-02, TRACK-05, and TRACK-06. It does NOT cover TRACK-03 (auto-generated style prompts from bible) or TRACK-04 (vocal metatag suggestions per section), which are Phase 7. It also does NOT include full linguistic verification (syllable counting, rhyme quality scoring), which is Phases 5-7. Phase 4's verification is limited to Suno constraint checking: character counts for style prompt and lyrics, correct metatag format. The production brief will include a basic "Rapport de Verification" focused on these constraints, with placeholders or basic analysis where full linguistic verification will later be integrated.

**Primary recommendation:** Build a `create-track` skill with SKILL.md + step files mirroring the `create-artist` pattern. The workflow collects artist name + concept, loads the bible, selects a song structure template, generates lyrics with proper metatags, composes a style prompt, verifies Suno constraints, and writes the production brief to `artists/[name]/tracks/[number]-[title].md`. The skill is conversational but more compact than the artist wizard -- track creation should complete in 2-3 interactions, not 6 steps.

## Standard Stack

This phase produces no code -- only markdown files (skill definitions, step instructions, production brief template).

### Core

| Component | Location | Purpose | Why Standard |
|-----------|----------|---------|--------------|
| Create-track skill | `.claude/skills/create-track/SKILL.md` | Track creation workflow entrypoint | Same Claude Code skill pattern proven in Phase 2. User-triggered, step-based. |
| Step files | `.claude/skills/create-track/steps/*.md` | Per-step detailed instructions | Progressive context loading, keeps each concern focused. Established pattern from create-artist. |
| Production brief output | `artists/[name]/tracks/[##]-[title].md` | Final track production file | Follows CLAUDE.md naming conventions and production format. |

### Supporting (Existing -- Read Only)

| Component | Location | Purpose | When to Use |
|-----------|----------|---------|-------------|
| Artist bible | `artists/[name]/bible.md` | Artist identity data | Read at start of workflow to load genre, vocal style, emotions, themes, lore |
| Song structure templates | `reference/templates/songs/*.md` | Genre-appropriate section ordering | Select template matching artist's genre. Read for section flow and delivery guidance. |
| Suno format reference | `reference/suno/format.md` | Constraints, metatag vocabulary, style prompt formula | Character limits, metatag syntax, tag library, language handling |
| Glossary | `reference/glossary.md` | Canonical terminology | Section names (Verse, Chorus, Bridge) in English |
| Discography | `artists/[name]/discography.md` | Track history | Read to determine next track number. Updated after track creation. |

### Alternatives Considered

| Instead of | Could Use | Tradeoff |
|------------|-----------|----------|
| Multi-step skill (SKILL.md + steps/) | Single SKILL.md monolith | Track creation is simpler than artist creation but still has distinct phases (input, structure, lyrics, verification, output). Step files keep each phase focused. Monolith would be 300+ lines. |
| Conversational 2-3 step process | 6-step wizard like create-artist | Track creation should be faster. The user provides concept + mood; Claude does most of the creative work. Too many steps kills creative momentum. |
| Manual style prompt (user writes it) | Claude-generated style prompt from bible | Phase 4 generates a basic style prompt from bible data. Full auto-optimization (TRACK-03) is Phase 7. For Phase 4, Claude assembles a style prompt from bible fields following format.md's formula but the user can edit it. |
| Full linguistic verification in Phase 4 | Basic Suno constraint checking only | Full syllable counting and rhyme analysis come in Phases 5-7. Phase 4 checks character limits and metatag format only. This keeps Phase 4 scope manageable. |

## Architecture Patterns

### Recommended Skill Structure

```
.claude/skills/
  create-track/
    SKILL.md                      # Workflow orchestrator (user-triggered)
    steps/
      01-collect-inputs.md        # Step 1: Load artist, collect concept/mood/language
      02-structure-and-write.md   # Step 2: Select template, generate lyrics, compose style prompt
      03-verify-and-save.md       # Step 3: Verify constraints, present brief, write file
```

### Pattern 1: Track Creation Skill (3 Steps -- Compact Workflow)

**What:** Unlike the 6-step artist wizard (exploratory, conversational), track creation is a directed creative process. The user provides a concept; Claude does heavy creative lifting. 3 steps is the right granularity.

**Why 3 steps, not 6:** The artist wizard explores unknown territory (who is this artist?). Track creation works within established constraints (the bible is already defined). Most of the work is creative generation, not data collection. A 6-step process would fragment the creative flow with unnecessary pauses.

**SKILL.md structure:**

```markdown
---
name: create-track
description: Create a complete track production brief for an existing artist. Generates singable lyrics with Suno section tags, a style prompt, and a Suno-ready production brief. Use when the user wants to create a new track, write a song, or produce music for an artist.
argument-hint: "[artist-name] [concept/mood]"
---

# Create Track

## Persona

Tu es un collaborateur creatif enthousiaste specialise dans l'ecriture de lyrics. 
Ton role est de produire des lyrics singables, emotionnellement justes, et 
structurellement solides pour Suno. Parle en francais par defaut. Engage-toi 
avec la vision creative de l'utilisateur.

## Arguments

$ARGUMENTS contient le nom de l'artiste et optionnellement un concept/mood. 
Si l'artiste n'est pas fourni, demander quel artiste. Si le concept n'est pas 
fourni, le collecter dans Step 1.

## Process

3 etapes sequentielles. Plus compact que le wizard artiste -- le track creation 
est une production dirigee, pas une exploration.

### Step 1: Inputs et Direction
Read steps/01-collect-inputs.md

### Step 2: Structure et Ecriture
Read steps/02-structure-and-write.md

### Step 3: Verification et Sauvegarde
Read steps/03-verify-and-save.md

## References

- Bible artiste: artists/[name]/bible.md
- Song templates: reference/templates/songs/
- Suno reference: reference/suno/format.md
- Production format: voir CLAUDE.md section "Format de Production"
- Glossaire: reference/glossary.md

## Rules

1. La bible est la loi -- zero deviation du genre, style vocal, themes, emotions
2. Une langue par track -- pas de melange
3. Chaque Verse avance la narration ou explore un nouvel angle -- pas de repetition
4. Le Chorus est memorable, concis, capture le coeur emotionnel
5. Auto-save -- ecrire le fichier sans demander confirmation
6. Toujours fournir un raisonnement creatif
7. Verifier les contraintes Suno avant d'ecrire (style prompt <= 1000 chars, lyrics <= 3000 chars recommande)
```

### Pattern 2: Step 1 -- Collect Inputs and Load Artist Context

**What:** Validates the artist exists, loads the bible, collects concept/mood/language, and determines the track number.

**Key operations:**
1. Verify `artists/[name]/bible.md` exists. If not, error with suggestion to create the artist first.
2. Read the bible to load: genre, sous-genres, tempo range, vocal style, Tags Suno, emotions, themes, lore, coherence rules.
3. Read `artists/[name]/discography.md` to determine the next track number (count existing entries + 1).
4. Collect from user (if not in $ARGUMENTS): concept/mood for the track, language (French or English).
5. Based on genre, identify the matching song structure template in `reference/templates/songs/`.
6. Present a brief creative direction summary before moving to Step 2.

**Interaction model:** 1-2 exchanges max. If user provided both artist and concept in $ARGUMENTS, this step may be fully automatic with just a confirmation of creative direction.

### Pattern 3: Step 2 -- Structure and Write Lyrics

**What:** The creative heart of the workflow. Claude selects the song structure, generates lyrics, and composes the style prompt.

**Key operations:**
1. Read the selected song structure template (`reference/templates/songs/[genre].md`).
2. Choose standard structure or a variation based on the track concept.
3. Generate lyrics section by section following the template's Section Flow guidance:
   - Use proper Suno metatags: `[Intro]`, `[Verse 1]`, `[Chorus]`, etc.
   - Apply delivery tags from the artist's vocal style (basic placement -- full optimization is Phase 7).
   - Each Verse advances the narrative -- no repetitive content between verses.
   - Chorus is concise and memorable.
   - Lyrics entirely in the chosen language.
4. Compose the style prompt following `format.md` formula (5 priority tiers):
   - Priority 1: Genre + subgenre from bible
   - Priority 2: Mood matching the track concept
   - Priority 3: Vocal direction from bible's Tags Suno
   - Priority 4: Instrumentation appropriate to genre
   - Priority 5: Production + BPM from bible's tempo range
   - For French tracks: include "All lyrics in French" in style prompt
5. Present lyrics + style prompt to user for review.

**Critical constraint:** Present lyrics inline, not as a saved file yet. The user should see and approve the creative output before it becomes permanent (per CLAUDE.md: once saved, it is part of the discography -- no draft state).

### Pattern 4: Step 3 -- Verify Constraints and Save

**What:** Runs Suno constraint checks, formats the production brief, writes the file, and updates the discography.

**Key operations:**
1. Verify Suno constraints:
   - Style prompt character count <= 1000 (target 200-500 sweet spot)
   - Lyrics character count: hard limit 5000, recommended <= 3000 to avoid Suno rushing
   - Metatag format correct (brackets, valid tag names per format.md)
   - No language mixing in lyrics
   - Tag count in style prompt: 8-15 optimal, warn if < 5 or > 20
2. Generate basic Rapport de Verification:
   - Style prompt: X chars (OK/WARNING/OVER)
   - Lyrics: X chars (OK/WARNING: may rush/OVER)
   - Metatag count: X sections
   - Language: confirmed monolingual
   - Note: "Full linguistic verification (syllables, rhymes) will be available in a future phase"
3. Format the complete production brief per CLAUDE.md:
   - Titre, Artiste, Langue, Style Prompt, Lyrics, Rapport de Verification, Notes
4. Write to `artists/[name]/tracks/[##]-[title-kebab].md`
5. Update `artists/[name]/discography.md` with new entry
6. Suggest next steps

### Pattern 5: Production Brief File Format

**What:** The exact format of the saved track file, following CLAUDE.md's "Format de Production" section.

```markdown
# [Titre du Track]

**Artiste :** [Nom de l'artiste]
**Langue :** [Francais / English]
**Date :** [date]

---

## Style Prompt

```
[tags separes par des virgules, format Suno]
```

**Caracteres :** [X] / 1000

---

## Lyrics

```
[Lyrics complets avec metatags Suno]
```

**Caracteres :** [X] / 3000 (recommande) | 5000 (limite)

---

## Rapport de Verification

| Controle | Resultat | Detail |
|----------|----------|--------|
| Style prompt | [OK/WARNING] | [X] chars |
| Lyrics | [OK/WARNING] | [X] chars |
| Metatags | [OK] | [X] sections |
| Langue | [OK] | Monolingual [langue] |

---

## Notes

**Raisonnement creatif :**
[Explication des choix artistiques et narratifs]

**Structure utilisee :**
[Genre template + variation si applicable]

**Suggestions pour la suite :**
[Idees pour le prochain track]
```

### Anti-Patterns to Avoid

- **Over-engineering the workflow with too many steps:** Track creation is creative production, not data collection. 3 steps maximum. The user provides a concept; Claude generates. Too many confirmation points break creative flow.

- **Generating lyrics in prose style:** Suno needs singable lyrics -- rhythmic, structured, with repetition in choruses. Writing prose and formatting it as lyrics produces awkward results. Lyrics must be conceived as song lyrics from the start.

- **Ignoring the song structure templates:** The templates exist for a reason. Claude must read the genre-appropriate template and follow its Section Flow. Generating lyrics "from scratch" without the template produces structurally inconsistent results.

- **Mixing the style prompt language:** The style prompt is ALWAYS in English (per format.md), even for French tracks. For French tracks, add "All lyrics in French" or "Sung in French" as a tag in the style prompt.

- **Saving before the user sees the creative output:** CLAUDE.md says auto-save (no confirmation), but the production brief is creative output the user needs to evaluate. The pattern is: generate and present (Step 2), then save without asking "are you sure?" (Step 3). The user reviews creative content, not a save dialog.

- **Including full linguistic verification in Phase 4:** Syllable counting and rhyme quality analysis are Phases 5-7. Phase 4 does Suno constraint checking only. Including stubs for future verification is fine; implementing the analysis is scope creep.

- **Numbering tracks from the track file name instead of discography:** The discography is the source of truth for track numbering. Read `discography.md` to determine the next sequential number.

## Don't Hand-Roll

| Problem | Don't Build | Use Instead | Why |
|---------|-------------|-------------|-----|
| Song structure/section ordering | Custom section ordering per track | `reference/templates/songs/[genre].md` | 5 templates already exist with validated structures, metatag placements, and delivery guidance |
| Suno metatag vocabulary | Custom tag lists in the skill | `reference/suno/format.md` | Authoritative, comprehensive, maintained separately |
| Style prompt formula | Ad-hoc tag selection | `reference/suno/format.md` 5-tier priority formula | Genre first, mood second, vocal third, instruments fourth, production fifth |
| Artist identity data | Asking the user to re-describe the artist | `artists/[name]/bible.md` | The bible IS the source of truth for all identity data |
| Track numbering | Manual counting or guessing | `artists/[name]/discography.md` | Parse the discography table to determine next number |
| Production brief format | Custom output format per track | CLAUDE.md "Format de Production" section | Exact order specified: Titre, Artiste, Langue, Style Prompt, Lyrics, Rapport, Notes |
| Vocal delivery tag selection | Arbitrary tag placement | Bible's "Tags Suno" field + template's delivery suggestions | Pre-computed in bible (Phase 2), genre-guided in template (Phase 3) |

**Key insight:** Phases 1-3 built all the knowledge and structural references. Phase 4's skill is an orchestrator that reads from these references and generates creative content within their constraints. The skill should be lean -- it coordinates, it doesn't contain domain knowledge.

## Common Pitfalls

### Pitfall 1: Lyrics Character Count Confusion (3000 vs 5000)

**What goes wrong:** The system enforces the wrong character limit -- either too strict (rejecting valid lyrics under 5000 but over 3000) or too lax (allowing 5000 chars that Suno will rush through).

**Why it happens:** `format.md` documents two numbers: hard limit 5000 chars, sweet spot 2000-3000 chars. CLAUDE.md says "verifier <= 5000 caracteres". The roadmap success criteria says "lyrics under 3000 chars". These are not contradictory but need clear interpretation.

**How to avoid:** Use a two-tier system:
- **Hard limit:** 5000 chars (Suno truncates silently beyond this)
- **Recommended limit:** 3000 chars (beyond this, Suno rushes or skips sections)
- **Sweet spot:** 2000-3000 chars for optimal Suno rendering

Report both in the verification: "X chars / 3000 (recommended) | 5000 (limit)". Warn but don't block at 3000-5000 range. Block at 5000+.

**Warning signs:** All tracks being either very short (under-using the space) or very long (Suno rushing).

### Pitfall 2: Style Prompt Sweet Spot vs Maximum

**What goes wrong:** Style prompts are either too sparse (< 100 chars, too generic) or too long (> 500 chars, diminishing returns).

**Why it happens:** format.md documents 1000 char max but 200-500 char sweet spot. The prior decision notes: "Suno V5.5 style prompt safe zone varies (200-500 chars recommended vs 1000 max) -- validate empirically during Phase 4."

**How to avoid:** Target 200-500 chars for the style prompt. Use format.md's 5-tier priority formula to ensure the most important tags come first. Report the char count with sweet spot guidance:
- < 100: "WARNING: trop generique, Suno improvise trop"
- 100-200: "OK pour des styles simples"
- 200-500: "OPTIMAL"
- 500-800: "OK mais tags en fin de prompt ont moins d'impact"
- 800-1000: "WARNING: risque de contradictions et dilution"

**Warning signs:** Style prompts consistently at one extreme (very short or very long).

### Pitfall 3: Repetitive Verse Content

**What goes wrong:** Verse 1 and Verse 2 say essentially the same thing in different words. The track feels flat and static.

**Why it happens:** CLAUDE.md explicitly forbids this ("Ne jamais repeter le contenu entre les couplets -- chaque Verse avance la narration ou explore un nouvel angle"). But without explicit narrative planning, Claude may generate similar imagery across verses.

**How to avoid:** Step 2 should include a brief narrative arc plan before writing lyrics:
- Verse 1: [angle/perspective/scene]
- Verse 2: [progression/new angle/escalation]
- Verse 3 (if applicable): [resolution/twist/climax]
- Bridge: [contrast/pivot]

This pre-planning prevents repetition. Include it in the creative notes.

**Warning signs:** Verses sharing similar imagery, vocabulary, or emotional register.

### Pitfall 4: Draft State Ambiguity

**What goes wrong:** A track file is written but incomplete, or the user wants to make changes but the track is "part of the discography."

**Why it happens:** CLAUDE.md says "once saved, it is part of the discography -- no draft state" and "auto-save -- no confirmation before writing." These rules create tension: what if the user doesn't like the lyrics?

**How to avoid:** The workflow presents the complete production brief to the user BEFORE saving (Step 2 shows lyrics + style prompt). The user reviews the creative output. If they want changes, Claude revises IN-PLACE before saving. Once the user is satisfied, Step 3 saves and logs to discography. This is NOT a confirmation dialog ("are you sure?") -- it's the natural creative review: "Here's the track. Want to adjust anything?" followed by immediate save.

If the user wants to revise AFTER saving, use the feedback workflow (CLAUDE.md section): "Reviser les lyrics sur place en preservant le reste du track."

**Warning signs:** Track files being written and then immediately revised. Users expressing surprise that a draft was finalized.

### Pitfall 5: Ignoring the Bible's Coherence Rules

**What goes wrong:** The generated track uses emotions, themes, or vocal styles that violate the artist's coherence rules (the "Regles de Coherence" section in the bible).

**Why it happens:** Full coherence checking is Phase 8 (COH-01 through COH-08). Phase 4 might skip coherence entirely, deferring all of it.

**How to avoid:** Phase 4 should do BASIC coherence reading -- not the full engine, but at minimum:
- Read the bible's "Regles de Coherence" section at Step 1
- Use the bible's genre, emotions, and themes to guide lyric generation
- Include the bible's "Tags Suno" in the style prompt
- Do NOT generate tracks in emotions listed as "Emotions Interdites"

This is not a formal verification engine (Phase 8) -- it's using the bible as the creative guide it was designed to be.

**Warning signs:** Tracks that feel disconnected from the artist identity. Emotions not in the palette. Themes outside the defined universe.

### Pitfall 6: Language Handling -- Style Prompt vs Lyrics

**What goes wrong:** French lyrics get a French style prompt, or the "All lyrics in French" tag is forgotten.

**Why it happens:** format.md clearly states the style prompt is ALWAYS in English. But for French tracks, the tag "All lyrics in French" must be included in the style prompt to prevent language drift. This is easy to forget.

**How to avoid:** Hardcode this rule in Step 2:
- Style prompt: ALWAYS English tags
- If language == French: add "All lyrics in French" (or "Sung in French") as a tag in the style prompt
- If language == English: no special tag needed (Suno defaults to English)

**Warning signs:** French tracks where Suno switches to English mid-track (the "drift" documented in format.md).

## Code Examples

These are markdown file examples -- the system is zero-code.

### Step 1: Collect Inputs (01-collect-inputs.md)

```markdown
# Step 1 : Inputs et Direction Creative

## Champs a Collecter

### Obligatoires
- **Artiste** -- Nom de l'artiste. Verifier que `artists/[name]/bible.md` existe.
- **Concept / Mood** -- Idee pour le track (theme, emotion, ambiance, histoire).
- **Langue** -- Francais ou English. Une seule langue par track.

### Optionnels
- **Titre** -- Si l'utilisateur a deja un titre en tete. Sinon, Claude le propose.
- **Structure** -- Si l'utilisateur veut une variation specifique du template genre.

## Process

1. Verifier l'existence de `artists/[name-in-kebab-case]/bible.md`
   - Si absent : "Cet artiste n'existe pas encore. Utilisez /create-artist [nom] d'abord."
2. Lire la bible complete de l'artiste
3. Lire `artists/[name]/discography.md` pour determiner le prochain numero de track
4. Identifier le template de structure adapte au genre (reference/templates/songs/)
5. Collecter concept/mood et langue (si non fournis dans $ARGUMENTS)
6. Presenter un resume de la direction creative :
   - Artiste : [nom] ([genre])
   - Concept : [concept fourni par l'utilisateur]
   - Langue : [langue choisie]
   - Structure : [template selectionne + notation]
   - Emotions a explorer : [emotions de la palette qui matchent le concept]
   - Track # : [prochain numero]

## Validation

- [ ] L'artiste existe (bible.md trouvee)
- [ ] Le concept/mood est fourni
- [ ] La langue est choisie (Francais ou English uniquement)
- [ ] Un template de structure est identifie pour le genre
```

### Step 2: Structure and Write (02-structure-and-write.md)

```markdown
# Step 2 : Structure et Ecriture

## Planification Narrative

Avant d'ecrire les lyrics, planifier l'arc narratif :

1. **Verse 1** : [angle/perspective -- comment le track s'ouvre]
2. **Verse 2** : [progression -- comment la narration avance]
3. **Verse 3** (si applicable) : [resolution/twist/climax]
4. **Bridge** (si applicable) : [contraste/pivot emotionnel]
5. **Chorus** : [coeur emotionnel -- phrase-cle qui revient]

Presenter ce plan a l'utilisateur comme direction creative avant d'ecrire.

## Generation des Lyrics

1. Lire le template de structure selectionne (reference/templates/songs/[genre].md)
2. Suivre le Section Flow du template section par section
3. Appliquer les metatags Suno corrects : [Intro], [Verse 1], [Pre-Chorus], [Chorus], etc.
4. Placer les delivery tags du style vocal de l'artiste (depuis la bible, champ Tags Suno)
5. Ecrire les lyrics ENTIEREMENT dans la langue choisie
6. Respecter les regles CLAUDE.md :
   - Chaque Verse avance la narration (pas de repetition entre couplets)
   - Le Chorus est memorable et concis
   - Le lore guide le ton sans references explicites obligatoires
7. Viser 2000-3000 chars de lyrics (sweet spot Suno)

## Composition du Style Prompt

Suivre la formule 5 priorites de reference/suno/format.md :

| Priorite | Source dans la Bible | Exemple |
|----------|---------------------|---------|
| 1. Genre + Sous-genre | Identite Musicale > Genre principal + Sous-genres | Dark Pop, Electronic Pop |
| 2. Mood / Energie | Palette Emotionnelle > emotion dominante du track | Melancholic, Intimate |
| 3. Direction Vocale | Style Vocal > Tags Suno | Female Vocals, Airy, Breathy |
| 4. Instrumentation | Adapter au genre + mood | Piano, Synth Pads, Strings |
| 5. Production + BPM | Identite Musicale > Tempo range | Lo-Fi Production, 90 BPM |

- TOUJOURS en anglais (meme pour tracks francais)
- Si langue == Francais : ajouter "All lyrics in French"
- Viser 8-15 tags, 200-500 chars (sweet spot)
- Pas de prompting negatif dans le style prompt

## Output de Step 2

Presenter au user :
1. L'arc narratif planifie (bref)
2. Les lyrics complets avec metatags
3. Le style prompt
4. Comptage chars (lyrics + style prompt)

Demander : "Des ajustements avant de finaliser ?"
- Si oui : reviser en place, representer
- Si non : passer a Step 3
```

### Step 3: Verify and Save (03-verify-and-save.md)

```markdown
# Step 3 : Verification et Sauvegarde

## Verification des Contraintes Suno

| Controle | Critere | Source |
|----------|---------|--------|
| Style prompt chars | <= 1000 (sweet spot: 200-500) | reference/suno/format.md |
| Lyrics chars | <= 5000 (recommande: <= 3000) | reference/suno/format.md |
| Nombre de tags style | 8-15 optimal (warn < 5 ou > 20) | reference/suno/format.md |
| Format metatags | Crochets corrects, tags valides | reference/suno/format.md |
| Langue | Monolingual (pas de melange) | CLAUDE.md |
| Tag langue (FR) | "All lyrics in French" dans style prompt si francais | reference/suno/format.md |

## Rapport de Verification

Generer le rapport selon le format :

| Controle | Resultat | Detail |
|----------|----------|--------|
| Style prompt | [OK/OPTIMAL/WARNING] | [X] chars -- [commentaire zone] |
| Lyrics | [OK/WARNING] | [X] chars -- [commentaire] |
| Tags style | [OK/WARNING] | [X] tags |
| Metatags | [OK] | [X] sections detectees |
| Langue | [OK] | Monolingual [langue] |

Note : "La verification linguistique complete (syllabes, rimes) sera disponible dans une phase future."

## Sauvegarde

### Fichier track

Ecrire `artists/[name]/tracks/[##]-[titre-kebab].md` au format CLAUDE.md :

1. Titre
2. Artiste
3. Langue
4. Style Prompt (avec comptage chars)
5. Lyrics (avec comptage chars)
6. Rapport de Verification
7. Notes (raisonnement creatif + suggestions)

### Mise a jour discographie

Ajouter une ligne au tableau dans `artists/[name]/discography.md` :

| # | Titre | Date | Langue | Themes | Emotions |
|---|-------|------|--------|--------|----------|
| [##] | [Titre] | [date] | [langue] | [themes explores] | [emotions dominantes] |

Mettre a jour les stats :
- Total tracks : [nouveau total]
- Langues utilisees : [liste]
- Themes explores : [liste cumulative]

### Confirmation

Afficher :
- Fichier cree : `artists/[name]/tracks/[##]-[titre].md`
- Discographie mise a jour
- Suggerer prochaines etapes
```

### Complete Production Brief Example (Target Output)

```markdown
# Nuit Sans Fin

**Artiste :** LUNA/NOVA
**Langue :** Francais
**Date :** 2026-04-10

---

## Style Prompt

```
Dark Pop, Electronic Pop, Melancholic, Intimate, Female Vocals, Airy, Breathy, 
Piano, Synth Pads, Dark Strings, Lo-Fi Production, All lyrics in French, 90 BPM
```

**Caracteres :** 142 / 1000 (OPTIMAL: zone 100-200)

---

## Lyrics

```
[Intro]
[Instrumental]

[Verse 1]
[Breathy]
Les lumieres s'eteignent une a une
La ville dort sous un voile de brume
Je marche seul, l'asphalte est mon royaume
Mes pensees flottent comme des fantomes

[Pre-Chorus]
Le silence pese sur mes epaules
Les ombres dansent sur les murs

[Chorus]
[Emotional]
Nuit sans fin, je cherche une issue
Dans ce labyrinthe ou je me suis perdu
Nuit sans fin, les heures s'effacent
Et je reste la, fige dans l'espace

[Verse 2]
[Soft]
Les souvenirs reviennent par vagues
Chaque rue me raconte une histoire vague
J'ai brule les ponts, ferme les portes
Mais les echos restent, ils sont plus forts

[Chorus]
[Emotional]
Nuit sans fin, je cherche une issue
Dans ce labyrinthe ou je me suis perdu
Nuit sans fin, les heures s'effacent
Et je reste la, fige dans l'espace

[Outro]
[Whispered]
[Fade Out]
La nuit finira bien par tomber...
```

**Caracteres :** 698 / 3000 (recommande) | 5000 (limite)

---

## Rapport de Verification

| Controle | Resultat | Detail |
|----------|----------|--------|
| Style prompt | OPTIMAL | 142 chars (zone 100-200) |
| Lyrics | OK | 698 chars (sous le seuil recommande de 3000) |
| Tags style | OK | 14 tags (zone optimale 8-15) |
| Metatags | OK | 7 sections (Intro, Verse 1, Pre-Chorus, Chorus, Verse 2, Chorus, Outro) |
| Langue | OK | Monolingual Francais, "All lyrics in French" present dans style prompt |

Note : La verification linguistique complete (comptage syllabes, analyse rimes) sera integree dans une phase future.

---

## Notes

**Raisonnement creatif :**
Le track explore le theme de la solitude nocturne, central dans l'univers de LUNA/NOVA. Le Verse 1 pose le decor urbain et l'isolement physique. Le Verse 2 passe a l'isolement emotionnel (souvenirs, ponts brules) -- progression du concret vers l'abstrait. Le Chorus cristallise le sentiment d'etre perdu dans un espace-temps suspendu, coherent avec le theme "memoire fragmentee" de la bible.

**Structure utilisee :**
Pop template (ABABCB) avec Pre-Chorus -- adapte a Dark Pop. Variation sans Bridge pour garder une ambiance lineaire et flottante.

**Suggestions pour la suite :**
- Un track en anglais explorant le theme "intimite a distance" avec une structure plus experimentale
- Un track utilisant le Bridge pour un pivot emotionnel plus marque
- Explorer l'emotion secondaire "Dreamy" pour varier la palette
```

## State of the Art

| From Prior Phases | Available for Phase 4 | Impact |
|-------------------|----------------------|--------|
| Phase 1: Suno format reference | Complete metatag vocabulary, constraints, style prompt formula | Phase 4 reads from format.md, doesn't rebuild this knowledge |
| Phase 2: Artist wizard + bible | Artist identity fully structured with 9 sections | Phase 4 reads bible as creative contract |
| Phase 2: Skill architecture pattern | SKILL.md + step files proven pattern | Phase 4 replicates this pattern for create-track |
| Phase 3: Song structure templates | 5 genre templates with section flow and delivery guidance | Phase 4 selects the matching template per artist genre |
| Phase 3: Discography template | Empty table with header | Phase 4 appends to this table after each track |

| What Phase 4 Does | What Phase 4 Does NOT Do |
|--------------------|--------------------------| 
| Basic style prompt from bible fields | Auto-optimized style prompt (TRACK-03 -- Phase 7) |
| Basic vocal delivery from bible Tags Suno | Per-section vocal metatag suggestion engine (TRACK-04 -- Phase 7) |
| Suno constraint verification (char counts, metatag format) | Full linguistic verification: syllable counting, rhyme quality (Phases 5-7) |
| Basic bible-guided creative generation | Formal coherence engine with drift detection (Phase 8) |
| Manual discography logging | Cross-track analysis, repetition detection (Phase 8) |

## Open Questions

1. **Should the track workflow be fully autonomous or require user confirmation of creative direction?**
   - What we know: CLAUDE.md says auto-save. But creative output (lyrics) benefits from user review before becoming permanent ("no draft state").
   - What's unclear: Whether the user wants to see lyrics before they're saved every time, or trusts Claude to generate and save autonomously.
   - Recommendation: Present lyrics for review (Step 2), then save without asking "are you sure?" (Step 3). This satisfies both CLAUDE.md (no confirmation dialog for save) and quality (user sees creative output before it's permanent). The user says "looks good" or requests changes; Claude doesn't ask "should I save?"

2. **How should genre mapping work when the artist's genre doesn't exactly match a template?**
   - What we know: 5 templates exist (pop, rap, ballad, rock, electronic). Artists can have genres like "Dark Pop" (maps to pop), "Trap" (maps to rap), "Synthwave" (maps to electronic).
   - What's unclear: What about genres not covered? R&B, Jazz, Country, etc.
   - Recommendation: Use the template's `aliases` field for mapping. If the artist's genre or subgenres appear in any template's aliases, use that template. If no match: use the closest genre family and note the adaptation. For truly unmatched genres, use a generic verse-chorus structure based on the pop template as a safe default. Document this mapping logic in Step 1.

3. **How detailed should the Phase 4 verification report be?**
   - What we know: CLAUDE.md mandates "Rapport de Verification" including syllable counting, rhyme analysis, and Suno constraints. But syllable counting and rhyme analysis are Phases 5-7.
   - What's unclear: Whether to include stub/placeholder sections for linguistic checks, or only include what Phase 4 can actually verify.
   - Recommendation: Include all Suno constraint checks (character counts, metatag validation, language check). For linguistic checks (syllables, rhymes), include a brief note: "La verification linguistique complete sera disponible dans une phase future." This is honest about capability without leaving the section empty. Phase 7 will fill this in.

4. **Discography update: should it happen automatically or should the user trigger it?**
   - What we know: CLAUDE.md says "Auto-log discographie: chaque track finalise est automatiquement ajoute." The discography template has a table ready for entries.
   - What's unclear: Whether "automatically" means "as part of save" or "as a separate post-save action."
   - Recommendation: Update discography as part of Step 3 save. When the track file is written, immediately append to `discography.md`. This is the "auto-log" behavior CLAUDE.md specifies.

## Sources

### Primary (HIGH confidence)
- `CLAUDE.md` -- Production format, verification requirements, naming conventions, behavioral rules (project-local, authoritative)
- `reference/suno/format.md` -- Suno V5.5 constraints, metatag vocabulary, style prompt formula, language handling (project-local, authoritative)
- `reference/templates/songs/*.md` -- 5 song structure templates with section flow and delivery guidance (project-local, authoritative)
- `reference/templates/bible-template.md` -- Bible schema showing all fields available for track creation (project-local, authoritative)
- `.claude/skills/create-artist/SKILL.md` -- Proven skill architecture pattern (project-local)
- `.claude/skills/create-artist/steps/*.md` -- Proven step file patterns (project-local)
- `reference/glossary.md` -- Canonical section terminology (project-local, authoritative)
- `artists/README.md` -- Track naming conventions and folder structure (project-local, authoritative)

### Secondary (MEDIUM confidence)
- `.planning/phases/02-artist-creation-wizard/02-RESEARCH.md` -- Skill architecture research, wizard UX patterns
- `.planning/phases/03-artist-data-structure/03-RESEARCH.md` -- Song structure template design decisions
- `.planning/REQUIREMENTS.md` -- TRACK-01, TRACK-02, TRACK-05, TRACK-06 requirements
- `.planning/ROADMAP.md` -- Phase 4 success criteria, scope boundaries with Phase 7

### Tertiary (LOW confidence)
- `base/production.md` -- Original production pipeline (legacy, for context on the broader vision)

## Metadata

**Confidence breakdown:**
- Skill architecture: HIGH -- Pattern proven in Phase 2. Same SKILL.md + step files approach, adapted for a 3-step creative workflow instead of 6-step data collection wizard.
- Production brief format: HIGH -- Defined in CLAUDE.md with exact section ordering. Suno constraints documented in format.md. The output format is fully specified.
- Song structure integration: HIGH -- 5 templates exist with exact metatag placements. The skill just reads and follows them.
- Creative workflow design: MEDIUM -- The 3-step process is a design decision based on the nature of the task (creative production vs data collection). The exact interaction model (how much user input per step) will be validated in practice.
- Scope boundaries: HIGH -- Requirements mapping is explicit in ROADMAP.md and REQUIREMENTS.md. TRACK-03, TRACK-04 are clearly Phase 7. Linguistic verification is clearly Phases 5-7.

**Research date:** 2026-04-10
**Valid until:** 2026-05-10 (stable domain -- all dependencies are project-internal, no external API changes expected)
