# Any creative app

> Carry Kwark's approach into another craft, such as music, animation, theatre, comics, games or podcasts, without importing film-specific assumptions: find the craft's own paper, its own units and its own conventions, then build them as one act.

Source: https://kwark.space/designSystem/kits/any-creative-app

## Who it is for

Teams building tools for any craft where a person makes something of their own: songwriting and music production, animation, theatre and stage management, comics, game narrative, podcasts, choreography, architecture sketchbooks. The other kits are about film. This one is about how to take Kwark's way of working into a craft it was not designed for.

## The method, in five steps

### 1. Find the craft's paper

Every craft has a physical artefact its people already trust: the screenplay page, the stripboard, the call sheet, the index card. Music has the lead sheet and the chord chart; theatre has the prompt book and the rehearsal report; animation has the exposure sheet (X-sheet); comics have the thumbnail and the script page; podcasts have the run sheet. Find it before drawing a screen, and build the screen as that artefact (Decision 0005: paper and digital together). The structured data is what the paper already holds.

### 2. Find the craft's units

Film counts pages in eighths and time in `HH:MM:SS:FF`. Other crafts count differently: bars and beats at a tempo; frames on twos (animation drawn every second frame at 24 fps); cues and scenes; panels and pages; spreads; minutes and segments. Use the craft's own unit everywhere, label it, and never convert it into a unit the craft does not use.

### 3. Find who owns each fact

One document owns each fact. In theatre the script owns lines, the stage manager's prompt book owns cues, the rehearsal report owns what changed today. Bind every control to the owner, and carry facts forward rather than retyping them (the breakdown writes the sheet; the cast list feeds the call sheet).

### 4. Decide what a machine may do

