> For the complete documentation index, see [llms.txt](https://docs.prophetmarket.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prophetmarket.ai/brand-guidelines/colour-and-type.md).

# Colour and Type

## Palette

| Role         | Value     | Use                                                        |
| ------------ | --------- | ---------------------------------------------------------- |
| Prophet blue | `#1F6FEB` | Primary brand colour. Flat colour fields, accents, data    |
| Ink          | `#0B0D10` | Near black. Type on blue and paper surfaces, dark surfaces |
| Paper        | `#F4F2ED` | Off white. Data heavy layouts, tables, comparisons         |
| Cyan         | `#00A8E8` | Secondary accent. Gradients on data only                   |
| White        | `#FFFFFF` | Type on photography and dark surfaces                      |

{% hint style="warning" %}
**Three different blues are currently in circulation**

The value above is the brand document value. The live product surfaces compute to approximately `#007DF3`, and the logo wordmark uses `#081B40` rather than the Ink value. These need reconciling at brand level. Until they are, match the surface you are working on rather than assuming the table is authoritative.
{% endhint %}

## Surfaces

Three surfaces, used deliberately rather than interchangeably.

| Surface                | When to use                                         |
| ---------------------- | --------------------------------------------------- |
| Flat Prophet blue      | Statements, single figures, brand moments           |
| Paper                  | Tables, comparisons, anything the reader must study |
| Full bleed photography | Human and emotional beats only, never for data      |

Flat colour fields are the brand asset. Avoid gradients on backgrounds, avoid texture, and avoid dark on dark layouts across a full set. A grid where every tile is dark reads as documentation rather than social content.

## Typography

| Role            | Typeface                          | Treatment                                      |
| --------------- | --------------------------------- | ---------------------------------------------- |
| Display         | Archivo, weight 800, condensed    | All caps. Should occupy roughly half the frame |
| Labels and data | JetBrains Mono, weight 500 to 700 | All caps, letterspaced, small                  |
| Body            | Inter, weight 400                 | Sentence case                                  |

Headline type should be large enough to read at thumbnail size. If a headline reads comfortably at full size but not as a grid thumbnail, it is too small.

## Contrast

Text colour follows the actual rendered background rather than the container. Light or high key imagery takes dark type. Dark or low key imagery takes white type with a gradient scrim to guarantee separation.

## Recurring devices

Three devices recur and together make a set feel like one system: a small monospaced series label with a position indicator in the top corner, a single dominant figure or equation as the hero element, and the ring mark footer lockup. A run of posts becomes a series when these stay consistent.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prophetmarket.ai/brand-guidelines/colour-and-type.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.