open-slide

Create a folder slides/<kebab-case-id>/ containing a single index.tsx that default-exports a non-empty array of zero-prop React page components. Optionally export meta, design, and notes, and generate meta.createdAt with node -e "console.log(new Date().toISOString())" just before writing.

Read node_modules/.open-slide/current.json fresh at the start of the turn to get slideId, pageIndex, pagePath, and selection. Use pagePath for source edits and pageIndex to locate the component in the default export array; ask the user if the file is stale or missing.

Every page renders into a fixed 1920x1080 canvas that the framework scales. Use absolute pixels for type and spacing, avoid rem, vw, and vh, and verify the vertical budget fits within 1080px without scrolling or hidden overflow.

Inspector comments persist as JSX markers like {/* @slide-comment id="c-<hex>" ts="<ISO>" text="<base64url>" */}. Decode the base64url text to get the note, apply the smallest faithful edit to the enclosing element in reverse line order, then remove the marker.

No. A slide must remain one index.tsx plus an optional assets/ folder. Define repeated elements like cards as small components inside the same file and instantiate each explicitly rather than using array.map, so the inspector can edit instances individually.

Do not use it for unrelated React apps, generic presentation advice, or editing the Open Slide framework internals unless explicitly asked. It also should not modify package.json, dependencies, or other decks during normal slide authoring.