From cidr-document-format
Use this skill whenever the user asks to create any document, report, memo, policy, SOP, proposal, playbook, or formatted deliverable for CIDR (Caller ID Reputation). This skill ensures every document uses the official CIDR cover page layout, color palette, heading hierarchy, and professional formatting. Trigger on any request involving document creation, Word docs, policies, procedures, guides, or any written deliverable that should look polished and consistent with the CIDR brand. Even if the user doesn't explicitly mention formatting, use this skill for any CIDR document output.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cidr-document-format:cidr-document-formatThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every document created for Caller ID Reputation (CIDR) MUST follow this formatting specification exactly. This ensures brand consistency across all SOPs, policies, proposals, and deliverables.
Every document created for Caller ID Reputation (CIDR) MUST follow this formatting specification exactly. This ensures brand consistency across all SOPs, policies, proposals, and deliverables.
Before writing any code, also read the core docx skill at /mnt/skills/public/docx/SKILL.md for the docx-js API reference and validation steps.
These are the ONLY colors to use in CIDR documents:
| Token | Hex | Usage |
|---|---|---|
NAVY_DARK | 1F3864 | Company name "CALLER ID REPUTATION", H1 headings |
BLUE_ACCENT | 2E75B6 | Document title, horizontal rules, H2 headings, links |
GRAY_SUBTITLE | 595959 | Cover page subtitle, metadata lines |
BODY_TEXT | 333333 | All body paragraph text |
GRAY_LIGHT | 808080 | Page header text, footer text |
RULE_COLOR | 2E75B6 | Horizontal divider lines (cover page + under H1s) |
CALLOUT_BG | F2F2F2 | Callout/highlight box background fill |
CALLOUT_BORDER | 2E75B6 | Left border on callout boxes |
TABLE_HEADER_BG | 1F3864 | Table header row background |
TABLE_HEADER_TEXT | FFFFFF | Table header row text |
TABLE_ALT_ROW | F2F7FB | Alternating table row fill |
| Element | Font | Size (pt) | Weight | Color |
|---|---|---|---|---|
| Company name | Calibri | 26 | Bold | NAVY_DARK |
| "CIDR" acronym | Calibri | 16 | Normal | BLUE_ACCENT |
| Document title | Calibri | 20 | Bold | NAVY_DARK |
| Cover subtitle | Calibri | 11 | Normal | GRAY_SUBTITLE |
| Cover metadata | Calibri | 11 | Normal | GRAY_SUBTITLE |
| H1 (numbered) | Calibri | 18 | Bold | NAVY_DARK |
| H2 (numbered) | Calibri | 14 | Bold | BLUE_ACCENT |
| H3 | Calibri | 12 | Bold | NAVY_DARK |
| Body text | Calibri | 11 | Normal | BODY_TEXT |
| Bold body | Calibri | 11 | Bold | BODY_TEXT |
| Callout title | Calibri | 11 | Bold | BODY_TEXT |
| Footer text | Calibri | 9 | Normal | GRAY_LIGHT |
| Page header | Calibri | 9 | Italic | GRAY_LIGHT |
The cover page is its own section with no header or footer. It contains these elements in order, all center-aligned:
Vertical spacing — approximately 2 inches (2880 DXA) of space before the company name to push content to the upper-middle of the page.
"CALLER ID REPUTATION" — 26pt Calibri Bold, NAVY_DARK, center-aligned, all caps.
"CIDR" — 16pt Calibri, BLUE_ACCENT, center-aligned. Small spacing after (200 DXA).
Horizontal rule — A full-width paragraph with a top border: BLUE_ACCENT, 1pt, BorderStyle.SINGLE. Spacing before: 400 DXA.
Document Title — 20pt Calibri Bold, NAVY_DARK, center-aligned. This is the actual title of the document (e.g., "Trade Show & Conference Conduct Policy"). It sits between the two horizontal rules.
Horizontal rule — Same as #4, but using a bottom border on the title paragraph or a top border on the next paragraph.
Subtitle line — 11pt Calibri, GRAY_SUBTITLE, center-aligned. Format: Standard Operating Procedure | [Document Type] (e.g., "Rules of Engagement", "Sales Playbook", "Revenue Operations"). Spacing before: 300 DXA.
Metadata block — 11pt Calibri, GRAY_SUBTITLE, center-aligned, each on its own line. Spacing before the block: 400 DXA. Lines:
Department: [Department Name]Effective Date: [Full date, e.g., February 19th, 2026]Version: [X.X]Approved By: Shawn Stiffler, CROIMPORTANT: The cover page section must specify sectionType: SectionType.NEXT_PAGE or equivalent so the body content starts on a new page.
CIDR | [Short Document Title] — 9pt Calibri Italic, GRAY_LIGHT, right-aligned.GRAY_LIGHT, 0.5pt) spanning the content width.Confidential – Caller ID Reputation (CIDR) left-aligned, and Page [X] right-aligned. Both 9pt Calibri, GRAY_LIGHT.H1 — Major Sections (numbered: "1.", "2.", "3.", etc.)
NAVY_DARKBLUE_ACCENT, 1pt, full width — applied as a paragraph borderH2 — Subsections (numbered: "2.1", "2.2", etc.)
BLUE_ACCENTH3 — Sub-subsections (no number, bold label)
NAVY_DARKBODY_TEXTLevelFormat.BULLET (never unicode bullets)BODY_TEXTUsed for "Key Principle", "Important", "Zero-Tolerance" blocks, etc.
CALLOUT_BORDER (BLUE_ACCENT)CALLOUT_BG (F2F2F2)BODY_TEXTBODY_TEXTTABLE_HEADER_BG background, TABLE_HEADER_TEXT text, 11pt Calibri BoldTABLE_ALT_ROWBFBFBFWidthType.DXA and set both columnWidths and cell widthFor policy documents with violation frameworks:
All major sections are manually numbered starting at 1. Subsections use decimal notation (1.1, 1.2, 2.1, etc.). Do NOT use Word's automatic numbering for section headers — manually prefix the number in the heading text.
Every page footer must include: Confidential – Caller ID Reputation (CIDR)
When creating a CIDR document, verify:
python scripts/office/validate.pyProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub shawndstiffler-bit/cidr-document-plugin --plugin cidr-document-format