Kwark. Design System
Open Kwark
Design SystemCreative app kits

Creative app kits

Everything a team needs to build a screenwriting, editing, storyboard, scheduling, sound, grading or production app on Kwark: screens, components, domain conventions, keyboard maps, phone rules, AI rules and a starter prompt.

Creative app kits
12INTEdit suiteMira finds the frameN1 3/81
13EXTRooftopThe drive over the edgeD2 1/812

What a kit is

A kit is the design system applied to one craft. Generic systems stop at buttons and tables; a team building a video editor still has to work out what a playhead is, how timecode is written, what J, K and L do, and how to stop the phone layout from eating the picture. Each kit answers those questions once, with Kwark’s real components and the conventions people in that craft already work by.

Every kit has the same parts, in the same order:

  1. Who it is for: the team building the app and the people who will use it.
  2. The screens: what such an app needs, and which Kwark component draws each.
  3. Live demo: real kw- components you can switch to dark mode and copy.
  4. Domain conventions: the industry’s own rules, stated accurately. Where a convention varies by country, union or software, the kit says so and does not invent a standard.
  5. Keyboard map: shortcuts people in the craft expect.
  6. Phone and desktop: what each device is for.
  7. AI and authorship: what a machine may do in that craft, and how it is marked.
  8. Starter prompt: a prompt you can give an agent to start the build.
  9. AI readiness test: a task that shows whether an agent has understood the kit.

The kits

ScreenwritingBuild a writing surface whose page on screen is the printed page, with the elements, revisions, outline and timeline a working screenwriter expects, and nothing that judges the work.Storyboard and shotsBuild shot planning the way a director and DP think about it: shots named by scene and letter, framing in industry terms, coverage lined on the script, boards at the film's aspect ratio, setups for the crew, and an animatic.Scheduling and call sheetsBuild the first AD's tools: a stripboard in pages and eighths with the four paper colours, shooting days, day out of days, and call sheets issued as numbered, frozen revisions that print, save as PDF and download as CSV.Production officeBuild the producer's and line producer's tools on Kwark: a marked-up breakdown that writes its own sheets, cast and locations that feed the budget, paperwork that remembers when it was checked, and sharing by film role.EditingBuild a picture editor or review tool on Kwark: a bin that knows the script, source and program viewers, a multitrack timeline with one coral playhead, timecode written correctly, and the keyboard editors already use.SoundBuild a sound session or dubbing tool on Kwark: tracks named by character, waveforms with fades and clip gain, a mixer in signal order, loudness against the target the project chose, and ADR cues made from the screenplay.Colour gradingBuild a grading or dailies colour tool on Kwark: a neutral viewer with before and after, scopes that measure, primaries with numbers, a node graph that shows order, clips with versions, and looks named by their colour spaces.Any creative appCarry 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.

In Kwark and ready for Kwark

Four kits describe crafts Kwark already does: screenwriting, storyboard and shots, scheduling and call sheets, and the production office. Their components are marked In the app and carry real import paths from the Kwark source.

Three kits describe crafts Kwark does not do today: editing, sound and colour grading. Their components are marked Ready for Kwark. They are designed on the same tokens and rules, and they say plainly that Kwark has no such module yet. Nothing in those kits claims a feature exists.

Rules every kit shares

  • Must start from the source document. The screenplay owns scene numbers, headings and parts. The schedule owns dates. An issued call sheet owns what it said when it was issued. An editor’s source media owns its own timecode. Decide which document owns each fact before binding a control to it.
  • Must build the paper artefact and the structured one in one act (Decision 0005). A marked breakdown page writes the sheet; an issued call sheet prints, saves as PDF and downloads as CSV from the same frozen copy.
  • Never judge the work. No scores, grades, verdicts, coverage or “health” for a story, a cut, a mix or a grade (Decision 0002). Measure, find and carry; never rate.
  • Must mark every machine-proposed word, frame or value with a Revision mark until a person accepts or edits it. Read AI and authorship.
  • Always keep structure optional (Decision 0003). An app that needs acts, beats, reels or stems to work at all has failed people who work differently.
  • Must treat competitors as the floor (Decision 0006). Parity with the standard tools of the craft is the minimum; each kit names what that floor is.
  • Must keep phones content first: one 44px header line, one floating control, content by about y = 200 (Decision 0016). Read Phones.
  • Always use the calm voice for saving, sync and errors (Decision 0013). Read Saving and sync and Errors.
  • Never use glows, gradients or decorative light, least of all around picture, where they change what people see. Read Colour.

Choosing a kit

You are building Start with Also read
A script editor, notes tool or writers’ room Screenwriting Writing systems
An animatic, previs or shot-planning tool Storyboard and shots Editing
A scheduling or AD tool Scheduling and call sheets Sharing and roles
A producer’s or line producer’s tool Production office Print and export
A video editor or review tool Editing Sound
A mixing, ADR or podcast tool Sound Editing
A grading or look-development tool Colour grading Data visualisation
Anything else made by artists Any creative app Principles

AI readiness test

Task. Plan a small app for an assistant director who issues call sheets from a stripboard.

Give the agent. Scheduling and call sheets, Call sheet, Stripboard strip, Sharing and roles.

Constraint. A crew member may be offline and holding yesterday’s issued PDF.

A reliable answer

  • Separates the working schedule from issued, numbered call sheet revisions
  • Uses the four strip paper colours by tone and page lengths in eighths
  • Scopes personal contacts by role
  • Gives the phone a read-first route to today’s sheet
  • Never claims issuing sends anything

Give this Markdown to your coding agent or share its URL.

Open .mdllms.txt
Loading…