Claude Skill

pdf-atelier

House style for creating ANY new PDF with Claude - reports, proposals, brochures, menus, resumes, certificates, newsletters, invoices, study notes, handouts, one-pagers, manuals. Builds the document as HTML/CSS rendered by WeasyPrint with an engineered design system - cards, stat

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download mehranqadirian-skills-documents_pdf-atelier-c88187d.zip · 310 KB

Install

skills CLI npx skills add https://github.com/MehranQadirian/skills/tree/main/documents/pdf-atelier
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install mehranqadirian-skills@llmmart
Git git clone https://github.com/MehranQadirian/skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole mehranqadirian/skills collection as a plugin from our marketplace. Git is the plain clone.

README

PDF Atelier

Beautiful, consistent PDFs from a single prompt. A Claude skill that turns reports, proposals, resumes, menus and more into polished documents with RTL support (Arabic, Hebrew, Persian) built in.

Why

  • One design language for every document: clean hierarchy, tight spacing, 6px corners.
  • 12 themes, all contrast-audited. Or generate one from any brand color.
  • RTL done right: layout, tables, charts and bullets mirror automatically.
  • Real components: cover, hero, stat tiles, tables, bar charts, timelines, checklists, callouts.
  • Fonts included: Vazirmatn and JetBrains Mono, no install needed.

Try it

Ask Claude:

Make me a clean PDF proposal for a website redesign, use the executive theme.

Create a quarterly report PDF with the ocean theme.

Themes

Theme Good for
indigo (default) Education, tech, product
ocean Corporate, finance, reports
executive Proposals, legal, premium
teal Health, science, wellness
emerald Sustainability, nutrition
forest Nature, outdoors
sunset Events, food, creative
crimson Sports, awards, urgent
rose Lifestyle, beauty, kids
violet Design, arts, music
graphite Minimal, formal, B&W print
paper Essays, long reading

Custom brand color: Theme.from_hex("#0f766e"). Full gallery: assets/theme-gallery.pdf.

Install

Claude.ai: zip this folder, then go to Settings > Capabilities > Skills > Upload.

Claude Code:

cp -r documents/pdf-atelier ~/.claude/skills/

Requires Python 3 and weasyprint (installed by scripts/setup.sh). poppler-utils is optional, used for visual previews.

Use as a library

from pdfkit import Doc

doc = Doc(rtl=False, theme="ocean", title="Quarterly report")
doc.hero("Internal", "Quarterly report", "Highlights and next steps")
doc.stats([("1.2M", "Revenue", "+14%"), ("92", "NPS"), ("3,400", "Users")])
doc.h2("Regions")
doc.bars([("North", 480), ("South", 310)], colors=True)
doc.save("report.pdf")

Run the full demo: python3 scripts/example.py ./out

Structure

pdf-atelier/
├── SKILL.md           skill instructions for Claude
├── assets/            fonts, theme gallery
├── scripts/           pdfkit.py (components), themes.py, setup.sh, example.py
└── references/        design rules and rendering pitfalls

Not for

Merging, splitting, filling forms, OCR or editing existing PDFs. Use a general PDF skill for those.

License

Fonts are under the SIL Open Font License (see assets/fonts).

Skill manifest

pdf-atelier

One consistent, professional design language for every PDF: calm hierarchy, generous but tight spacing, 6px corners (never sharp, never pill-like), engineered colour palettes, perfect RTL. Topic does not matter; the content decides which components to use and the theme decides the mood.

pdf-atelier/
├── SKILL.md
├── assets/
│   ├── fonts/            Vazirmatn 400/500/700, JetBrains Mono 400/700 (+ OFL licences)
│   └── theme-gallery.pdf pre-rendered preview of all 12 themes
├── scripts/
│   ├── setup.sh          installs weasyprint / pillow if missing
│   ├── themes.py         OKLCH palette engine + 12 curated themes + contrast audit
│   ├── pdfkit.py         Doc class: all components (import this)
│   ├── example.py        runnable demo (RTL report + LTR proposal)
│   ├── themes_preview.py regenerates the theme gallery PDF
│   ├── render_preview.sh PDF -> PNG pages + contact sheet (visual QA)
│   └── extras.py         OPTIONAL terminal/code windows - only if the content truly needs them
└── references/
    ├── design-rules.md   spacing, type scale, colour engineering, layout patterns, checklist
    └── pitfalls.md       rendering traps and fixes

