---
name: kwark-creative-app
description: Start a new creative or filmmaking app (a script tool, an editor, a storyboard, a scheduler, a sound or grading tool, a production office) on the Kwark Design System - set up kwark.css and tokens, the writing rooms, phone and desktop shells, saving and offline, print, and the first screens. Use when beginning a new creative-tool project or adopting the Kwark system in an existing one.
---

# Start a creative app on the Kwark system

The Kwark Design System was made for a filmmaking app and works for any tool where a person makes something: a script, a cut, a board, a schedule, a mix. This skill sets a new app up on it the way Kwark is built.

## Load first

- https://kwark.space/designSystem/llms.txt (the map)
- https://kwark.space/designSystem/AGENTS.md (the rules)
- https://kwark.space/designSystem/developing.md (kwark.css, tokens, theming)
- https://kwark.space/designSystem/agents/roadmap.md (the stages and the "ready enough" line for each)
- The kit closest to the app: https://kwark.space/designSystem/kits/<screenwriting|editing|storyboard-and-shots|scheduling-and-call-sheets|sound|colour-grading|production-office|any-creative-app>.md

## Order of work

1. **The person and the artefact.** Write one sentence: who makes what, in what situation. Name the paper artefact the industry already uses (a script page, a stripboard, a call sheet, a cue sheet). The digital version is that artefact, not a table beside it.
2. **The journey before any code.** Walk it at phone size and at desktop: where they come from, each step, what can go wrong, how they get back to the work. Agree it with the product owner. Ask two or three questions at most, then state your calls.
3. **Set up the system.** Link `https://kwark.space/designSystem/kwark.css` (or copy it into the repo), load Poppins, Raleway and Courier Prime, add `class="kw-root"` on the app root, `class="dark"` on `<html>` for dark. Use writing rooms for sustained writing surfaces when they fit the craft. An image or grade viewer keeps the stable surround its monitoring requires.
4. **The shells.** Desktop: a header with File, Edit, View, Tools, Help menus and real shortcuts. Phone: one 44px header line, content by about y = 200, one floating control, menus as bottom sheets.
5. **Saving first.** Autosave, a one-word save state, offline that keeps the work on the device, undo, recoverable trash. Build this before the second feature.
6. **The first real screen**, with every state (empty, loading, error, offline, read-only).
7. **Print or export the artefact** from the start, at the industry's page geometry.
8. **Record decisions** in `docs/ux/decisions/` from the first one.

## Rules

- **Must** use only `--k-*` tokens and `kw-` components; add a token only with a light and a dark value and a comment.
- **Must** keep the person the author: anything a machine proposes is marked as a revision until they accept it. Never score or grade their work.
- **Must** make structure optional: outlines, targets, templates can be switched off and nothing breaks.
- **Never** add streaks, leaderboards, public counts or notifications that exist to bring people back.
- **Never** copy a competitor's feature as the reason to build it. Describe the unmet need and verify any differentiation claim against the products actually reviewed.
- **Always** check each step against the roadmap's AI readiness check before moving on.
