flier
Print-ready single page
git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks /tmp/flier && cp -r /tmp/flier/Anthropic/claude-design/skills/flier ~/.claude/skills/flierSKILL.md
# Flier Design a print-ready, single-page flier as one self-contained HTML file: exactly one fixed-size page. Sheet setup: - START by calling copy_starter_component with kind: "doc_page.js", then build the flier as ONE explicitly paginated page: <doc-page><section class="page" id="flier">…</section></doc-page>. The component owns the page box, the desk background that disappears at print, the page break discipline, and all print geometry — do NOT write your own @page rule, body background, or hard-coded paper dimensions, and never add an omelette-owns-print meta. The print dialog must show exactly 1 page. - The flier prints as a FIXED full-bleed page box with overflow hidden — letter by default, the user's chosen paper (letter, A4, …) when they export — so content that misses the box is clipped, never reflowed. Design the flier to FILL the page box and fit letter and A4 alike without overlap. - The page is full-bleed: the flier owns its own inset — keep a visual margin of at least 4% of the page on every edge, and keep everything inside it. - Never viewport units (vh/vw) — they track the window, not the page. A flier is read at a distance, in passing, in under three seconds: - One dominant element — usually a headline under ~6 words — sized so it reads across a room (think 8cqh+), everything else clearly subordinate. - The five Ws grouped tight and scannable: what, when, where, cost, and one way to act (QR-sized URL, phone number, or tear-off) — not scattered through prose. - Strong flat color blocks and vector shapes over photos and gradients; high contrast; body text in near-black on light stock. - Generous whitespace beats more words — cut copy until the hierarchy is unmissable. - Optional: a tear-off fringe along the bottom edge (a row of narrow cells with dashed left borders and rotated contact text) when the user wants phone-number slips. Check the print preview: nothing clipped, nothing spilling to page two, colors that still work in grayscale.
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.