Workflow

  1. Setup once: bash <skill>/scripts/setup.sh (fonts need no installation).
  2. Choose the theme (see table). If the user names a colour/brand, use Theme.from_hex("#..."). If they gave no hint, pick by subject and mention the theme name in one phrase; offer assets/theme-gallery.pdf when they want to browse.
  3. Plan pages and sections before writing: aim for 1-4 A4 pages (a dedicated cover() only for long formal documents). Map each piece of content to a component (table below). Keep text short; prefer tables, tiles, lists and charts over paragraphs. One idea per bullet.
  4. Check facts and numbers with code (totals, percentages, dates, conversions). Never do arithmetic by hand in the document. Keep units and spelling consistent everywhere.
  5. Write the build script (in /home/claude) and save to /mnt/user-data/outputs/<name>.pdf:
    import sys; sys.path.insert(0, "/mnt/skills/user/pdf-atelier/scripts")    # use the real install path
    from pdfkit import Doc, mono, b, ul, tag
    doc = Doc(rtl=False, theme="ocean", title="Quarterly report")           # rtl=True for fa/ar/he
    doc.hero("Internal · Q3", "Quarterly report", "Highlights and next steps")
    doc.stats([("1.2M", "Revenue", "▲ 14%"), ("92", "NPS"), ("3,400", "Active users")])
    doc.h2("Regions"); doc.bars([("North", 480), ("South", 310)], colors=True)
    doc.save("/mnt/user-data/outputs/report.pdf")
    
  6. Look at every page: bash <skill>/scripts/render_preview.sh <pdf> 75 then view /tmp/preview/sheet.png (zoom with /tmp/preview/page-N.png). Fix clipping, orphan headings, big empty areas, flipped symbols; re-render. Judge RTL by the picture, never by pdftotext (extracted RTL text always looks scrambled).
  7. Deliver with present_files. One or two sentences, no long recap.

Themes (all contrast-audited: brand/white >= 7:1, body >= 7:1, muted >= 4.5:1, chips/badges >= 4.5:1)

theme mood / use
indigo (default) education, tech, product documents
ocean trustworthy blue: corporate, finance, reports
executive navy + gold: proposals, legal, premium
teal calm clean: health, science, wellness
emerald fresh: sustainability, growth, nutrition
forest earthy: nature, outdoors, organic
sunset warm orange: events, food, creative
crimson bold red: urgent, sports, awards
rose soft magenta: lifestyle, beauty, kids
violet creative purple: design, arts, music
graphite neutral grey: minimal, formal, print-first / B&W printers
paper warm sepia: essays, literature, long reading

Custom: Theme.from_hex("#0f766e") (whole palette from one colour) or Theme.make("name", brand_hue=258, accent_hue=82, chroma=0.9) (two-hue schemes) -> pass as theme=. theme.audit() returns every contrast pair with pass/fail; run it for custom themes and fix failures by changing chroma/lightness. Never hand-pick extra colours: use theme tokens (doc.t["accent"], doc.t["series"][i], ...).

Components (pdfkit.Doc)

Need Method
Full cover page (own page, no footer) cover(title, subtitle, tag_line, meta=[(k, v)])
Title banner on page 1 hero(tag_line, title, subtitle)
Section / sub-section / paragraph / intro h2(text, page_break=False), h3, p, lead
Soft panel / callout (info, warn, ok, bad) card(html, title), note(html, kind, title)
Numbered steps, chapters, features numbered(n, title, body_html, tags=[...])
KPI tiles stats([(value, label, note?)], colors=False) (3-4 per row)
Table (zebra, aligned columns, total row) table(headers, rows, widths, align, total_row); align: start/end/center/ltr
Key-value list (contact, specs) kv([(k, v)])
Bar chart (pure CSS) bars([(label, value)], colors, fmt)
Timeline / roadmap timeline([(when, title, desc)])
Checklist checklist(["a", ("b", True)])
Two columns columns(left_html, right_html, ratio=(1, 1))
Quote quote(text, by)
Image / SVG with caption figure('<img src="file:///...">', caption)
Divider, page break, raw HTML divider(), pagebreak(), raw(html)
Inline helpers b(), mono() (LTR code/IDs/English terms), tag(), ul(), ol()

