Skip to content

jackson2w/claude-code-skills / better-documents

better-documents

Verified

Apply communication best practices when generating or reviewing any document, presentation, report, memo, slide deck, proposal, or email. Use this skill when asked to write, create, draft, or generate a document or presentation — apply the principles at generation time, not as an afterthought. Also use when asked to "review my doc," "look at this deck," "does this make sense," "is this clear," "improve this proposal," "check this before I send it," "make this more effective," or any request to evaluate whether a document will land with its audience. Use this skill even when the request seems minor — a "quick look" or a "short memo" is exactly when these principles matter most.

FileKindSize
BLOG-NOTES.mdmarkdown4.5 KB
LICENSEother34.3 KB
README.mdmarkdown3.2 KB
SKILL.mdskill md12.9 KB
document-design.mdmarkdown6.5 KB

BLOG-NOTES.md

View on GitHub
# Blog post notes: promoting the better-documents skill

## The key insight / lede

There is **no Anthropic guidance anywhere** — not in system prompts, not in
the skills library, not in the cookbook, not in the prompting docs — that covers
the design of business documents Claude generates on behalf of users.

The `frontend-design` skill (293K+ installs, #2 on skills.sh) exists specifically
to stop Claude from producing "AI slop" UIs. It is explicitly scoped to web
components and applications.

Nobody has done this for documents.

Claude Opus 4.7 has a documented default house style — cream backgrounds, serif
display type, terracotta accents — that Anthropic's own docs note "appears in
slide decks as well as web UIs" and "will feel off for dashboards, dev tools,
fintech, healthcare, or enterprise apps." The recommended fix in Anthropic's
docs is to specify a concrete alternative or ask the model to propose options.
This skill does both, automatically.

So: there is a 293K-install skill that stops Claude from making ugly websites.
There is nothing that stops Claude from making ugly (or just eerily identical)
board decks, client proposals, and status reports. Until now.

---

## Angles / framings to explore

**The symmetry angle**
The `frontend-design` skill for devs, the `better-documents` skill for everyone
else. Devs already know to install skills for this kind of thing. Business users
don't. This is the version that reaches them — via LinkedIn, not GitHub.

**The "you can already tell" angle**
People are starting to recognize Claude-generated documents the same way they
recognize AI-generated images. The cream background, the Playfair headline, the
tiny all-caps kicker above the body copy block. It's a tell. This skill fixes
the tell — but more importantly, it fixes the underlying communication problems
that make AI-generated documents feel thin even when they look fine.

**The original post angle**
Link back to "Make better documents" (March 2024) as the source material — now
translated into something a coding agent can actually act on. The post was about
human authors; the skill is about AI authors. Same principles, different actor.

**The gap-in-the-ecosystem angle**
The agent skills ecosystem is massive and growing fast — 90K+ skills on
skills.sh, official repos from Vercel, Anthropic, Microsoft, Stripe. It has
deep coverage of code, UI, deployment, marketing copy. Business document
communication is almost entirely absent. The only adjacent things are
`sciwrite` (academic manuscripts) and some marketing copy skills. Nothing for
the documents most knowledge workers produce every day.

---

## Key points to make in the post

1. The skills ecosystem solves a real problem — you no longer have to re-explain
   your preferences to your AI every session. But the catalog reflects what
   developers built, not what knowledge workers need.

2. Business document design has different rules from UI design. Restraint beats
   expression. The audience can't interact. Non-designers are in the loop at
   every stage. These aren't obvious things and Claude doesn't know them by
   default.

3. Anthropic's own docs document the Opus 4.7 default style as a known problem
   for non-editorial, non-hospitality contexts — and note it shows up in slide
   decks. No skill addresses this for documents.

4. The skill doesn't just fix aesthetics. The communication principles (audience
   first, conclusion up top, no murder mysteries, answerable questions) are the
   more important half. The visual stuff is just the most visible symptom.

5. This is installable in one command and works across Claude Code, Cursor,
   Codex, and every other SKILL.md-compatible agent.

---

## Distribution notes

- Primary channel: LinkedIn (business productivity audience, not devs)
- Secondary: link from the original "Make better documents" post
- Potential: mention in a Claude.ai conversation or project instructions for
  people who don't use Claude Code
- The skill itself should link back to the blog post; the blog post should
  link to the GitHub repo and the original 2024 post

---

## Things to verify before publishing

- [ ] Test the skill against a few real document generation prompts to confirm
      the visual style override actually fires
- [ ] Check whether skills.sh has a "business documents" or "productivity"
      category to file under
- [ ] Confirm the `npx skills add` install command path once the repo is live
- [ ] Decide whether to publish under anildash.com GitHub or a new repo
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall