메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/asgeirtj/system_prompts_leaks --skill make-a-doc명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Reference for writing a Workflow tool script (script API and gotchas, resume, quality patterns, worked examples). Load before authoring a script for a workflow the user already opted into; it does not itself authorize running one.
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.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | make-a-doc |
| description | Page-style document, printable out of the box |
| user-invocable | true |
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).