better-documentslisted

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.
jackson2w/claude-code-skills · ★ 1 · Data & Documents · score 64

Install: claude install-skill jackson2w/claude-code-skills

# Document Review Apply communication best practices when generating or reviewing any business document — whether the right message reaches the right audience in the right order. This skill applies the principles from Anil Dash's [Make better documents](https://www.anildash.com/2024/03/10/make-better-documents/). ## Scope This skill covers **business documents**: presentations, slide decks, proposals, reports, memos, briefs, one-pagers, and emails. It does not cover UI, web components, or frontend applications — use the `frontend-design` skill for those. The design principles here differ from frontend design in important ways: - **Restraint over expression.** UI benefits from bold aesthetic commitment and distinctive visual personality. Business documents benefit from getting out of the way of the content. Most people reading a board deck or a client proposal are not there to appreciate the typography. - **The audience can't interact.** A web interface rewards exploration. A document gets one read, often skimmed, often on a small screen or printed. Every design choice that draws attention to itself is attention stolen from the message. - **Non-designers are both authors and audiences.** UI is built and consumed with design context nearby. Business documents are built by operators, analysts, executives, and founders — and read by the same. Complexity that a designer handles intuitively becomes noise for everyone else. ## Modes | Mode | When to use | W