Install
Design Philosophy Creation (.md file)Who it is for
Use canvas-design when the user asks for a poster, a piece of work, graphic design, or another static visual. It produces .png and .pdf from a design philosophy, and the work must be original: do not copy an existing artist’s work, so you avoid copyright problems.
A better fit is accepting that you output only three file types — .md, .pdf, and .png — and that you write the visual philosophy before it lands on the canvas. The source material does not give an agent-product list or an installer; do not invent a repository path. The official description page is
https://raw.githubusercontent.com/anthropics/skills/main/skills/canvas-design/SKILL.md
First attempt in 3 minutes
The recommended path is the first of two steps; do not generate a poster file yet. The source material states: 1. Design Philosophy Creation (.md); 2. express it on the canvas (.pdf or .png). There is no second install command; do not add an installer that never appeared.
Prerequisite: you already have a static visual theme. Low-risk first move: draft only the visual philosophy, do not write a layout template. The philosophy is to be read through form, space, color, and composition; it also includes images, graphics, shapes, and patterns; type is only the smallest visual accent. The philosophy must repeat craft: the finished piece should look as if countless hours were spent, as if it were carefully polished, and as if it came from a top practitioner in that field.
Writing a .md will hit disk; confirm the filename and directory before saving. Success signal: a philosophy draft that is not a layout spec, that repeats the craft requirement, and that has not yet exported png/pdf. Do not enter step two before the philosophy is confirmed, and do not copy a reference image first.
Usage cases
Case 1: Write the visual philosophy first for a poster task. Output can only be .md. The content is a visual movement, not a column template. The done criterion is that the file shows a stance on form, space, color, and composition, type is treated as accent, and the craft requirement is repeated. Do not embed a full poster sketch in this step. The source material does not give a filename template for the philosophy file, so do not invent a required filename.
Case 2: Land the same philosophy on the canvas. Step two generates .pdf or .png. The finished piece should be about 90% visual design and 10% necessary type. This writes to disk: confirm the output format and whether you would overwrite an existing image before exporting. The done criterion is that the canvas work shows the form and color from the philosophy, not long explanatory copy. Do not copy the recognizable style of a living or existing artist. The excerpt does not write a concrete drawing-library command, so do not invent a renderer name.
Boundaries
Output only .md, .pdf, .png. Philosophy first, canvas second. The philosophy is not a layout template and should not be written as a component-library note. Canvas work is visual first, type second. Top-level craft must be repeated. Copying existing artists’ work is forbidden.
Do not invent an installer or an in-repo path. The source material does not give font files, a print-size table, or a client list. Confirm before overwriting an existing .png/.pdf. Anything beyond these stated file types, two-step order, and originality requirement is outside this guide. If the user wants an editable project file or a dynamic page, not a static png/pdf, do not follow this path. Before step one is confirmed, do not export finished images in several sizes in parallel. Align the philosophy first, then take visual risk on the canvas.