Measure, find, carry and convert; never judge or put words, notes or frames into the work without the person choosing them (Decision 0002). Read [AI and authorship](https://kwark.space/designSystem/foundations/ai-and-authorship.md).

### 5. Build the phone for the moment the craft uses it

Film's phone moments are the recce, the set at 6 a.m. and the train ride home with the script. Find your craft's: the rehearsal room, the gig, the studio between takes. Design the phone for that moment, content first (Decision 0016).

## Mapping Kwark's components to other crafts

| Kwark component | Music | Theatre | Animation | Comics | Podcasts |
|---|---|---|---|---|---|
| [Screenplay page](https://kwark.space/designSystem/components/screenplay-page.md) | Lyric sheet | Prompt book page | Script | Script page | Script, run sheet |
| [Index card](https://kwark.space/designSystem/components/index-card.md) | Section (verse, chorus) | Scene or French scene | Sequence | Page or panel beat | Segment |
| [Story spine](https://kwark.space/designSystem/components/story-spine.md) | Song structure | Acts | Sequences | Issue structure | Episode rundown |
| [Script timeline](https://kwark.space/designSystem/components/script-timeline.md) | Arrangement in bars | Running time | Edit length in frames | Page count | Running time |
| [Stripboard strip](https://kwark.space/designSystem/components/stripboard-strip.md) | Session plan | Rehearsal schedule | Production schedule by shot | Page schedule | Recording schedule |
| [Call sheet](https://kwark.space/designSystem/components/call-sheet.md) | Session sheet | Rehearsal call | Daily assignments | Not used | Recording call |
| [Storyboard frame](https://kwark.space/designSystem/components/storyboard-frame.md) | Not used | Blocking sketch | Storyboard, layout | Thumbnail | Not used |
| [Waveform](https://kwark.space/designSystem/components/waveform.md) | Tracks | Sound cues | Dialogue track for lip sync | Not used | Tracks |
| [Script revision diff](https://kwark.space/designSystem/components/script-revision-diff.md) | Arrangement changes | Script changes in rehearsal | Script changes | Script changes | Edits |

## Live demo

The same components, used for a song: sections as cards on the paper, a structure strip, and a session plan in rows.

```html
<nav class="kw-spine" aria-label="The song at a glance"><ul class="kw-spine__strip"><li style="flex-grow:20"><button class="kw-spine__act" type="button" style="--kw-act:var(--k-cal-writing)" aria-label="Intro and verse 1, 3 sections"><span class="kw-spine__band"><span class="kw-spine__part"><i></i><i></i><i></i></span></span><span class="kw-spine__name">Verse 1</span><span class="kw-spine__meta">16 bars</span></button></li><li style="flex-grow:15"><button class="kw-spine__act" type="button" style="--kw-act:var(--k-cal-rehearsal)" aria-label="Chorus, 8 bars"><span class="kw-spine__band"><span class="kw-spine__part"><i></i></span></span><span class="kw-spine__name">Chorus</span><span class="kw-spine__meta">8 bars</span></button></li><li style="flex-grow:20"><button class="kw-spine__act" type="button" style="--kw-act:var(--k-cal-recce)" aria-label="Verse 2, 16 bars"><span class="kw-spine__band"><span class="kw-spine__part"><i></i><i></i></span></span><span class="kw-spine__name">Verse 2</span><span class="kw-spine__meta">16 bars</span></button></li></ul><p class="kw-spine__total">3 sections · 40 bars at 92 bpm</p></nav>
<article class="kw-index-card" data-tint="green" aria-label="Verse 2, the drive home"><div class="kw-index-card__top"><span>Track 3 · Section 3</span></div><h3 class="kw-index-card__title">Verse 2: the drive home</h3><p class="kw-index-card__body">Strip the drums back to brushes.</p><div class="kw-index-card__foot"><span class="kw-index-card__landing">1:42</span><span>Bars 33–48</span></div></article>
<div class="kw-table-wrap"><table class="kw-table kw-table--dense"><caption class="kw-visually-hidden">Session plan, Saturday</caption><thead><tr><th scope="col">Time</th><th scope="col">Track</th><th scope="col">Parts</th><th scope="col">Players</th></tr></thead><tbody><tr><td class="num">10:00</td><td>3 · Drive home</td><td>Drums, bass</td><td>Ravi, Ana</td></tr><tr><td class="num">13:30</td><td>3 · Drive home</td><td>Vocal</td><td>Mira</td></tr></tbody></table></div>
```

## Conventions you must look up, not invent

The system's rule for every kit is that domain conventions are stated accurately or not at all. When you apply Kwark to a new craft:

- **Must** find the craft's own standards from its practitioners, unions, guilds or standards bodies, and cite them in your decision record. For example: tempo and time signature in music notation; the X-sheet's frame columns in animation; the stage manager's cue naming (often LX for lighting and SQ or Sound for sound cues in UK practice, with numbering conventions that differ by company); comics script formats that differ by publisher.
- **Never** present one company's habit as an industry standard. Where practice varies, say *conventions vary* and make it a setting.
- **Always** ask two or three practitioners before building a multi-screen flow, then walk the journey and get the UX agreed (memory: UX before build; few questions, then decide and build).

## Keyboard map

Start from Kwark's shared map and add the craft's own transport and element keys.

| Key | Does everywhere |
|---|---|
| ⌘ S | Says *Saved*; saving is continuous |
| ⌘ Z / ⇧ ⌘ Z | Undo / redo |
| ⌘ F | Find |
| ⌘ K | [Command palette](https://kwark.space/designSystem/components/command-palette.md) |
| Esc | Close the open menu, sheet or panel and return focus |
| Space, J, K, L | Transport, wherever there is time |
| ? | Keyboard shortcuts |

Menus are desktop-grade with five at the top level where possible (Decision 0015) and shortcuts shown in items. Read [Menus and shortcuts](https://kwark.space/designSystem/patterns/menus-and-shortcuts.md).

## Phone and desktop

- **Phone:** one 44px header line (back, a one-word title, at most two labelled actions, *Menu ▾*), content by about y = 200, one floating control, menus as sheets that drill down one page at a time (Decision 0016). Read [Phones](https://kwark.space/designSystem/patterns/phones.md).
- **Desktop:** the craft's paper at its true geometry, panels beside it, keyboard first.

## AI and authorship

The rules are the same in every craft:

- **Never** score, grade, rank or judge the work or the artist (Decision 0002). No "song strength", no "panel composition score", no streaks.
- **Never** save machine-made words, notes, frames or values into the work. Mark them with the [Revision mark](https://kwark.space/designSystem/components/revision-mark.md) and a source until the person accepts or edits them.
- **May** measure, find, carry and convert. Say what ran, where, and on what data.
- **Never** send the work to a model provider by default. Private is the default (Decision 0001); every outward step is chosen, explained and reversible.
- **Never** imitate a real artist's voice, likeness or style on request without their documented consent.

## Before you ship

- The craft's paper prints, and the printout matches the screen.
- Every unit is labelled.
- Nothing judges the work.
- The phone layout works at 320px and 375px.
- A decision record explains each convention you adopted and its source (see [Decision records](https://kwark.space/designSystem/method/decision-records.md)).

## Edge cases to test

- A person works in a way the craft's convention does not describe: structure stays optional (Decision 0003), and nothing breaks when the expected sections are missing.
- Work is written in an Indian script or right to left: units, numbers and layout follow [Writing systems](https://kwark.space/designSystem/foundations/writing-systems.md).
- The craft's paper is wider than a phone: the phone shows a reading view with the paper's proportions kept, not a shrunken page.
- Two people edit the same artefact: presence is shown ([Presence cursor](https://kwark.space/designSystem/components/presence-cursor.md)) and conflicts are resolved in the calm voice of [Saving and sync](https://kwark.space/designSystem/patterns/saving-and-sync.md).
- The person deletes something by mistake: Undo in a toast, not a confirmation dialog ([Destructive actions](https://kwark.space/designSystem/patterns/destructive-actions.md)).

## Starter prompt

> You are adapting the Kwark Design System to a new craft: {craft}. Read https://kwark.space/designSystem/kits/any-creative-app.md, /foundations/principles.md, /foundations/ai-and-authorship.md and /patterns/phones.md. First list the craft's paper artefact, its units, who owns each fact, and the phone moment, and mark every convention you are unsure of as "to confirm with practitioners" instead of inventing it. Then map the craft's screens to existing Kwark components using the mapping table. Use only `--k-*` tokens. Do not add any feature that judges the work or saves machine-made content without the person's acceptance.

## AI readiness test

**Task:** Plan a rehearsal tool for a theatre stage manager using the Kwark Design System.

**Give the agent:** Any creative app kit, Screenplay page, Call sheet, Script revision diff, Phones pattern.

**Constraint:** Cue naming differs between companies.

**A reliable answer:**
- Names the prompt book as the craft's paper
- Uses the company's own cue naming as a setting, not a claimed standard
- Rehearsal calls reuse the call sheet pattern with numbered revisions
- Script changes in rehearsal tracked with the revision diff
- Phone designed for the rehearsal room
- Nothing judges the performance