Charts beyond bars: draw inline SVG (use theme colours) and pass it to figure(), or render with matplotlib to PNG using the theme colours and embed with file://.

Design principles (details: references/design-rules.md)

  • Hierarchy: one hero/cover -> h2 sections with an accent bar -> content in cards, tiles or tables.
  • Colour discipline: brand (dark) for banners and headings, ONE accent for markers, neutrals for surfaces; amber/green/red only for status callouts; series colours only for charts/chips.
  • Density: 10pt body, 1.7 line-height, 6px gaps. Prefer fewer, fuller pages; avoid pages with only 3 lines.
  • Components never split across pages (page-break-inside: avoid); use h2(..., page_break=True) to start a big block on a fresh page.
  • Write for the reader: short sentences, concrete numbers, no filler. Beginners: define a term once, in a chip or a table, not in a paragraph.

Right-to-left (Arabic / Hebrew / Persian)

  • Doc(rtl=True, lang="ar") mirrors layout, bullets, accent bars, tables, timelines and charts automatically.
  • Wrap every Latin token inside RTL sentences (names, codes, formulas, URLs) in mono() so symbols never flip. For table columns with Latin/code content use align="ltr"; numbers use align="end".
  • RTL typography: use the correct script variants and joiners for the language, and keep program output and IDs exactly as they are.
  • Footer page numbers stay LTR (2 / 5).

Optional: terminal and code windows

Only when the content genuinely shows software output: from extras import TechDoc (subclass of Doc) adds terminal(...) (macOS Terminal mockup, dark/light) and code_window(...). Not part of the normal design system.

Do not

  • Hide text in the PDF (white-on-white, tiny fonts, metadata tricks); it is unreliable and hurts accessibility.
  • Use box-shadow (WeasyPrint ignores it), wkhtmltopdf or reportlab for RTL, or hard-code hex colours outside the theme.
  • Deliver without having looked at every rendered page.
