docs-designer
/docs-designer
Zamienia rozmowę lub wcześniejszą sesję Claude Code w zaprojektowany dokument PDF w formacie A4, po angielsku lub bułgarsku, z nazwiskiem autora i datą.
- Autor
- iystoychev ↗
- Repozytorium
- docs-designer ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 41
- Skrypty
- 5
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 5 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: assets/inspector.js, scripts/blocks.py, scripts/extract_session.py, scripts/inspect_server.py, scripts/render.py
Co robi i kiedy
Zamienia rozmowę lub wcześniejszą sesję Claude Code w zaprojektowany dokument PDF w formacie A4, po angielsku lub bułgarsku, z nazwiskiem autora i datą.
Wyzwalacze z opisu
Oryginalny opis (EN)
Turn a conversation or a previous Claude Code session into a designed A4 PDF (report, memo, guide, proposal or technical requirements) in one consistent design language, with the author's name and creation date, in English or Bulgarian. Use when the user asks to document, write up, summarize, export or "make a PDF/report/memo/guide/proposal/spec/assignment" from this conversation or a past session, e.g. "turn this into a PDF", "write up what we decided as a memo", "make the requirements doc".
Jak działa
- 1. Get the source
- 2. Pick the kind
- 3. Distill
- 4. Write two files (in a scratch/temp directory, not the user's repo)
- 5. Render
- 6. Check and report
- Inspector (optional)
Podgląd SKILL.md
---
name: docs-designer
description: Turn a conversation or a previous Claude Code session into a designed A4 PDF (report, memo, guide, proposal or technical requirements) in one consistent design language, with the author's name and creation date, in English or Bulgarian. Use when the user asks to document, write up, summarize, export or "make a PDF/report/memo/guide/proposal/spec/assignment" from this conversation or a past session, e.g. "turn this into a PDF", "write up what we decided as a memo", "make the requirements doc".
---
# docs-designer
Turn conversation content into an A4 PDF printed through one shared design system. Your job is editorial: choosing what matters and writing it well. The design is fixed in code (`assets/`, `scripts/render.py`) and must never be changed per document.
`SKILL_DIR` below means the directory that contains this file.
## 1. Get the source
- **This conversation (default):** use what is already in your context.
- **Another session:** list the candidates, then extract one:
```bash
python3 SKILL_DIR/scripts/extract_session.py --list --project "$PWD"
python3 SKILL_DIR/scripts/extract_session.py <session-id> # or a path to a .jsonl
python3 SKILL_DIR/scripts/extract_session.py --latest --skip-current --project "$PWD"
```
Redirect long output to a scratch file and read it in parts.
- **A file the user gives you** (PDF, Markdown, notes): read it and use it as the source.
## 2. Pick the kind
| `kind` | Use for | Front page |
|---|---|---|
| `report` | findings, technical summaries, recaps, decision records | full cover: title, summary, key point |
| `memo` | a short decision or announcement (1–2 pages) | no cover; compact head, body starts on page one |
| `guide` | how-tos, onboarding, step-by-step instructions | cover with a contents map |
| `proposal` | a plan or request that someone must approve | cover that leads with the recommendation |
| `requirements` | specs, assignment briefs, acceptance criteria | cover with a contents map; requirements numbered across the document |
If the user names a kind, use it. Otherwise pick the closest one, and ask only when two fit equally well.
## 3. Distill
- Lead with the outcome. Keep final code, commands, names, numbers and dates exactly as they appeared.
- **Never invent anything.** Every claim, number and quote must come from the source. If something is unresolved, say so.
- **The document never mentions Claude, the AI, the chat or the session.** Write as the author's own document about its subject. The only exception is when the user explicitly asks for that.
- Write in the language the user wants. Use `"lang": "bg"` for Bulgarian (labels, dates and headings switch automatically). If the user hasn't said, use the language of the source.
- Keep it short. A memo is 1–2 pages; most reports and guides are 2–6.
## 4. Write two files (in a scratch/temp directory, not the user's repo)
**`doc.json`**: plain text only. The renderer escapes it.
```json
{
"kind": "report",
"lang": "en",
"title": "Short, specific title (≤ 8 words works best)",
"subtitle": "Optional one-line framing",
"abstract": "Optional. 2–4 sentences shown on the front page",
"outcome": "Optional. The single most important point, struck in cobalt on the front page",
"meta": {"Status": "Draft", "Version": "1.2"},
"body": "body.html"
}
```
- `meta` adds extra labelled cells to the front-page form, in the order given, for example `To` (memo), `Prepared for` (proposal), `Audience` (guide) or `Revision` (requirements). Use labels in the document's language.
- The front page labels `outcome` per kind: Outcome, Decision, Goal, Recommendation or Objective.
- Leave `author` out unless the user names someone. It defaults to `git config user.name`, and `--author` overrides it. **The date is always the render date**, so never add one.
**`body.html`**: a fragment that uses **only** this vocabulary. Look at `examples/<kind>/body.html` for each kind. Don't use `<style>`, `style=`, `<script>` or `<h1>`; the renderer rejects them.
| Element | Use for |
|---|---|
| `<p class="lede">` | optional opening paragraph, once at the top |
| `<h2>`, `<h3>`, `<h4>` | sections (numbered 1, 1.1 automatically; `h2` feeds the contents map), and unnumbered `h4` sub-heads |
| `<p>`, `<ul>`, `<ol>`, `<strong>`, `<em>`, `<code>`, `<a>` | prose |
| `<ol class="requirements"><li><p>…</p></li></ol>` | numbered requirements; numbering continues across every list in the document |
| `<div class="callout decision">` | a decision and its reason |
| `<div class="callout warning">` | a risk, a gotcha or something not to do |
| `<div class="callout note">` | an aside that matters |
| `<div class="callout aside">` | allowances, exceptions, permitted deviations (set in italic) |
| `data-label="…"` on any callout | renames its rail label, e.g. `data-label="Allowed deviations"` |
| `<dl class="keyfacts"><div><dt>Label</dt><dd>Value</dd></div>…</dl>` | 3, 6 or 9 short facts (dates, versions, counts, owners) |
| `<ol class="steps"><li><p>…</p></li>…</ol>` | a procedure; a `<pre>` may sit inside a step |
| `<pre data-label="Shell"><code>…</code></pre>` | code or commands (escape `<`, `>` and `&`). Keep lines ≤ 68 characters |
| `<table><caption>…</caption><thead>…</thead><tbody>…</tbody></table>` | comparisons. `class="num"` right-aligns numbers, `<tr class="group">` marks a subtotal or group row, `<tfoot>` holds a total, and `<table class="long">` lets a long table break across pages |
| `<blockquote><p>…</p><cite>…</cite></blockquote>` | someone's exact words, only when the wording matters |
| `<figure>…<figcaption>…</figcaption></figure>` | an inline SVG diagram or `<img>` (paths are relative to doc.json); draw in ink, not cobalt |
Colour carries meaning: cobalt marks decisions and the front-page key point, and amber marks warnings. Don't use them for anything else.
## 5. Render
```bash
python3 SKILL_DIR/scripts/render.py /path/to/doc.json --out "$PWD/docs/<slug>-<YYYY-MM-DD>.pdf"
```
Without `--out`, the file goes to `./docs/<title-slug>-<date>.pdf`. Ask before writing into the user's repo if they didn't give a location. The renderer needs Google Chrome or Chromium (`CHROME_PATH` can point to it).
## 6. Check and report
Read the PDF back. Check that the front page shows the title, author and date, that no section is empty, and that tables and code aren't cut off. Then give the user the path and a one-line summary. If the render fails, fix the body (usually a forbidden element or invalid JSON), never the stylesheet.
## Inspector (optional)
Every render records itself in `~/.docs-designer/last.json`. With the docs-inspector mod installed, the document opens in a pane where the user can click any text to edit it or send you an instruction about it. Those instructions arrive as a prompt that names the element, its section, its current text and its file. Apply them to that element in the source and re-render to the same PDF path. Without the mod, `python3 SKILL_DIR/scripts/inspect_server.py` serves the same inspector at http://127.0.0.1:8765.
Pliki w paczce (41)
- SKILL.md 7 KB
- assets/inspector.css 4 KB
- assets/inspector.js 7 KB
- assets/style.css 22 KB
- assets/template.html 1 KB
- assets/fonts/JetBrainsMono-normal-cyrillic-ext.woff2 2 KB
- assets/fonts/JetBrainsMono-normal-cyrillic.woff2 9 KB
- assets/fonts/JetBrainsMono-normal-latin-ext.woff2 11 KB
- assets/fonts/JetBrainsMono-normal-latin.woff2 31 KB
- assets/fonts/OFL.txt 5 KB
- assets/fonts/RobotoFlex-normal-cyrillic-ext.woff2 65 KB
- assets/fonts/RobotoFlex-normal-cyrillic.woff2 102 KB
- assets/fonts/RobotoFlex-normal-latin-ext.woff2 140 KB
- assets/fonts/RobotoFlex-normal-latin.woff2 191 KB
- assets/fonts/SourceSerif4-italic-cyrillic-ext.woff2 45 KB
- assets/fonts/SourceSerif4-italic-cyrillic.woff2 88 KB
- assets/fonts/SourceSerif4-italic-latin-ext.woff2 108 KB
- assets/fonts/SourceSerif4-italic-latin.woff2 127 KB
- assets/fonts/SourceSerif4-normal-cyrillic-ext.woff2 44 KB
- assets/fonts/SourceSerif4-normal-cyrillic.woff2 91 KB
- assets/fonts/SourceSerif4-normal-latin-ext.woff2 98 KB
- assets/fonts/SourceSerif4-normal-latin.woff2 119 KB
- assets/fronts/guide.html 1 KB
- assets/fronts/memo.html 1 KB
- assets/fronts/proposal.html 1 KB
- assets/fronts/report.html 1 KB
- assets/fronts/requirements.html 1 KB
- examples/guide/body.html 1 KB
- examples/guide/doc.json 1 KB
- examples/memo/body.html 1 KB
- examples/memo/doc.json 1 KB
- examples/proposal/body.html 1 KB
- examples/proposal/doc.json 1 KB
- examples/report/body.html 3 KB
- examples/report/doc.json 1 KB
- examples/requirements/body.html 6 KB
- examples/requirements/doc.json 1 KB
- scripts/blocks.py 6 KB
- scripts/extract_session.py 5 KB
- scripts/inspect_server.py 9 KB
- scripts/render.py 14 KB
Wersje
W bazie nie ma innych skilli o nazwie docs-designer.
Migawka bazy z 13.11.2026 · wersja paczki 1be99d413013 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100docs-artifact
Tworzy, edytuje i przegląda dokumenty dla użytkownika (Word, Google Docs, PDF), np. memo, raport, propozycję lub brief, oraz odpowiada na pytania wymagające zajrzenia do istniejącego dokumentu. - 90pressroom
Tworzy dokument, list, raport, CV, ofertę, notatkę lub plik PDF na podstawie opisu użytkownika. - 100share
Tworzy i publikuje w p11 dokumenty do komentowania, np. propozycje, raporty i specyfikacje, gdy działa Claude Code. - 100hk-pdf-export
Zamienia stronę HTML w PDF w firmowym stylu i sprawdza, czy po drodze nic nie zginęło. - 100report-pdf
Zamienia raport Markdown z zespołu deweloperskiego w ostylowany PDF do załączenia do ticketu lub przekazania interesariuszowi. - 100pdf
Tworzy od zera, wypełnia i przeformatowuje PDF-y o dopracowanym wyglądzie: raporty, oferty, CV i dokumenty gotowe dla klienta.