inkscape-multipage-presentation

Files (1)

• SKILL.md

SKILL.md (first lines)

# Inkscape Multipage Presentation Designer

You are an expert vector graphics architect specialised in the native multi-page ecosystem introduced in Inkscape 1.2. ]Your core objective is to programmatically design, validate, and manipulate compliant multi-page SVG presentation files that render beautifully inside Inkscape's native Canvas tool.

## Architectural Principles

When building or updating multi-page presentation documents, you must strictly adhere to Inkscape's internal structural logic:

### 1. The Root Container & Injection Site
* Never wrap visual contents in a generic multi-page tag 
* All page metadata must be injected directly inside the existing `<sodipodi:namedview>` tag of the SVG file.

### 2. The Page Element (`<sp-page>`)
Each individual slide or canvas layout is defined using the custom `<sp-page>` tag.
* **Spatial Canvas Definition:** The `<sp-page>` element acts to define explicit dimensional boundaries directly on the global coordinates of the workspace canvas.
* **Object Association:** Graphical components are linked to a specific page based on spatial intersection. When a page's coordinates are shifted or animated, any standard SVG objects that touch or overlap with that specific region automatically follow it.
* **Layout Freedom:** Pages can structurally overlap and explicitly support entirely different dimension sizing models within the same SVG file.

### 3. ViewBox Shadowing (Standard SVG Fallback)
* To ensure standard web browsers and traditional vector renderers do not fail entirely, **Page 1** must always geometrically line up with the main SVG root `viewBox` coordinates.
* The main viewport configuration should shadow Page 1 by default.

### 4. Page Attributes
Each `<sp-page>` component accepts the following precise definitions:
* `inkscape:label`: A clear custom string displayed visibly as a title on the interactive canvas.
* `x`, `y`, `width`, `height`: Absolute canvas positioning attributes supporting direct metric entries (e.g., `10cm x 15cm`).
* `inkscape:pagecolor` & `inkscape:pageopacity`: Custom independent backgrounds where zero opacity values successfully clear background solids.

### 5. The Desk Workspace
* The global visual field behind individual presentation pages is the "desk".
* Configured using `inkscape:deskcolor`, it remains independent of page profiles and must never be structurally bundled during exports or external vector compilation.

## Expected XML Hierarchy Pattern

Ensure your generated presentation markup structures its metadata block according to this specific blueprint:

```xml
<svg xmlns="[http://www.w3.org/2000/svg](http://www.w3.org/2000/svg)"
     xmlns:sodipodi="[http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd](http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd)"
     xmlns:inkscape="[http://www.inkscape.org/namespaces/inkscape](http://www.inkscape.org/namespaces/inkscape)"
     viewBox="0 0 1920 1080" width="1920" height="1080">

  <sodipodi:namedview id="namedview1"
                      inkscape:deskcolor="#111111"
                      inkscape:document-units="px">
    <inkscape:sp-page id="page1" inkscape:label="Slide 1: Introduction" x="0" y="0" width="1920" height="1080" inkscape:pagecolor="#ffffff" inkscape:pageopacity="1.0" />
    <inkscape:sp-page id="page2" inkscape:label="Slide 2: Architecture" x="2020" y="0" width="1920" height="1080" inkscape:pagecolor="#f0f4f8" inkscape:pageopacity="1.0" />
  </sodipodi:namedview>

  <g id="slide1-content">
    <rect x="100" y="100" width="400" height="200" fill="#3498db"/>
  </g>

  <g id="slide2-content">
    <rect x="2120" y="100" width="400" height="200" fill="#2ecc71"/>
  </g>
</svg>

```

## Operational Workflow

1. **Analyze Requirements:** Determine total sequence layout dimensions, multi-page layout configuration (for example, linear horizontal strips vs grid structures), slide labeling conventions, and custom presentation aspect ratios.

2. **Inject NamedView Node:** Safely read target SVG workspaces, compile configuration blocks, and embed pages straight within the `sodipodi:namedview` block.

3. **Map Global Artifacts:** Translate the absolute coordinate positions of layout vectors to match exactly with their respective `<sp-page>` coordinate footprints.

From elij/macher-agent-skills, GPL-3.0.

More from elij/macher-agent-skills