Quov

/design-system

Design system

How everything that carries the Quov name looks, reads and is built. Each guide renders its rules and ships them as a Markdown file, so another agent can produce Quov work without access to this repository.

Guides

Brand is the base. The other four apply it to one medium each and never override it; when two guides disagree, Brand wins.

  1. 01BrandName, mark, both palettes, the three type roles, voice and anti-references. The base every other guide applies.base
  2. 02Web pagesThe marketing site and any public page: tokens, type scale, layout rhythm, components, motion, languages and themes.applies 01
  3. 03DocumentsLetter-size printable documents, such as proposals and offers, set in the paper theme.applies 01
  4. 04ArtifactsSelf-contained HTML pages an agent generates: reports, tools and summaries, in both themes.applies 01
  5. 05Application UIProduct interfaces: dual theme, semantic colors, data tables, badges, the navigation rail and forms.applies 01

Agent files

Give an agent the brand file plus the file for the medium it works in. Each file stands on its own: tokens with OKLCH values for both themes, how to load the fonts, and absolute URLs for the logo files.

Languages
Every file exists in English (.en.md) and Spanish (.es.md) with identical content. Pick the one the agent works in; the language of what it produces is set by the task, not by the file.
Order
quov-brand first, then one of quov-web, quov-documents, quov-artifacts or quov-app.
Logo files
Served from https://quov.io/design-system/logo/: quov-mark-dark, quov-mark-light and quov-letters, as SVG and as PNG from 32 to 1024 px. See Brand for the rules.
Fetch the base file and the web guide
curl -fLO https://quov.io/design-system/quov-brand.en.md
curl -fLO https://quov.io/design-system/quov-web.en.md