Kwark. Design System
Open Kwark
Design SystemGetting started

What sets Kwark apart

Ten things this system does that a general-purpose design system does not, most of them not about how the interface looks. Each one links to the rule, the decision or the file that proves it.

Getting started

Most design systems describe how an interface looks. Kwark’s also says who may change a writer’s words, which decision a rule comes from, what an agent must prove before its code ships, and how a page prints on paper for a crew at 6 a.m. These ten points are the reasons to choose it. Each one is a rule written into the system or a file you can download today, not a promise.

1. Authorship is a rule, not a setting

A machine in Kwark may find, move, convert or carry the writer’s own words. It never writes them, scores them or judges them (Decision 0002). That one sentence decides how every AI feature is built: proposals come from the writer’s own outline beat or script, carry a revision mark until the writer accepts or rewrites them, and record where they came from. General systems give you a “sparkle” button style. This one gives you the line a feature may not cross, and a test that fails when it does.

See AI and authorship, Revision mark and AI assistance pattern.

2. Every rule traces to a decision

Rules are not opinions. Each one points to a numbered decision record with the problem, the options, the choice and the date: the phone header (0016), call sheet revisions (0020), sharing by film role (0042), the breadcrumb (0044). When a rule is wrong, you change the decision and the rule follows, and you can see why it was made in the first place.

See Decision records.

3. Written once, read by people and by agents

Every page is published twice: as a page for people and as clean markdown for agents, from the same source. The system ships AGENTS.md, llms.txt, W3C design tokens, an MCP server that can audit code against the rules, and fourteen skills. Flip any page to Agent and you see exactly what a coding agent receives.

See For agents, MCP server and Skills.

4. Agents have to pass a test

Every foundation, pattern and kit ends with a readiness test: a task, the context the agent gets, a constraint, and the behaviours that count as reliable. You run it against your own agent and see whether it follows the system before you trust its output. The tests are part of the documentation, not a separate QA project.

See Readiness tests and AI-ready roadmap.

5. Built for the work, not the dashboard

Generic systems stop at buttons, forms and tables. Kwark carries on into the parts of a film: the screenplay page with print geometry, index cards, the stripboard, the call sheet with numbered revisions, the shooting calendar, the cast board, storyboards, and kits for editing, colour grading and sound. Teams building any creative tool start from the hard parts instead of drawing them from scratch.

See Creative app kits and Components.

6. Paper and digital in one act

A crew still works from paper. Every structured artefact in Kwark has a printed form that matches the industry’s: the screenplay page at the right margins, the call sheet a first AD would recognise, revision colours in the standard order. The screen and the page are designed together, so nothing has to be re-typed into a spreadsheet to be printed.

See Print and export and Screenplay page.

7. Every script, on the same page

Screenplays in India, and in most of the world, mix languages. The system has a font token per script, phonetic typing on an English keyboard, right-to-left lines, and rules for numbers, case and sorting across scripts, so Devanagari, Tamil and Latin sit on one page at one rhythm.

See Writing systems.

8. Writing rooms, with the legibility maths

Writers work at 2 a.m. and in daylight. The editor has five rooms (Studio, Daylight, Paper, Lamplight, Midnight), each a complete surface with every colour derived from it and checked for contrast, so a feature built in one room works in all five without extra design.

See Writing rooms.

9. A safe place, by design

Kwark has no leaderboards, public scores, competitions or social feeds. A writer’s work is private until they share it, and sharing is by film role (writer, director, first AD, department head) rather than generic viewer and editor permissions (Decision 0042). The system writes these limits down so a new feature cannot quietly add them.

See Sharing and roles and Principles.

10. Built for students and cheap phones

Kwark’s users include students from 13 and filmmakers on low-cost Android phones and slow connections. Phones get one header line and one floating button (Decision 0016), content starts high on the screen, nothing a person reads is under 12px, and every screen is designed to cost few database reads, because a free tier is a real budget. Inclusive design here is a constraint the system was built under, not a checklist added at the end.

See Inclusive design and Phones.

And the method that produced it

The system publishes how Kwark decides, not only what it decided: walk the user journey before building (UX before build), treat competitors as the floor not the target, give structure without teaching, and record every decision. Any team can adopt the method with the components.

See Kwark method.

  • Must treat Decision 0002 as a hard limit: never generate, score or rewrite a writer’s story text.
  • Must cite the decision number when a rule comes from one.
  • Always run the page’s readiness test before claiming an agent follows the system.
  • Never add public scores, leaderboards or social feeds to a Kwark screen.

AI readiness test

Task. A founder asks for a one-paragraph pitch of why a team building a video editing app should adopt the Kwark Design System instead of Material.

Give the agent. This page.

Constraint. Only claims this page supports.

A reliable answer

  • Mentions the creative-tool components and editing kit
  • Mentions agent-readable docs with readiness tests or the MCP server
  • Mentions decisions behind rules or the authorship rule
  • Does not invent customers, metrics or comparisons with Material’s features

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

Open .mdllms.txt
Loading…