How do I install the Office Design System skill?

Run npx skillmds@latest add haifai-ai/office-design-system in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Office Design System safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Office Design System?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Office Design System free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Office Design System?

Haifai-AI (@haifai-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Office Design System by haifai-ai — Agent Skill

Name: Office Design System
Author: Haifai-AI

Office Design System

Cross-format visual language for Baby Whale deliverables: how to pick a fresh topic-informed palette and carry it consistently across workbooks, decks, documents, and PDFs so a multi-file pack reads as one designed set. Use alongside the other office skills whenever more than one file ships.

Haifai-AI Updated Sep 17, 2026

File contents

Office design system

A quarterly pack usually ships as a set — workbook, deck, document. Ship it as one designed system, not three unrelated files. Each format designs itself fresh for the topic (no templates); the SYSTEM is the shared decisions listed here.

One palette decision per engagement

Pick ONE topic-informed palette: a dominant color, 1–2 supporting tones, one sharp accent used ~10% of the time. Inspiration table: powerpoint-deck/references/design.md. With brand hexes from the user, use theirs everywhere.
Write the hexes as named constants at the top of every build script — same names, same values in openpyxl / python-pptx / python-docx / reportlab. Derive tints (blend/tints in powerpoint-deck/scripts/pptx_helpers.py) instead of new hues.
Chart series draw from the same ramp in every file, in the same order.

Consistency checklist

Identical title wording across cover page, deck title slide, and workbook banner (same case, same punctuation).
Currency, units, and date formats match across every file (usd vs $ in prose; yyyy-mm-dd everywhere).
One number, one home: each metric has a canonical sheet; decks/documents quote it instead of recomputing.
Typography discipline per format (deck titles ≥30pt, doc body 10.5–11pt, workbook labels 10–11pt) — consistent FEELING, format-appropriate sizes.
Never accent bars/stripes/title underlines in any format — separation comes from whitespace and tints.

File layout convention

Deliverables live under deliverables/ with dated slugs: deliverables/q1-review-deck.pptx, deliverables/q1-revenue.xlsx, deliverables/q1-summary.docx. Mention the folder once, list files after.

---name: office-design-systemdescription: Cross-format visual language for Baby Whale deliverables: how to pick a fresh topic-informed palette and carry it consistently across workbooks, decks, documents, and PDFs so a multi-file pack reads as one designed set. Use alongside the other office skills whenever more than one file ships.---# Office design systemA quarterly pack usually ships as a set — workbook, deck, document. Ship itas one designed system, not three unrelated files. Each format designsitself fresh for the topic (no templates); the SYSTEM is the shareddecisions listed here.## One palette decision per engagement- Pick ONE topic-informed palette: a dominant color, 1–2 supporting tones, one sharp accent used ~10% of the time. Inspiration table: `powerpoint-deck/references/design.md`. With brand hexes from the user, use theirs everywhere.- Write the hexes as named constants at the top of every build script — same names, same values in openpyxl / python-pptx / python-docx / reportlab. Derive tints (`blend`/`tints` in `powerpoint-deck/scripts/pptx_helpers.py`) instead of new hues.- Chart series draw from the same ramp in every file, in the same order.## Consistency checklist- Identical title wording across cover page, deck title slide, and workbook banner (same case, same punctuation).- Currency, units, and date formats match across every file (`usd` vs `$` in prose; `yyyy-mm-dd` everywhere).- One number, one home: each metric has a canonical sheet; decks/documents quote it instead of recomputing.- Typography discipline per format (deck titles ≥30pt, doc body 10.5–11pt, workbook labels 10–11pt) — consistent FEELING, format-appropriate sizes.- Never accent bars/stripes/title underlines in any format — separation comes from whitespace and tints.## File layout conventionDeliverables live under `deliverables/` with dated slugs:`deliverables/q1-review-deck.pptx`, `deliverables/q1-revenue.xlsx`,`deliverables/q1-summary.docx`. Mention the folder once, list files after.

Frequently asked questions