Files (skills)
  • assets
    • fonts
      • JetBrainsMono-Bold.ttf 56 KB · in bundle
      • JetBrainsMono-OFL.txt 4.4 KB
        Loading…
      • JetBrainsMono-Regular.ttf 56.1 KB · in bundle
      • Vazirmatn-Bold.ttf 120.2 KB · in bundle
      • Vazirmatn-Medium.ttf 119.8 KB · in bundle
      • Vazirmatn-OFL.txt 4.3 KB
        Loading…
      • Vazirmatn-Regular.ttf 119.9 KB · in bundle
    • theme-gallery.pdf 21.3 KB · in bundle
  • references
    • design-rules.md 4 KB
      Loading…
    • pitfalls.md 1.8 KB
      Loading…
  • scripts
    • example.py 3.6 KB
      Loading…
    • extras.py 5.1 KB
      Loading…
    • pdfkit.py 19.9 KB
      Loading…
    • render_preview.sh 697 B
      Loading…
    • setup.sh 553 B
      Loading…
    • themes.py 9.5 KB
      Loading…
    • themes_preview.py 2.4 KB
      Loading…
  • README.md 2.6 KB
    # PDF Atelier
    
    Beautiful, consistent PDFs from a single prompt. A [Claude skill](../../README.md) that turns reports, proposals, resumes, menus and more into polished documents with RTL support (Arabic, Hebrew, Persian) built in.
    
    ## Why
    
    - **One design language** for every document: clean hierarchy, tight spacing, 6px corners.
    - **12 themes**, all contrast-audited. Or generate one from any brand color.
    - **RTL done right**: layout, tables, charts and bullets mirror automatically.
    - **Real components**: cover, hero, stat tiles, tables, bar charts, timelines, checklists, callouts.
    - **Fonts included**: Vazirmatn and JetBrains Mono, no install needed.
    
    ## Try it
    
    Ask Claude:
    
    > Make me a clean PDF proposal for a website redesign, use the executive theme.
    
    > Create a quarterly report PDF with the ocean theme.
    
    ## Themes
    
    | Theme | Good for |
    |---|---|
    | `indigo` (default) | Education, tech, product |
    | `ocean` | Corporate, finance, reports |
    | `executive` | Proposals, legal, premium |
    | `teal` | Health, science, wellness |
    | `emerald` | Sustainability, nutrition |
    | `forest` | Nature, outdoors |
    | `sunset` | Events, food, creative |
    | `crimson` | Sports, awards, urgent |
    | `rose` | Lifestyle, beauty, kids |
    | `violet` | Design, arts, music |
    | `graphite` | Minimal, formal, B&W print |
    | `paper` | Essays, long reading |
    
    Custom brand color: `Theme.from_hex("#0f766e")`. Full gallery: [`assets/theme-gallery.pdf`](assets/theme-gallery.pdf).
    
    ## Install
    
    **Claude.ai:** zip this folder, then go to Settings > Capabilities > Skills > Upload.
    
    **Claude Code:**
    
    ```bash
    cp -r documents/pdf-atelier ~/.claude/skills/
    ```
    
    Requires Python 3 and `weasyprint` (installed by `scripts/setup.sh`). `poppler-utils` is optional, used for visual previews.
    
    ## Use as a library
    
    ```python
    from pdfkit import Doc
    
    doc = Doc(rtl=False, theme="ocean", title="Quarterly report")
    doc.hero("Internal", "Quarterly report", "Highlights and next steps")
    doc.stats([("1.2M", "Revenue", "+14%"), ("92", "NPS"), ("3,400", "Users")])
    doc.h2("Regions")
    doc.bars([("North", 480), ("South", 310)], colors=True)
    doc.save("report.pdf")
    ```
    
    Run the full demo: `python3 scripts/example.py ./out`
    
    ## Structure
    
    ```
    pdf-atelier/
    ├── SKILL.md           skill instructions for Claude
    ├── assets/            fonts, theme gallery
    ├── scripts/           pdfkit.py (components), themes.py, setup.sh, example.py
    └── references/        design rules and rendering pitfalls
    ```
    
    ## Not for
    
    Merging, splitting, filling forms, OCR or editing existing PDFs. Use a general PDF skill for those.
    
    ## License
    
    Fonts are under the SIL Open Font License (see `assets/fonts`).
    
  • SKILL.md 8.4 KB
    ---
    name: pdf-atelier
    description: House style for creating ANY new PDF with Claude - reports, proposals, brochures, menus, resumes, certificates, newsletters, invoices, study notes, handouts, one-pagers, manuals. Builds the document as HTML/CSS rendered by WeasyPrint with an engineered design system - cards, stat tiles, tables, timelines, bar charts, callouts, cover pages - 12 ready colour themes (OKLCH-generated and WCAG contrast-audited, switchable per document or derived from any brand colour), bundled Vazirmatn + JetBrains Mono fonts, and first-class right-to-left (RTL) support for Arabic, Hebrew and Persian. Use this skill whenever the user asks Claude to create, design, write or export a PDF in any language and topic, even if they only say "make me a PDF", "a clean PDF" or "export this as a PDF", and whenever visual quality matters. Not for merging, splitting, filling forms, OCR or editing an existing PDF (use the pdf skill for those).
    ---
    
    # pdf-atelier
    
    One consistent, professional design language for every PDF: calm hierarchy, generous but tight spacing, 6px corners
    (never sharp, never pill-like), engineered colour palettes, perfect RTL. Topic does not matter; the content decides
    which components to use and the theme decides the mood.
    
    ```
    pdf-atelier/
    ├── SKILL.md
    ├── assets/
    │   ├── fonts/            Vazirmatn 400/500/700, JetBrains Mono 400/700 (+ OFL licences)
    │   └── theme-gallery.pdf pre-rendered preview of all 12 themes
    ├── scripts/
    │   ├── setup.sh          installs weasyprint / pillow if missing
    │   ├── themes.py         OKLCH palette engine + 12 curated themes + contrast audit
    │   ├── pdfkit.py         Doc class: all components (import this)
    │   ├── example.py        runnable demo (RTL report + LTR proposal)
    │   ├── themes_preview.py regenerates the theme gallery PDF
    │   ├── render_preview.sh PDF -> PNG pages + contact sheet (visual QA)
    │   └── extras.py         OPTIONAL terminal/code windows - only if the content truly needs them
    └── references/
        ├── design-rules.md   spacing, type scale, colour engineering, layout patterns, checklist
        └── pitfalls.md       rendering traps and fixes
    ```
    
    ## Workflow
    
    1. **Setup once**: `bash <skill>/scripts/setup.sh` (fonts need no installation).
    2. **Choose the theme** (see table). If the user names a colour/brand, use `Theme.from_hex("#...")`. If they gave no
       hint, pick by subject and mention the theme name in one phrase; offer `assets/theme-gallery.pdf` when they want
       to browse.
    3. **Plan** pages and sections before writing: aim for 1-4 A4 pages (a dedicated `cover()` only for long formal
       documents). Map each piece of content to a component (table below). Keep text short; prefer tables, tiles,
       lists and charts over paragraphs. One idea per bullet.
    4. **Check facts and numbers with code** (totals, percentages, dates, conversions). Never do arithmetic by hand in
       the document. Keep units and spelling consistent everywhere.
    5. **Write the build script** (in `/home/claude`) and save to `/mnt/user-data/outputs/<name>.pdf`:
       ```python
       import sys; sys.path.insert(0, "/mnt/skills/user/pdf-atelier/scripts")    # use the real install path
       from pdfkit import Doc, mono, b, ul, tag
       doc = Doc(rtl=False, theme="ocean", title="Quarterly report")           # rtl=True for fa/ar/he
       doc.hero("Internal · Q3", "Quarterly report", "Highlights and next steps")
       doc.stats([("1.2M", "Revenue", "▲ 14%"), ("92", "NPS"), ("3,400", "Active users")])
       doc.h2("Regions"); doc.bars([("North", 480), ("South", 310)], colors=True)
       doc.save("/mnt/user-data/outputs/report.pdf")
       ```
    6. **Look at every page**: `bash <skill>/scripts/render_preview.sh <pdf> 75` then `view /tmp/preview/sheet.png`
       (zoom with `/tmp/preview/page-N.png`). Fix clipping, orphan headings, big empty areas, flipped symbols; re-render.
       Judge RTL by the picture, never by `pdftotext` (extracted RTL text always looks scrambled).
    7. **Deliver** with `present_files`. One or two sentences, no long recap.
    
    ## Themes (all contrast-audited: brand/white >= 7:1, body >= 7:1, muted >= 4.5:1, chips/badges >= 4.5:1)
    
    | theme | mood / use |
    |---|---|
    | `indigo` (default) | education, tech, product documents |
    | `ocean` | trustworthy blue: corporate, finance, reports |
    | `executive` | navy + gold: proposals, legal, premium |
    | `teal` | calm clean: health, science, wellness |
    | `emerald` | fresh: sustainability, growth, nutrition |
    | `forest` | earthy: nature, outdoors, organic |
    | `sunset` | warm orange: events, food, creative |
    | `crimson` | bold red: urgent, sports, awards |
    | `rose` | soft magenta: lifestyle, beauty, kids |
    | `violet` | creative purple: design, arts, music |
    | `graphite` | neutral grey: minimal, formal, print-first / B&W printers |
    | `paper` | warm sepia: essays, literature, long reading |
    
    Custom: `Theme.from_hex("#0f766e")` (whole palette from one colour) or
    `Theme.make("name", brand_hue=258, accent_hue=82, chroma=0.9)` (two-hue schemes) -> pass as `theme=`.
    `theme.audit()` returns every contrast pair with pass/fail; run it for custom themes and fix failures by changing
    chroma/lightness. Never hand-pick extra colours: use theme tokens (`doc.t["accent"]`, `doc.t["series"][i]`, ...).
    
    ## Components (`pdfkit.Doc`)
    
    | Need | Method |
    |---|---|
    | Full cover page (own page, no footer) | `cover(title, subtitle, tag_line, meta=[(k, v)])` |
    | Title banner on page 1 | `hero(tag_line, title, subtitle)` |
    | Section / sub-section / paragraph / intro | `h2(text, page_break=False)`, `h3`, `p`, `lead` |
    | Soft panel / callout (info, warn, ok, bad) | `card(html, title)`, `note(html, kind, title)` |
    | Numbered steps, chapters, features | `numbered(n, title, body_html, tags=[...])` |
    | KPI tiles | `stats([(value, label, note?)], colors=False)` (3-4 per row) |
    | Table (zebra, aligned columns, total row) | `table(headers, rows, widths, align, total_row)`; align: `start/end/center/ltr` |
    | Key-value list (contact, specs) | `kv([(k, v)])` |
    | Bar chart (pure CSS) | `bars([(label, value)], colors, fmt)` |
    | Timeline / roadmap | `timeline([(when, title, desc)])` |
    | Checklist | `checklist(["a", ("b", True)])` |
    | Two columns | `columns(left_html, right_html, ratio=(1, 1))` |
    | Quote | `quote(text, by)` |
    | Image / SVG with caption | `figure('<img src="file:///...">', caption)` |
    | Divider, page break, raw HTML | `divider()`, `pagebreak()`, `raw(html)` |
    | Inline helpers | `b()`, `mono()` (LTR code/IDs/English terms), `tag()`, `ul()`, `ol()` |
    
    Charts beyond bars: draw inline SVG (use theme colours) and pass it to `figure()`, or render with matplotlib to PNG
    using the theme colours and embed with `file://`.
    
    ## Design principles (details: `references/design-rules.md`)
    
    - Hierarchy: one hero/cover -> `h2` sections with an accent bar -> content in cards, tiles or tables.
    - Colour discipline: brand (dark) for banners and headings, ONE accent for markers, neutrals for surfaces;
      amber/green/red only for status callouts; series colours only for charts/chips.
    - Density: 10pt body, 1.7 line-height, 6px gaps. Prefer fewer, fuller pages; avoid pages with only 3 lines.
    - Components never split across pages (`page-break-inside: avoid`); use `h2(..., page_break=True)` to start a big
      block on a fresh page.
    - Write for the reader: short sentences, concrete numbers, no filler. Beginners: define a term once, in a chip or
      a table, not in a paragraph.
    
    ## Right-to-left (Arabic / Hebrew / Persian)
    
    - `Doc(rtl=True, lang="ar")` mirrors layout, bullets, accent bars, tables, timelines and charts automatically.
    - Wrap every Latin token inside RTL sentences (names, codes, formulas, URLs) in `mono()` so symbols never flip.
      For table columns with Latin/code content use `align="ltr"`; numbers use `align="end"`.
    - RTL typography: use the correct script variants and joiners for the language, and keep program output and IDs exactly as they are.
    - Footer page numbers stay LTR (`2 / 5`).
    
    ## Optional: terminal and code windows
    
    Only when the content genuinely shows software output: `from extras import TechDoc` (subclass of `Doc`) adds
    `terminal(...)` (macOS Terminal mockup, dark/light) and `code_window(...)`. Not part of the normal design system.
    
    ## Do not
    
    - Hide text in the PDF (white-on-white, tiny fonts, metadata tricks); it is unreliable and hurts accessibility.
    - Use `box-shadow` (WeasyPrint ignores it), wkhtmltopdf or reportlab for RTL, or hard-code hex colours outside the theme.
    - Deliver without having looked at every rendered page.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.