make-a-doc
Page-style document, printable out of the box
git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks /tmp/make-a-doc && cp -r /tmp/make-a-doc/Anthropic/claude-design/skills/make-a-doc ~/.claude/skills/make-a-docSKILL.md
# Make a doc Create a document (resume, one-pager, memo, letter, report, guide, paper). First decide which of two shapes the user wants — they export completely differently: **Flowing pages** — text that pours onto standard sheets (Letter/A4) and breaks wherever needed: reports, memos, letters, papers, guides. START by calling `copy_starter_component` with `kind: "doc_page.js"`, then write the whole document as normal flowing HTML inside `<doc-page size="letter" margin="0.75in">`. The component owns the sheet, the desk background, and all print geometry — do NOT write your own `@page` rule, body background, page-card divs, `break-after: page` fake sheets, or `break-inside: avoid` on items inside multi-column grids (a grid only breaks between rows, so a kept row that doesn't fit leaves a blank band). Print rules for flowing pages: multi-column text uses CSS columns (`column-count` + `column-gap`; `column-span: all` on a heading that spans; `hyphens: auto` in narrow columns — it needs `lang` on the html element), never side-by-side flex/grid columns — only real CSS columns flow and break across pages. Use `break-before: page` on anything that must start a new page (a chapter, an appendix); add custom kept-together blocks (callouts, stat tiles, cards) to a `break-inside: avoid` rule and keep each shorter than a page — the component already keeps headings with their content, keeps figures/code/table rows whole, and suppresses orphans and widows (extend `orphans: 3; widows: 3` to custom text blocks). Long tables get a `<thead>` so the header repeats on every page. No `position: fixed`/`sticky` and no viewport units in content — fixed elements stamp every printed page (running headers/footers go in the component's slots) and `100vh` mis-sizes at print. **Fixed sheet** — a design that must fill exactly one page of fixed dimensions: poster, infographic, social graphic, certificate. No starter component — build it at its true pixel size with an explicit px `width` (and `height` if fixed) on the top-level element; the export sizes the PDF page to it automatically. Do not write any `@page` rule for it. Styling (both shapes): body type 14–16px with generous line-height (1.55–1.7); clear heading hierarchy; restrained palette. Tables get a header row and hairline borders; figures and code blocks each carry a short caption. Open with the document's own h1 as the first body element (use any header-shaped first line of pasted content as that h1 rather than rendering it as a separate masthead).
Deep research harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report.
Author or improve the run-<unit> skill - a per-project skill that tells agents how to build, launch, and drive this project's app. Use when the user asks to set up the project, get it running, write run instructions, or verify build/run steps work from a clean environment.
Runtime capabilities a published Artifact page can be granted — behavior static HTML cannot provide on its own, such as the page reading live or connected data, remembering what people do on it (a poll, a sign-up sheet, a checklist, a document edited in place — it saves new versions of itself), keeping state shared across viewers, knowing who is viewing, asking Claude a question of its own, storing files people add, or handing the viewer a file to save. Serves this user's live capability roster and the typed call definitions. Load it whenever the user asks for an artifact needing any such runtime behavior.
Design guidance and fundamentals for Artifacts.
Diagramming know-how for Artifacts - when a picture earns its place, how to draw one that shows the real mechanism, and the inline-SVG mechanics that keep it legible in both themes.
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
Automates your Chrome browser to interact with web pages - clicking elements, filling forms, capturing screenshots, reading console logs, and navigating sites. Opens pages in new tabs within your existing Chrome session. Requires site-level permissions before executing (configured in the extension).
Review the current diff, or a PR number/branch/path target, for correctness bugs and reuse/simplification/efficiency cleanups at the given effort level (low/medium: fewer, high-confidence findings; high→max: broader coverage, may include uncertain findings; ultra: deep multi-agent review in the cloud); with no level given, it reuses the level you typed last. Pass --comment to post findings as inline PR comments, or --fix to apply the findings to the working tree after the review. For ultra on a GitHub.com PR target, --post asks to post the finished review’s findings to the PR as a single comment from the user’s GitHub account (not a review; the launch dialog still confirms in interactive sessions, while non-interactive mode posts on the flag alone) and --no-post hides that option.