# Branded Doc

**Status:** <mark style="color:$primary;">In Development</mark>

### What It Does

Employees ask Claude to create a document in natural language and receive a fully branded Mailworks document saved directly to Google Drive. Claude handles the content, structure, and formatting automatically based on the Mailworks brand system and the employee's request.

Examples of what employees can ask:

* "Create a document called Role Based Prompts with a section for each department leader."
* "Write up an internal update on the Portal 2.0 migration."
* "Draft a one-pager about our partnership program."

***

### Architecture

{% code overflow="wrap" %}

```
Employee (Claude web or desktop) → SKILL.md (brand rules + generation logic) → docx-js (branded .docx output) → Google Drive Connector → Doc in Drive
```

{% endcode %}

Claude receives the employee's request, structures the content following the brand rules defined in the skill instructions, and generates a branded .docx file using docx-js. The employee saves the file to Google Drive through the built-in Google Drive connector. Google auto-converts the .docx to a Google Doc on upload. This is the current interim approach. A dedicated MCP server for direct Google Docs API integration is planned as the production architecture for org-wide deployment.

***

### Intake Flow

When an employee requests a document, Claude first evaluates whether the request contains enough detail to begin drafting. If the request is specific enough (clear topic, audience, and purpose), Claude proceeds directly to content generation. If the request is too vague or missing key details, Claude asks targeted clarifying questions before drafting. This prevents low-quality first drafts and reduces the back-and-forth needed to reach a final document.

Examples of requests that are rich enough to build immediately:

* "Create a one-pager for employees explaining our new PTO policy. Include the accrual schedule, blackout dates, and how to submit requests."
* "Write an internal memo from Sarah announcing the Q3 hiring plan for the operations team. We're adding two warehouse leads and one logistics coordinator."

Examples that need clarifying questions first:

* "Make me a document about the new project." (Which project? Who is the audience? What should it cover?)
* "Write something about onboarding." (A checklist? A welcome guide? For new hires or for managers?)

***

### Brand System

All documents follow the Mailworks brand system:

| Element   | Font                   | Size | Color                  | Capitalization |
| --------- | ---------------------- | ---- | ---------------------- | -------------- |
| Title     | Proxima Nova Extrabold | 30pt | Navy `#0B3B60`         | ALL CAPS       |
| Subtitle  | Proxima Nova Extrabold | 22pt | Navy `#0B3B60`         | Title Case     |
| Heading 1 | Proxima Nova Extrabold | 16pt | Indicia Pink `#E81F76` | Title Case     |
| Heading 2 | Proxima Nova Bold      | 14pt | Navy `#0B3B60`         | Title Case     |
| Heading 3 | Proxima Nova Bold      | 12pt | Teal `#3FBEAC`         | Title Case     |
| Heading 4 | Proxima Nova Bold      | 11pt | Graphite `#57585A`     | Title Case     |
| Body Text | Proxima Nova Regular   | 11pt | Graphite `#57585A`     | Sentence case  |

Additional brand elements:

* Line spacing is 1.15 document-wide on all text including headings
* Gray horizontal dividers before each H1 section
* Bold inline labels for metadata (e.g., "Prepared by: Name"), included only when explicitly requested
* Arctic `#9DDAE7` table header backgrounds with Navy text
* Title, Subtitle, and H1 use "Proxima Nova Extrabold" as a distinct font weight. H2 through H4 use "Proxima Nova" Bold. This distinction is what makes the Google Docs Styles dropdown show correct weights after conversion.
* Never use em dashes in any Mailworks document. Use commas, semicolons, or colons instead.
* The full brand specification is maintained in the `brand-guide.md` reference file.

***

### Logo

The Mailworks logo is fully implemented. The asset is a verified transparent PNG at 1000x436 pixels (2.294:1 aspect ratio), converted from the original SVG. The skill supports cover page placement and faded footer placement.

***

### Skill Components

| Component          | File                                      | Description                                                                                  |
| ------------------ | ----------------------------------------- | -------------------------------------------------------------------------------------------- |
| Skill Instructions | `SKILL.md`                                | Core rules for document structure, brand application, and content formatting                 |
| Reference File     | `references/brand-guide.md`               | Complete brand specification with colors, typography, heading hierarchy, and layout patterns |
| Asset              | `assets/mailworks-logo.png`               | Mailworks logo for documents that require it                                                 |
| MCP Server         | <mark style="color:$info;">Planned</mark> | Node.js server to create and edit Google Docs via the Google Docs API (future enhancement)   |

***

### Current Limitations

* MCP server is planned but not yet built; current approach uses docx-js as an interim solution
* Skill is functional and tested but not deployed org-wide
* Editing existing documents is not supported; the skill regenerates documents from scratch

***

### What's Next

* Test the full employee workflow end-to-end with real document requests
* Build and provision the Node.js MCP server for direct Google Docs integration
* Connect the MCP server as a custom connector in Claude admin settings
* Expand role-based profile prompts as more employees onboard
* Explore branded .pptx generation
* Deploy skill org-wide once MCP server is live
* Expand supported document types and patterns


---

# Agent Instructions: 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:

```
GET https://knowledge.themailworks.com/skills/branded-doc.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.