[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CY5WHFGASZATK5CQF05G0A":3,"skill-same:01M7CY5WHFGASZATK5CQF05G0A":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CY5WHFGASZATK5CQF05G0A","slide-authoring",null,"Technical reference for writing or editing open-slide pages — file contract, 1920×1080 canvas, type scale, layout, palette\u002Fvisual direction, assets, speaker notes, stepped reveals, page transitions, and morph transitions. Consult this whenever you are about to write or modify any file under `slides\u002F\u003Cid>\u002F`, including from inside the `create-slide` or `apply-comments` workflows, or for any ad-hoc slide edit. Triggers on phrases like \"edit slide\", \"tweak this page\", \"fix the layout\", \"change the palette\", \"reveal one by one\", \"add a transition\", \"morph transition\", \"write the speaker notes\", \"generate the script \u002F talk track\", \"investigate the slide framework\", \"how do slides work here\".","BotHarness\u002FDeepSeekBot","BotHarness","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F330270786?v=4","01M7CX37EXWM53FHAQ28JNKZTZ","01M7CX37FHA8NY5D2KXFZWV63Y",852,"MIT","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: slide-authoring\ndescription: Technical reference for writing or editing open-slide pages — file contract, 1920×1080 canvas, type scale, layout, palette\u002Fvisual direction, assets, speaker notes, stepped reveals, page transitions, and morph transitions. Consult this whenever you are about to write or modify any file under `slides\u002F\u003Cid>\u002F`, including from inside the `create-slide` or `apply-comments` workflows, or for any ad-hoc slide edit. Triggers on phrases like \"edit slide\", \"tweak this page\", \"fix the layout\", \"change the palette\", \"reveal one by one\", \"add a transition\", \"morph transition\", \"write the speaker notes\", \"generate the script \u002F talk track\", \"investigate the slide framework\", \"how do slides work here\".\n---\n\n# Authoring open-slide pages\n\nThis skill is the **technical reference** for everything that happens inside `slides\u002F\u003Cid>\u002Findex.tsx`. It does not own a workflow:\n\n- `create-slide` owns \"draft a new deck\" — it asks the user scoping questions, then delegates the *how* to this skill.\n- `apply-comments` owns \"process inspector markers\" — it finds markers and applies edits, but the edits themselves follow the rules here.\n- `current-slide` resolves deictic references (\"this page\", \"the slide I'm on\") to a concrete `slideId` + `pageIndex`. Consult it **first** when the user references the current slide without naming it, then come back here for how to edit it.\n- Any ad-hoc slide edit (manual tweak, one-off fix) should also consult this skill before touching the file.\n\nWhen any of those paths reach the point of *writing React code for a page*, this is the source of truth. Do not duplicate the knowledge below into other skills — link here instead.\n\n## Primitive references\n\nEach framework primitive has a full reference file under `references\u002F` in this skill — contract, worked examples, and its own anti-patterns. This file keeps only the always-on rules and a short summary per primitive. **Read the relevant reference file before using a primitive on a page**:\n\n| Primitive | Read before | File |\n| --- | --- | --- |\n| `design` const + `var(--osd-X)` tokens | writing any new slide (default baseline) | `references\u002Fdesign-system.md` |\n| Assets + `\u003CImagePlaceholder>` | importing images\u002Fvideos or leaving a placeholder | `references\u002Fassets.md` |\n| Webfonts | loading any non-system font | `references\u002Fwebfonts.md` |\n| `useSlidePageNumber()` | rendering a page-number footer | `references\u002Fpage-numbers.md` |\n| `\u003CSteps>` \u002F `\u003CStep>` | staging a page's reveal | `references\u002Fsteps.md` |\n| `SlideTransition` | declaring any enter\u002Fexit animation | `references\u002Ftransitions.md` |\n| `MorphElement` + `morph` | morphing a shared element across pages | `references\u002Fmorph.md` |\n\n## Hard rules\n\n- Put the slide under `slides\u002F\u003Ckebab-case-id>\u002F`.\n- Entry is `slides\u002F\u003Cid>\u002Findex.tsx`. Images\u002Fvideos\u002Ffonts go under `slides\u002F\u003Cid>\u002Fassets\u002F`.\n- Do **not** touch `package.json`, `open-slide.config.ts`, or other slides.\n- Do not add dependencies. Only `react`, `@open-slide\u002Fcore`, and standard web APIs are available.\n- A slide is **one `index.tsx` plus `assets\u002F`** — nothing else. Do not create sibling `.tsx`\u002F`.ts` files (`Card.tsx`, `components\u002F`, `helpers.ts`, etc.); helper components and constants go inside `index.tsx`. Do not create `README.md` or other prose files either — speaker notes \u002F a talk script belong in the `notes` export (see **Speaker notes** below), not in a markdown file.\n\n## File contract\n\n```tsx\n\u002F\u002F slides\u002F\u003Cid>\u002Findex.tsx\nimport type { Page, SlideMeta } from '@open-slide\u002Fcore';\n\nconst Cover: Page = () => \u003Cdiv>…\u003C\u002Fdiv>;\nconst Body: Page = () => \u003Cdiv>…\u003C\u002Fdiv>;\n\nexport const meta: SlideMeta = {\n  title: 'My slide',\n  createdAt: '2026-05-16T12:00:00Z',\n};\nexport default [Cover, Body] satisfies Page[];\n```\n\n- `export default` is a **non-empty array of zero-prop React components**, one per page, in order.\n- `meta.title` (optional) shows in the slide header. Default is the folder name.\n- The slide id is the kebab-case folder name. Pick something short and descriptive (`q2-roadmap`, `team-offsite-2026`).\n- `meta.theme` (optional) marks the slide as built from a theme under `themes\u002F`. The id must match a `\u003Cid>.md` basename. Surfaces a back-link chip on the slide card and lists the slide on `\u002Fthemes\u002F\u003Cid>`. Omit if the slide isn't derived from a registered theme.\n- `meta.createdAt` is an **ISO 8601 string literal** (e.g. `'2026-05-16T12:00:00Z'`) set once when the slide is scaffolded. The home page uses it for the default \"newest first\" sort. Always include it on new slides — **immediately before writing the file, run `node -e \"console.log(new Date().toISOString())\"` via Bash and paste the exact output** as the value. Don't type a timestamp from memory — you will get the date or time wrong. Must be a plain string literal (no `new Date(...)` or imports in the slide itself) — the framework reads it via a regex at build time, not by evaluating the module.\n\n## Speaker notes (`notes` export)\n\nThe framework has **built-in speaker notes**: an optional `notes` export in `index.tsx`, index-aligned with the default page array. The viewer shows them in the notes drawer and present mode shows them in the presenter view next to the timer.\n\n**When the user asks for a speech script, talk track, or presenter notes — in any language — write it into this export, never into a markdown\u002Ftext file.** A `script.md` or `notes.md` is invisible to the runtime; the `notes` export is the only place the presenter view reads.\n\n```tsx\nexport const notes: (string | undefined)[] = [\n  'Open with the analyst quote, then introduce yourself.',\n  undefined,\n  `Walk through the three pillars, one beat each.\nPause for questions before moving on.`,\n];\n```\n\n- One entry per page, same order as the `export default` array. `notes[0]` belongs to the first page.\n- Entries are **plain text** — line breaks are preserved, markdown is not rendered. Use a template literal for multi-line notes, a normal string for one-liners.\n- Use `undefined` for a page with no notes; trailing `undefined` entries can be dropped.\n- When you add, remove, or reorder pages, re-align `notes` in the same edit — a shifted index silently attaches the wrong script to every page after it.\n- Write notes as something to *say*, not a summary of what's on screen: openers, transitions, numbers to cite, timing cues.\n\n## Editing an existing slide\n\nA finished slide commonly runs 1000–1800 lines. When you only need to touch one page, **don't read the whole file** — locate the page first, then read just that range:\n\n```bash\ngrep -n \": Page = \" slides\u002F\u003Cid>\u002Findex.tsx\n```\n\nThis lists every `const Foo: Page = …` declaration with its line number. Read the target page with `Read` using `offset` + `limit` (~150 lines is usually enough to capture one page plus its helper components). Read the whole file only when you need cross-page context (palette audit, reordering, design const tweaks).\n\n## Canvas\n\nEvery page renders into a fixed **1920 × 1080** canvas. The framework scales it; you design as if the viewport is literally 1920×1080.\n\n- Use **absolute pixel values** for `font-size`, padding, positioning. No `rem`, no `vw`\u002F`vh`, no `%` for type.\n- The root element of each page should fill the canvas: `width: '100%'; height: '100%'`.\n- Prefer inline `style={{ … }}`. Any CSS you load is global — scope classnames carefully.\n\n### Type scale (start here, adjust to taste)\n\n| Element          | Size       |\n| ---------------- | ---------- |\n| Hero title       | 140–200px  |\n| Section heading  | 80–120px   |\n| Page heading     | 56–80px    |\n| Body text        | 32–44px    |\n| Caption \u002F label  | 22–28px    |\n\n### Spacing\n\n- Content padding: **100–160px** from canvas edges. Never let text touch the edge.\n- Line-height: 1.2 for headings, 1.5–1.7 for body.\n- Breathing room between elements: 32–64px.\n\n### Vertical budget — content MUST fit 1080px\n\nThe canvas does **not** scroll. Anything past the 1080px bottom edge is silently cropped. Before writing JSX, do the math on paper and confirm the page fits. This is the #1 cause of broken slides — assume you will overflow unless you've checked.\n\n**Usable height** = `1080 − top_padding − bottom_padding`. With 120px padding on each side that's **840px**. With 160px each side, **760px**. Pick the padding first, then design within that budget.\n\n**Element height** = `font_size × line_height × number_of_lines`. A bullet that wraps to 2 lines counts as 2 lines. Add the gap below it (32–64px) before summing the next element.\n\n**Worked example — single content page, 120px padding (budget = 840px):**\n\n| Element                                  | Height                  |\n| ---------------------------------------- | ----------------------- |\n| Heading: 80px × 1.2 × 1 line             | 96px                    |\n| Gap                                      | 64px                    |\n| Body paragraph: 40px × 1.6 × 3 lines     | 192px                   |\n| Gap                                      | 48px                    |\n| 5 bullets: 40px × 1.6 × 1 line each      | 320px (5 × 64px)        |\n| 4 gaps between bullets: 24px each        | 96px                    |\n| **Total**                                | **816px ✅ fits in 840** |\n\nSwap the heading to 120px or add a 6th bullet and you're over. **Verify every page like this before you write it.**\n\n**Page-level rules:**\n\n- One heading + body OR one heading + ≤5 short bullets. Not both blocks of body copy *and* a long bullet list.\n- A bullet should fit on one line at the chosen font size. If it wraps, either shorten the copy or move it to its own page.\n- Hero title pages (140–200px) carry a title + 1 subtitle + maybe an eyebrow — nothing else.\n- Section headings (80–120px) need almost nothing else on the page.\n- If you find yourself raising padding, shrinking type below the scale's lower bound, or tightening body line-height under 1.4 to make things fit — **split into two pages instead**. Splitting is always the right answer when the budget is tight.\n\n**Never** use `overflow: auto\u002Fscroll`, negative margins, or transforms to hide overflow. The canvas is fixed; cropped content is gone.\n\n## Visual direction\n\nPick a coherent look and hold it across every page:\n\n- **Palette** — 1 background, 1 primary text, 1 accent, 1 muted. Put bg\u002Ftext\u002Faccent in the `design` const (see Design system below); extra colors like muted stay as plain consts.\n- **Typography** — one display font + one body font. System stack unless the user specifies. Heavy weight for headlines (800–900), normal for body (400–500).\n- **Layout grid** — pick a single content padding (e.g. 120px) and stick to it. Left-aligned content feels editorial; centered feels ceremonial.\n- **Aesthetic commitment** — choose ONE: minimal, maximalist, editorial, retro, brutalist, soft\u002Fpastel, neon, paper\u002Fprint. Don't mix.\n\nIf the `frontend-design` skill is available, consult it for deeper aesthetic guidance when the user wants something bold.\n\n## Webfonts\n\nThe default is a system font stack — prefer it. When a deck genuinely needs a webfont (a brand font, or CJK \u002F Thai \u002F Arabic where system coverage is poor), read `references\u002Fwebfonts.md` first — loading the stylesheet inside a page component registers the whole `@font-face` set once per mounted page, and CJK families need subsetting.\n\n## Themes\n\nIf `themes\u002F\u003Cid>.md` exists at the project root and the slide is meant to follow it, **the theme file overrides the defaults in this skill** — its palette, typography, layout padding, and Title\u002FFooter components are authoritative. Read the theme file before applying anything else in this section.\n\nThemes are produced by the `create-theme` skill and are pure documentation: copy the palette and the paste-ready Title \u002F Footer \u002F Eyebrow components straight into your slide. If the theme's frontmatter has `mode: dark` or `mode: light`, treat that as the slide's background mode (e.g. when picking which logo variant to import).\n\n## Design system (opt-in, per-slide)\n\nA slide can declare typed design tokens at the top of `index.tsx` — `export const design: DesignSystem = { palette, fonts, typeScale, radius }` — and consume them via `var(--osd-X)` in inline styles. The framework injects the CSS variables at the canvas root, and the dev UI's Design panel can live-tweak them.\n\n**Default to using it.** Every new slide should declare a `design` const so it stays tweakable from the panel after generation. Only fall back to plain palette constants for a one-off slide whose palette is intentionally locked (`references\u002Fdesign-system.md` covers the fallback).\n\n`references\u002Fdesign-system.md` has the full token shape, the two consumption surfaces (`var(--osd-X)` vs direct `design.X` reads), Design panel behavior, and the format constraints the panel's AST writer requires. Read it before writing the const.\n\n## Starter template\n\n```tsx\nimport type { DesignSystem, Page, SlideMeta } from '@open-slide\u002Fcore';\n\nexport const design: DesignSystem = {\n  palette: { bg: '#0f172a', text: '#f8fafc', accent: '#fbbf24' },\n  fonts: {\n    display: 'system-ui, -apple-system, sans-serif',\n    body: 'system-ui, -apple-system, sans-serif',\n  },\n  typeScale: { hero: 180, body: 40 },\n  radius: 12,\n};\n\n\u002F\u002F Extra colors \u002F sizes outside the DesignSystem shape stay as plain consts.\nconst muted = '#94a3b8';\n\nconst fill = {\n  width: '100%',\n  height: '100%',\n  fontFamily: 'var(--osd-font-body)',\n} as const;\n\nconst Cover: Page = () => (\n  \u003Cdiv\n    style={{\n      ...fill,\n      background: 'var(--osd-bg)',\n      color: 'var(--osd-text)',\n      display: 'flex',\n      flexDirection: 'column',\n      justifyContent: 'center',\n      padding: '0 160px',\n    }}\n  >\n    \u003Cdiv style={{ fontSize: 28, color: 'var(--osd-accent)', letterSpacing: '0.2em' }}>\n      CHAPTER 01\n    \u003C\u002Fdiv>\n    \u003Ch1\n      style={{\n        fontFamily: 'var(--osd-font-display)',\n        fontSize: 'var(--osd-size-hero)',\n        fontWeight: 900,\n        margin: '32px 0',\n        lineHeight: 1.05,\n      }}\n    >\n      The Big Idea\n    \u003C\u002Fh1>\n    \u003Cp style={{ fontSize: 'var(--osd-size-body)', color: muted, maxWidth: 1200 }}>\n      A short subtitle that explains what this slide is about.\n    \u003C\u002Fp>\n  \u003C\u002Fdiv>\n);\n\nconst Content: Page = () => (\n  \u003Cdiv style={{ ...fill, background: 'var(--osd-bg)', color: 'var(--osd-text)', padding: 120 }}>\n    \u003Ch2 style={{ fontFamily: 'var(--osd-font-display)', fontSize: 80, fontWeight: 800, margin: 0 }}>\n      Section heading\n    \u003C\u002Fh2>\n    \u003Cul style={{ fontSize: 'var(--osd-size-body)', lineHeight: 1.6, marginTop: 64, paddingLeft: 48 }}>\n      \u003Cli>One clear point per line\u003C\u002Fli>\n      \u003Cli>Keep to 3–5 bullets\u003C\u002Fli>\n      \u003Cli>Let the space breathe\u003C\u002Fli>\n    \u003C\u002Ful>\n  \u003C\u002Fdiv>\n);\n\nexport const meta: SlideMeta = {\n  title: 'The Big Idea',\n  createdAt: '2026-05-16T12:00:00Z',\n};\nexport default [Cover, Content] satisfies Page[];\n```\n\n## Assets\n\nSlide-local assets live under `slides\u002F\u003Cid>\u002Fassets\u002F` and are imported as ES modules (`import hero from '.\u002Fassets\u002Fhero.jpg'`). Global assets shared across decks (logos, avatars, recurring icons) live in the project root `assets\u002F` and are imported via the `@assets` alias. For a pure-text slide, don't create `slides\u002F\u003Cid>\u002Fassets\u002F` at all.\n\n`references\u002Fassets.md` covers import forms (module vs `new URL(...)`), the `@assets` alias, and how themes name asset paths.\n\n## Image placeholders\n\nWhen a page genuinely needs a real image **the user has to provide** (product screenshot, team photo, chart from their data), leave a typed `\u003CImagePlaceholder hint=\"…\" \u002F>` from `@open-slide\u002Fcore` instead of inventing a stand-in — the user replaces it via the Assets panel + inspector. **Do not** use placeholders for decoration or generic stock-photo filler; if type, layout, and color can carry the page, do that.\n\n`references\u002Fassets.md` has the full usage rules, sizing guidance, and examples of when a placeholder is (and isn't) warranted.\n\n## Page numbers\n\nIf a footer shows the current page (`03 \u002F 12`), read it from `useSlidePageNumber()` — **never hardcode** `n` \u002F `TOTAL`. See `references\u002Fpage-numbers.md` for the hook's contract and where it can be called.\n\n## Stepped reveals (`\u003CSteps>` \u002F `\u003CStep>`)\n\nReveal a page one beat at a time: wrap deferred parts in `\u003CStep>`, the group in `\u003CSteps>`; each `→` reveals the next step. Use it when the *order* of ideas is the point — not reflexively on every page. Two rules are load-bearing: `\u003CStep>` must be a **direct child** of `\u003CSteps>` (otherwise it silently renders fully revealed), and a page must still read as complete when jumped to via the overview grid (jumping in shows all steps revealed).\n\nRead `references\u002Fsteps.md` before authoring a stepped page — it covers composition order across multiple `\u003CSteps>` blocks, the \"headline always, body in turn\" pattern, and entry-direction behavior. If `slides\u002Fbuild-on-reveal\u002F` exists in this project, it is the canonical worked example.\n\n## Page transitions\n\nThe framework can run an enter\u002Fexit animation between slide changes, declared as a `SlideTransition` (module-level default, per-page override; the **incoming page wins**). There's **no default** — pages snap unless you opt in, and snap-swap is a perfectly tasteful default. If you do opt in: one motion DNA per deck, 200–280 ms, magnitude under 12 px \u002F 3% scale, the outgoing page holds while the incoming page fades in on top (the framework ignores exit opacity unless `throughBackground: true`).\n\nRead `references\u002Ftransitions.md` before declaring one — it has the full type contract, design principles, a six-member \"tasteful family\" of ready-to-use transitions sharing one DNA, direction-aware keyframes, and the anti-pattern list.\n\n## Morph transitions\n\nWhen the *same visual object* exists on two adjacent pages, wrap it on both pages in `MorphElement` with the same `id` and enable `morph` on the incoming page's transition — position, size, radius, and colors interpolate in one continuous move (Keynote's \"Magic Move\"). Morph is for **state continuity** (a toggle sliding, a card expanding, a box joining a row); don't morph decoration.\n\nRead `references\u002Fmorph.md` before writing one — the seven rules there (held exit + opacity-only enter, deterministic geometry, no `transform` on the morph node, `useIsActivePage()` gating, …) were each earned on a real deck, and violating any of them produces a visibly broken morph.\n\n## Repeated elements: component, not `map`\n\nWhen a page has visually repeated items — cards, logo rows, gallery tiles, list rows, step indicators — **define a small component and instantiate it once per item**. Do **not** render the group with `array.map` over a data array.\n\nDefine the component **in the same `index.tsx`**, alongside the `Page` components. Never split it into a sibling file like `Card.tsx` — a slide is always a single `index.tsx` plus its `assets\u002F`.\n\n```tsx\n\u002F\u002F ✅ Each card is its own JSX node — inspector edits one at a time.\nconst Card = ({ src, label }: { src: string; label: string }) => (\n  \u003Cdiv style={{ display: 'flex', flexDirection: 'column', gap: 16 }}>\n    \u003Cimg src={src} style={{ width: 320, height: 320, objectFit: 'cover', borderRadius: 12 }} \u002F>\n    \u003Cp style={{ fontSize: 32 }}>{label}\u003C\u002Fp>\n  \u003C\u002Fdiv>\n);\n\n\u003Cdiv style={{ display: 'grid', gridTemplateColumns: 'repeat(3, 1fr)', gap: 64 }}>\n  \u003CCard src={alpha} label=\"Alpha\" \u002F>\n  \u003CCard src={beta}  label=\"Beta\"  \u002F>\n  \u003CCard src={gamma} label=\"Gamma\" \u002F>\n\u003C\u002Fdiv>\n```\n\n```tsx\n\u002F\u002F ❌ One shared template — replacing the image or text in the inspector\n\u002F\u002F    changes every rendered card at once.\nconst items = [\n  { src: alpha, label: 'Alpha' },\n  { src: beta,  label: 'Beta'  },\n  { src: gamma, label: 'Gamma' },\n];\nitems.map((item) => (\n  \u003Cdiv>\n    \u003Cimg src={item.src} \u002F>\n    \u003Cp>{item.label}\u003C\u002Fp>\n  \u003C\u002Fdiv>\n));\n```\n\nThe inspector edits source JSX in place. A `map` body is **one source location** shared by every rendered instance, so when the user replaces an image or tweaks a label there, every card mutates together. Explicit instances give each card its own JSX node and its own props — the unit the inspector can target.\n\nThe component definition stays the single source of truth for layout\u002Fstyling (change it once → all cards update). Only the per-instance data — `src`, `label`, accent color — lives at the call site.\n\nThis applies whenever the *visual element* repeats, not whenever the *data* does. Pure-text lists (`\u003Cul>\u003Cli>` bullets) are fine: each `\u003Cli>` is already its own JSX node, so plain literal markup is the correct shape — no need to wrap them in a component.\n\n## Runtime behavior you get for free\n\n- Home page lists every folder under `slides\u002F`.\n- Clicking a slide shows a left thumbnail rail, main page, prev\u002Fnext, page counter.\n- Arrow keys \u002F PageUp \u002F PageDown navigate. `F` enters fullscreen play mode.\n- In play mode: Space\u002F→ next, ← prev, Esc exit.\n- Hot reload: edit `index.tsx` and the browser updates live.\n\n## Self-review before finishing\n\n- [ ] `slides\u002F\u003Cid>\u002Findex.tsx` `export default`s a non-empty `Page[]`.\n- [ ] Every page's root fills `100% × 100%`.\n- [ ] Content lives inside padding (no text kisses the edge).\n- [ ] **For every page, sum (font_size × line_height × lines) + gaps + 2×padding ≤ 1080px.** If close, split the page. No `overflow: auto` escape hatches.\n- [ ] No bullet wraps to a second line at the chosen font size.\n- [ ] One coherent visual direction across every page (palette + type scale).\n- [ ] Slide declares a top-level `export const design: DesignSystem = { … }` and references the values via `var(--osd-X)` (use `design.X` only when you need a JS number for arithmetic). Only omit the `design` const for a one-off slide whose palette is intentionally locked.\n- [ ] One idea per page.\n- [ ] Visually repeated elements (cards, tiles, logo rows) are rendered as explicit `\u003CComponent \u002F>` instances, not via `array.map` over a data list.\n- [ ] All imported assets exist on disk — slide-local under `slides\u002F\u003Cid>\u002Fassets\u002F`, or global under `assets\u002F` (imported via `@assets\u002F...`).\n- [ ] Every `\u003CImagePlaceholder>` corresponds to a real image the user must supply — not decorative filler. If it could be replaced by typography or layout, it should be.\n- [ ] If a page uses `\u003CSteps>`\u002F`\u003CStep>`, every `\u003CStep>` is a direct child of a `\u003CSteps>`, and the page still reads as complete when jumped to via the overview grid (entering forward builds up; jumping in shows it fully revealed).\n- [ ] If a `SlideTransition` is declared, every page sits in one family — same duration band (200–280 ms), same easing pair, same hold-then-fade-in shape (no enter delay, no `throughBackground` outside a deliberate section break), magnitude under 12 px \u002F 3%. No six-different-vocabularies decks. When in doubt, omit transitions entirely. (Pages that opt into `morph` may exceed the band to match the morph — see `references\u002Fmorph.md`.)\n- [ ] If a transition opts into `morph`: every morph `id` is unique per page and stable across the pair, morph geometry is pixel-constant (never measured after mount), no `transform` sits on the morph node, and entrance animations are gated behind `useIsActivePage()`.\n- [ ] If the user asked for a speech script \u002F speaker notes, it lives in `export const notes` (index-aligned with the page array) — not in a markdown or text file.\n- [ ] Nothing outside `slides\u002F\u003Cid>\u002F` was edited.\n\n## Anti-patterns\n\n- ❌ Walls of text. If a page has more than ~40 words, split it.\n- ❌ Using the full canvas for body copy. Respect 100–160px padding.\n- ❌ Overflowing 1080px vertically. Cropped content is invisible — split the page.\n- ❌ `overflow: auto` \u002F `overflow: scroll` \u002F `overflow: hidden` to \"hide\" too much content. The canvas doesn't scroll; you've just hidden the bug.\n- ❌ Shrinking type below the scale's lower bound, or padding below 100px, to cram more in. Split instead.\n- ❌ Bullets that wrap to a second line — either shorten or move to its own page.\n- ❌ Body type under 28px — unreadable on a projector.\n- ❌ Inconsistent palette across pages.\n- ❌ Installing packages. Only `react`, `@open-slide\u002Fcore`, and standard web APIs are available.\n- ❌ Writing CSS to a shared file. Inline styles or scoped classnames only.\n- ❌ Creating `README.md` or other prose files inside the slide folder.\n- ❌ Delivering a speech script as a markdown or text file. The runtime only surfaces the `notes` export — anything else never reaches the presenter view.\n- ❌ Editing `package.json`, `open-slide.config.ts`, or other slides.\n- ❌ Using a primitive without reading its reference file — each `references\u002F*.md` carries the primitive's own anti-pattern list (placeholder misuse, transition vocabulary, `\u003CStep>` nesting, morph geometry).\n","# Authoring open-slide pages\n\nThis skill is the **technical reference** for everything that happens inside `slides\u002F\u003Cid>\u002Findex.tsx`. It does not own a workflow:\n\n- `create-slide` owns \"draft a new deck\" — it asks the user scoping questions, then delegates the *how* to this skill.\n- `apply-comments` owns \"process inspector markers\" — it finds markers and applies edits, but the edits themselves follow the rules here.\n- `current-slide` resolves deictic references (\"this page\", \"the slide I'm on\") to a concrete `slideId` + `pageIndex`. Consult it **first** when the user references the current slide without naming it, then come back here for how to edit it.\n- Any ad-hoc slide edit (manual tweak, one-off fix) should also consult this skill before touching the file.\n\nWhen any of those paths reach the point of *writing React code for a page*, this is the source of truth. Do not duplicate the knowledge below into other skills — link here instead.\n\n## Primitive references\n\nEach framework primitive has a full reference file under `references\u002F` in this skill — contract, worked examples, and its own anti-patterns. This file keeps only the always-on rules and a short summary per primitive. **Read the relevant reference file before using a primitive on a page**:\n\n| Primitive | Read before | File |\n| --- | --- | --- |\n| `design` const + `var(--osd-X)` tokens | writing any new slide (default baseline) | `references\u002Fdesign-system.md` |\n| Assets + `\u003CImagePlaceholder>` | importing images\u002Fvideos or leaving a placeholder | `references\u002Fassets.md` |\n| Webfonts | loading any non-system font | `references\u002Fwebfonts.md` |\n| `useSlidePageNumber()` | rendering a page-number footer | `references\u002Fpage-numbers.md` |\n| `\u003CSteps>` \u002F `\u003CStep>` | staging a page's reveal | `references\u002Fsteps.md` |\n| `SlideTransition` | declaring any enter\u002Fexit animation | `references\u002Ftransitions.md` |\n| `MorphElement` + `morph` | morphing a shared element across pages | `references\u002Fmorph.md` |\n\n## Hard rules\n\n- Put the slide under `slides\u002F\u003Ckebab-case-id>\u002F`.\n- Entry is `slides\u002F\u003Cid>\u002Findex.tsx`. Images\u002Fvideos\u002Ffonts go under `slides\u002F\u003Cid>\u002Fassets\u002F`.\n- Do **not** touch `package.json`, `open-slide.config.ts`, or other slides.\n- Do not add dependencies. Only `react`, `@open-slide\u002Fcore`, and standard web APIs are available.\n- A slide is **one `index.tsx` plus `assets\u002F`** — nothing else. Do not create sibling `.tsx`\u002F`.ts` files (`Card.tsx`, `components\u002F`, `helpers.ts`, etc.); helper components and constants go inside `index.tsx`. Do not create `README.md` or other prose files either — speaker notes \u002F a talk script belong in the `notes` export (see **Speaker notes** below), not in a markdown file.\n\n## File contract\n\n```tsx\n\u002F\u002F slides\u002F\u003Cid>\u002Findex.tsx\nimport type { Page, SlideMeta } from '@open-slide\u002Fcore';\n\nconst Cover: Page = () => \u003Cdiv>…\u003C\u002Fdiv>;\nconst Body: Page = () => \u003Cdiv>…\u003C\u002Fdiv>;\n\nexport const meta: SlideMeta = {\n  title: 'My slide',\n  createdAt: '2026-05-16T12:00:00Z',\n};\nexport default [Cover, Body] satisfies Page[];\n```\n\n- `export default` is a **non-empty array of zero-prop React components**, one per page, in order.\n- `meta.title` (optional) shows in the slide header. Default is the folder name.\n- The slide id is the kebab-case folder name. Pick something short and descriptive (`q2-roadmap`, `team-offsite-2026`).\n- `meta.theme` (optional) marks the slide as built from a theme under `themes\u002F`. The id must match a `\u003Cid>.md` basename. Surfaces a back-link chip on the slide card and lists the slide on `\u002Fthemes\u002F\u003Cid>`. Omit if the slide isn't derived from a registered theme.\n- `meta.createdAt` is an **ISO 8601 string literal** (e.g. `'2026-05-16T12:00:00Z'`) set once when the slide is scaffolded. The home page uses it for the default \"newest first\" sort. Always include it on new slides — **immediately before writing the file, run `node -e \"console.log(new Date().toISOString())\"` via Bash and paste the exact output** as the value. Don't type a timestamp from memory — you will get the date or time wrong. Must be a plain string literal (no `new Date(...)` or imports in the slide itself) — the framework reads it via a regex at build time, not by evaluating the module.\n\n## Speaker notes (`notes` export)\n\nThe framework has **built-in speaker notes**: an optional `notes` export in `index.tsx`, index-aligned with the default page array. The viewer shows them in the notes drawer and present mode shows them in the presenter view next to the timer.\n\n**When the user asks for a speech script, talk track, or presenter notes — in any language — write it into this export, never into a markdown\u002Ftext file.** A `script.md` or `notes.md` is invisible to the runtime; the `notes` export is the only place the presenter view reads.\n\n```tsx\nexport const notes: (string | undefined)[] = [\n  'Open with the analyst quote, then introduce yourself.',\n  undefined,\n  `Walk through the three pillars, one beat each.\nPause for questions before moving on.`,\n];\n```\n\n- One entry per page, same order as the `export default` array. `notes[0]` belongs to the first page.\n- Entries are **plain text** — line breaks are preserved, markdown is not rendered. Use a template literal for multi-line notes, a normal string for one-liners.\n- Use `undefined` for a page with no notes; trailing `undefined` entries can be dropped.\n- When you add, remove, or reorder pages, re-align `notes` in the same edit — a shifted index silently attaches the wrong script to every page after it.\n- Write notes as something to *say*, not a summary of what's on screen: openers, transitions, numbers to cite, timing cues.\n\n## Editing an existing slide\n\nA finished slide commonly runs 1000–1800 lines. When you only need to touch one page, **don't read the whole file** — locate the page first, then read just that range:\n\n```bash\ngrep -n \": Page = \" slides\u002F\u003Cid>\u002Findex.tsx\n```\n\nThis lists every `const Foo: Page = …` declaration with its line number. Read the target page with `Read` using `offset` + `limit` (~150 lines is usually enough to capture one page plus its helper components). Read the whole file only when you need cross-page context (palette audit, reordering, design const tweaks).\n\n## Canvas\n\nEvery page renders into a fixed **1920 × 1080** canvas. The framework scales it; you design as if the viewport is literally 1920×1080.\n\n- Use **absolute pixel values** for `font-size`, padding, positioning. No `rem`, no `vw`\u002F`vh`, no `%` for type.\n- The root element of each page should fill the canvas: `width: '100%'; height: '100%'`.\n- Prefer inline `style={{ … }}`. Any CSS you load is global — scope classnames carefully.\n\n### Type scale (start here, adjust to taste)\n\n| Element          | Size       |\n| ---------------- | ---------- |\n| Hero title       | 140–200px  |\n| Section heading  | 80–120px   |\n| Page heading     | 56–80px    |\n| Body text        | 32–44px    |\n| Caption \u002F label  | 22–28px    |\n\n### Spacing\n\n- Content padding: **100–160px** from canvas edges. Never let text touch the edge.\n- Line-height: 1.2 for headings, 1.5–1.7 for body.\n- Breathing room between elements: 32–64px.\n\n### Vertical budget — content MUST fit 1080px\n\nThe canvas does **not** scroll. Anything past the 1080px bottom edge is silently cropped. Before writing JSX, do the math on paper and confirm the page fits. This is the #1 cause of broken slides — assume you will overflow unless you've checked.\n\n**Usable height** = `1080 − top_padding − bottom_padding`. With 120px padding on each side that's **840px**. With 160px each side, **760px**. Pick the padding first, then design within that budget.\n\n**Element height** = `font_size × line_height × number_of_lines`. A bullet that wraps to 2 lines counts as 2 lines. Add the gap below it (32–64px) before summing the next element.\n\n**Worked example — single content page, 120px padding (budget = 840px):**\n\n| Element                                  | Height                  |\n| ---------------------------------------- | ----------------------- |\n| Heading: 80px × 1.2 × 1 line             | 96px                    |\n| Gap                                      | 64px                    |\n| Body paragraph: 40px × 1.6 × 3 lines     | 192px                   |\n| Gap                                      | 48px                    |\n| 5 bullets: 40px × 1.6 × 1 line each      | 320px (5 × 64px)        |\n| 4 gaps between bullets: 24px each        | 96px                    |\n| **Total**                                | **816px ✅ fits in 840** |\n\nSwap the heading to 120px or add a 6th bullet and you're over. **Verify every page like this before you write it.**\n\n**Page-level rules:**\n\n- One heading + body OR one heading + ≤5 short bullets. Not both blocks of body copy *and* a long bullet list.\n- A bullet should fit on one line at the chosen font size. If it wraps, either shorten the copy or move it to its own page.\n- Hero title pages (140–200px) carry a title + 1 subtitle + maybe an eyebrow — nothing else.\n- Section headings (80–120px) need almost nothing else on the page.\n- If you find yourself raising padding, shrinking type below the scale's lower bound, or tightening body line-height under 1.4 to make things fit — **split into two pages instead**. Splitting is always the right answer when the budget is tight.\n\n**Never** use `overflow: auto\u002Fscroll`, negative margins, or transforms to hide overflow. The canvas is fixed; cropped content is gone.\n\n## Visual direction\n\nPick a coherent look and hold it across every page:\n\n- **Palette** — 1 background, 1 primary text, 1 accent, 1 muted. Put bg\u002Ftext\u002Faccent in the `design` const (see Design system below); extra colors like muted stay as plain consts.\n- **Typography** — one display font + one body font. System stack unless the user specifies. Heavy weight for headlines (800–900), normal for body (400–500).\n- **Layout grid** — pick a single content padding (e.g. 120px) and stick to it. Left-aligned content feels editorial; centered feels ceremonial.\n- **Aesthetic commitment** — choose ONE: minimal, maximalist, editorial, retro, brutalist, soft\u002Fpastel, neon, paper\u002Fprint. Don't mix.\n\nIf the `frontend-design` skill is available, consult it for deeper aesthetic guidance when the user wants something bold.\n\n## Webfonts\n\nThe default is a system font stack — prefer it. When a deck genuinely needs a webfont (a brand font, or CJK \u002F Thai \u002F Arabic where system coverage is poor), read `references\u002Fwebfonts.md` first — loading the stylesheet inside a page component registers the whole `@font-face` set once per mounted page, and CJK families need subsetting.\n\n## Themes\n\nIf `themes\u002F\u003Cid>.md` exists at the project root and the slide is meant to follow it, **the theme file overrides the defaults in this skill** — its palette, typography, layout padding, and Title\u002FFooter components are authoritative. Read the theme file before applying anything else in this section.\n\nThemes are produced by the `create-theme` skill and are pure documentation: copy the palette and the paste-ready Title \u002F Footer \u002F Eyebrow components straight into your slide. If the theme's frontmatter has `mode: dark` or `mode: light`, treat that as the slide's background mode (e.g. when picking which logo variant to import).\n\n## Design system (opt-in, per-slide)\n\nA slide can declare typed design tokens at the top of `index.tsx` — `export const design: DesignSystem = { palette, fonts, typeScale, radius }` — and consume them via `var(--osd-X)` in inline styles. The framework injects the CSS variables at the canvas root, and the dev UI's Design panel can live-tweak them.\n\n**Default to using it.** Every new slide should declare a `design` const so it stays tweakable from the panel after generation. Only fall back to plain palette constants for a one-off slide whose palette is intentionally locked (`references\u002Fdesign-system.md` covers the fallback).\n\n`references\u002Fdesign-system.md` has the full token shape, the two consumption surfaces (`var(--osd-X)` vs direct `design.X` reads), Design panel behavior, and the format constraints the panel's AST writer requires. Read it before writing the const.\n\n## Starter template\n\n```tsx\nimport type { DesignSystem, Page, SlideMeta } from '@open-slide\u002Fcore';\n\nexport const design: DesignSystem = {\n  palette: { bg: '#0f172a', text: '#f8fafc', accent: '#fbbf24' },\n  fonts: {\n    display: 'system-ui, -apple-system, sans-serif',\n    body: 'system-ui, -apple-system, sans-serif',\n  },\n  typeScale: { hero: 180, body: 40 },\n  radius: 12,\n};\n\n\u002F\u002F Extra colors \u002F sizes outside the DesignSystem shape stay as plain consts.\nconst muted = '#94a3b8';\n\nconst fill = {\n  width: '100%',\n  height: '100%',\n  fontFamily: 'var(--osd-font-body)',\n} as const;\n\nconst Cover: Page = () => (\n  \u003Cdiv\n    style={{\n      ...fill,\n      background: 'var(--osd-bg)',\n      color: 'var(--osd-text)',\n      display: 'flex',\n      flexDirection: 'column',\n      justifyContent: 'center',\n      padding: '0 160px',\n    }}\n  >\n    \u003Cdiv style={{ fontSize: 28, color: 'var(--osd-accent)', letterSpacing: '0.2em' }}>\n      CHAPTER 01\n    \u003C\u002Fdiv>\n    \u003Ch1\n      style={{\n        fontFamily: 'var(--osd-font-display)',\n        fontSize: 'var(--osd-size-hero)',\n        fontWeight: 900,\n        margin: '32px 0',\n        lineHeight: 1.05,\n      }}\n    >\n      The Big Idea\n    \u003C\u002Fh1>\n    \u003Cp style={{ fontSize: 'var(--osd-size-body)', color: muted, maxWidth: 1200 }}>\n      A short subtitle that explains what this slide is about.\n    \u003C\u002Fp>\n  \u003C\u002Fdiv>\n);\n\nconst Content: Page = () => (\n  \u003Cdiv style={{ ...fill, background: 'var(--osd-bg)', color: 'var(--osd-text)', padding: 120 }}>\n    \u003Ch2 style={{ fontFamily: 'var(--osd-font-display)', fontSize: 80, fontWeight: 800, margin: 0 }}>\n      Section heading\n    \u003C\u002Fh2>\n    \u003Cul style={{ fontSize: 'var(--osd-size-body)', lineHeight: 1.6, marginTop: 64, paddingLeft: 48 }}>\n      \u003Cli>One clear point per line\u003C\u002Fli>\n      \u003Cli>Keep to 3–5 bullets\u003C\u002Fli>\n      \u003Cli>Let the space breathe\u003C\u002Fli>\n    \u003C\u002Ful>\n  \u003C\u002Fdiv>\n);\n\nexport const meta: SlideMeta = {\n  title: 'The Big Idea',\n  createdAt: '2026-05-16T12:00:00Z',\n};\nexport default [Cover, Content] satisfies Page[];\n```\n\n## Assets\n\nSlide-local assets live under `slides\u002F\u003Cid>\u002Fassets\u002F` and are imported as ES modules (`import hero from '.\u002Fassets\u002Fhero.jpg'`). Global assets shared across decks (logos, avatars, recurring icons) live in the project root `assets\u002F` and are imported via the `@assets` alias. For a pure-text slide, don't create `slides\u002F\u003Cid>\u002Fassets\u002F` at all.\n\n`references\u002Fassets.md` covers import forms (module vs `new URL(...)`), the `@assets` alias, and how themes name asset paths.\n\n## Image placeholders\n\nWhen a page genuinely needs a real image **the user has to provide** (product screenshot, team photo, chart from their data), leave a typed `\u003CImagePlaceholder hint=\"…\" \u002F>` from `@open-slide\u002Fcore` instead of inventing a stand-in — the user replaces it via the Assets panel + inspector. **Do not** use placeholders for decoration or generic stock-photo filler; if type, layout, and color can carry the page, do that.\n\n`references\u002Fassets.md` has the full usage rules, sizing guidance, and examples of when a placeholder is (and isn't) warranted.\n\n## Page numbers\n\nIf a footer shows the current page (`03 \u002F 12`), read it from `useSlidePageNumber()` — **never hardcode** `n` \u002F `TOTAL`. See `references\u002Fpage-numbers.md` for the hook's contract and where it can be called.\n\n## Stepped reveals (`\u003CSteps>` \u002F `\u003CStep>`)\n\nReveal a page one beat at a time: wrap deferred parts in `\u003CStep>`, the group in `\u003CSteps>`; each `→` reveals the next step. Use it when the *order* of ideas is the point — not reflexively on every page. Two rules are load-bearing: `\u003CStep>` must be a **direct child** of `\u003CSteps>` (otherwise it silently renders fully revealed), and a page must still read as complete when jumped to via the overview grid (jumping in shows all steps revealed).\n\nRead `references\u002Fsteps.md` before authoring a stepped page — it covers composition order across multiple `\u003CSteps>` blocks, the \"headline always, body in turn\" pattern, and entry-direction behavior. If `slides\u002Fbuild-on-reveal\u002F` exists in this project, it is the canonical worked example.\n\n## Page transitions\n\nThe framework can run an enter\u002Fexit animation between slide changes, declared as a `SlideTransition` (module-level default, per-page override; the **incoming page wins**). There's **no default** — pages snap unless you opt in, and snap-swap is a perfectly tasteful default. If you do opt in: one motion DNA per deck, 200–280 ms, magnitude under 12 px \u002F 3% scale, the outgoing page holds while the incoming page fades in on top (the framework ignores exit opacity unless `throughBackground: true`).\n\nRead `references\u002Ftransitions.md` before declaring one — it has the full type contract, design principles, a six-member \"tasteful family\" of ready-to-use transitions sharing one DNA, direction-aware keyframes, and the anti-pattern list.\n\n## Morph transitions\n\nWhen the *same visual object* exists on two adjacent pages, wrap it on both pages in `MorphElement` with the same `id` and enable `morph` on the incoming page's transition — position, size, radius, and colors interpolate in one continuous move (Keynote's \"Magic Move\"). Morph is for **state continuity** (a toggle sliding, a card expanding, a box joining a row); don't morph decoration.\n\nRead `references\u002Fmorph.md` before writing one — the seven rules there (held exit + opacity-only enter, deterministic geometry, no `transform` on the morph node, `useIsActivePage()` gating, …) were each earned on a real deck, and violating any of them produces a visibly broken morph.\n\n## Repeated elements: component, not `map`\n\nWhen a page has visually repeated items — cards, logo rows, gallery tiles, list rows, step indicators — **define a small component and instantiate it once per item**. Do **not** render the group with `array.map` over a data array.\n\nDefine the component **in the same `index.tsx`**, alongside the `Page` components. Never split it into a sibling file like `Card.tsx` — a slide is always a single `index.tsx` plus its `assets\u002F`.\n\n```tsx\n\u002F\u002F ✅ Each card is its own JSX node — inspector edits one at a time.\nconst Card = ({ src, label }: { src: string; label: string }) => (\n  \u003Cdiv style={{ display: 'flex', flexDirection: 'column', gap: 16 }}>\n    \u003Cimg src={src} style={{ width: 320, height: 320, objectFit: 'cover', borderRadius: 12 }} \u002F>\n    \u003Cp style={{ fontSize: 32 }}>{label}\u003C\u002Fp>\n  \u003C\u002Fdiv>\n);\n\n\u003Cdiv style={{ display: 'grid', gridTemplateColumns: 'repeat(3, 1fr)', gap: 64 }}>\n  \u003CCard src={alpha} label=\"Alpha\" \u002F>\n  \u003CCard src={beta}  label=\"Beta\"  \u002F>\n  \u003CCard src={gamma} label=\"Gamma\" \u002F>\n\u003C\u002Fdiv>\n```\n\n```tsx\n\u002F\u002F ❌ One shared template — replacing the image or text in the inspector\n\u002F\u002F    changes every rendered card at once.\nconst items = [\n  { src: alpha, label: 'Alpha' },\n  { src: beta,  label: 'Beta'  },\n  { src: gamma, label: 'Gamma' },\n];\nitems.map((item) => (\n  \u003Cdiv>\n    \u003Cimg src={item.src} \u002F>\n    \u003Cp>{item.label}\u003C\u002Fp>\n  \u003C\u002Fdiv>\n));\n```\n\nThe inspector edits source JSX in place. A `map` body is **one source location** shared by every rendered instance, so when the user replaces an image or tweaks a label there, every card mutates together. Explicit instances give each card its own JSX node and its own props — the unit the inspector can target.\n\nThe component definition stays the single source of truth for layout\u002Fstyling (change it once → all cards update). Only the per-instance data — `src`, `label`, accent color — lives at the call site.\n\nThis applies whenever the *visual element* repeats, not whenever the *data* does. Pure-text lists (`\u003Cul>\u003Cli>` bullets) are fine: each `\u003Cli>` is already its own JSX node, so plain literal markup is the correct shape — no need to wrap them in a component.\n\n## Runtime behavior you get for free\n\n- Home page lists every folder under `slides\u002F`.\n- Clicking a slide shows a left thumbnail rail, main page, prev\u002Fnext, page counter.\n- Arrow keys \u002F PageUp \u002F PageDown navigate. `F` enters fullscreen play mode.\n- In play mode: Space\u002F→ next, ← prev, Esc exit.\n- Hot reload: edit `index.tsx` and the browser updates live.\n\n## Self-review before finishing\n\n- [ ] `slides\u002F\u003Cid>\u002Findex.tsx` `export default`s a non-empty `Page[]`.\n- [ ] Every page's root fills `100% × 100%`.\n- [ ] Content lives inside padding (no text kisses the edge).\n- [ ] **For every page, sum (font_size × line_height × lines) + gaps + 2×padding ≤ 1080px.** If close, split the page. No `overflow: auto` escape hatches.\n- [ ] No bullet wraps to a second line at the chosen font size.\n- [ ] One coherent visual direction across every page (palette + type scale).\n- [ ] Slide declares a top-level `export const design: DesignSystem = { … }` and references the values via `var(--osd-X)` (use `design.X` only when you need a JS number for arithmetic). Only omit the `design` const for a one-off slide whose palette is intentionally locked.\n- [ ] One idea per page.\n- [ ] Visually repeated elements (cards, tiles, logo rows) are rendered as explicit `\u003CComponent \u002F>` instances, not via `array.map` over a data list.\n- [ ] All imported assets exist on disk — slide-local under `slides\u002F\u003Cid>\u002Fassets\u002F`, or global under `assets\u002F` (imported via `@assets\u002F...`).\n- [ ] Every `\u003CImagePlaceholder>` corresponds to a real image the user must supply — not decorative filler. If it could be replaced by typography or layout, it should be.\n- [ ] If a page uses `\u003CSteps>`\u002F`\u003CStep>`, every `\u003CStep>` is a direct child of a `\u003CSteps>`, and the page still reads as complete when jumped to via the overview grid (entering forward builds up; jumping in shows it fully revealed).\n- [ ] If a `SlideTransition` is declared, every page sits in one family — same duration band (200–280 ms), same easing pair, same hold-then-fade-in shape (no enter delay, no `throughBackground` outside a deliberate section break), magnitude under 12 px \u002F 3%. No six-different-vocabularies decks. When in doubt, omit transitions entirely. (Pages that opt into `morph` may exceed the band to match the morph — see `references\u002Fmorph.md`.)\n- [ ] If a transition opts into `morph`: every morph `id` is unique per page and stable across the pair, morph geometry is pixel-constant (never measured after mount), no `transform` sits on the morph node, and entrance animations are gated behind `useIsActivePage()`.\n- [ ] If the user asked for a speech script \u002F speaker notes, it lives in `export const notes` (index-aligned with the page array) — not in a markdown or text file.\n- [ ] Nothing outside `slides\u002F\u003Cid>\u002F` was edited.\n\n## Anti-patterns\n\n- ❌ Walls of text. If a page has more than ~40 words, split it.\n- ❌ Using the full canvas for body copy. Respect 100–160px padding.\n- ❌ Overflowing 1080px vertically. Cropped content is invisible — split the page.\n- ❌ `overflow: auto` \u002F `overflow: scroll` \u002F `overflow: hidden` to \"hide\" too much content. The canvas doesn't scroll; you've just hidden the bug.\n- ❌ Shrinking type below the scale's lower bound, or padding below 100px, to cram more in. Split instead.\n- ❌ Bullets that wrap to a second line — either shorten or move to its own page.\n- ❌ Body type under 28px — unreadable on a projector.\n- ❌ Inconsistent palette across pages.\n- ❌ Installing packages. Only `react`, `@open-slide\u002Fcore`, and standard web APIs are available.\n- ❌ Writing CSS to a shared file. Inline styles or scoped classnames only.\n- ❌ Creating `README.md` or other prose files inside the slide folder.\n- ❌ Delivering a speech script as a markdown or text file. The runtime only surfaces the `notes` export — anything else never reaches the presenter view.\n- ❌ Editing `package.json`, `open-slide.config.ts`, or other slides.\n- ❌ Using a primitive without reading its reference file — each `references\u002F*.md` carries the primitive's own anti-pattern list (placeholder misuse, transition vocabulary, `\u003CStep>` nesting, morph geometry).\n",{"name":5,"description":7},"main","d922e716d0801fbdf6c27f023b245c8da7e4c804","apps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring",63,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot","https:\u002F\u002Ftobs.app","https:\u002F\u002Fgithub.com\u002FBotHarness","https:\u002F\u002Fdeepseekbot.app\u002F","2026-11-15 06:17:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add BotHarness\u002FDeepSeekBot --skill slide-authoring",{"tool":38,"command":39},"bunx","bunx skills add BotHarness\u002FDeepSeekBot --skill slide-authoring",{"tool":41,"command":42},"pnpm","pnpm dlx skills add BotHarness\u002FDeepSeekBot --skill slide-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring\u002FSKILL.md",true,[46,52,56,60,64,68,72],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fassets.md","REFERENCE","参考文档",2671,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring\u002Freferences\u002Fassets.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fdesign-system.md",3128,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring\u002Freferences\u002Fdesign-system.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fmorph.md",6788,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring\u002Freferences\u002Fmorph.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fpage-numbers.md",891,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring\u002Freferences\u002Fpage-numbers.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fsteps.md",3467,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring\u002Freferences\u002Fsteps.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Ftransitions.md",9453,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring\u002Freferences\u002Ftransitions.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fwebfonts.md",2583,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring\u002Freferences\u002Fwebfonts.md",[77,84,91,98,105,112],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7CY5NMS099ZRH9ECYS47ZKG","current-slide","Resolve which slide, page, and (optionally) selected element the user is currently viewing in the open-slide dev server. Consult this whenever the user references \"this page\", \"this slide\", \"this element\", \"the slide I'm on\", \"the current page\", or any deictic reference to slide content without naming it. Re-read `node_modules\u002F.open-slide\u002Fcurrent.json` at the start of every such turn — the user navigates between turns, so a value you read earlier in the conversation is almost certainly stale.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fcurrent-slide\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7CY5G6XHNY7Y8KVGGKF654E","create-theme","Use this skill when the user wants to create, draft, author, or extract a slide theme in this open-slide repo. Triggers on phrases like \"create a theme\", \"make a theme called X\", \"extract a theme from \u003Cslide>\", \"build a theme from these images\". Produces two paired files under `themes\u002F` — `\u003Cid>.md` (palette, typography, layout, fixed Title\u002FFooter components, motion) and `\u003Cid>.demo.tsx` (a runnable demo slide that the dev-UI Themes panel previews). Do NOT use for editing real slides — only for authoring the theme bundle.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fcreate-theme\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M7CY5B0DZNEVRY95X3QEKW3C","create-slide","Use this skill when the user wants to create, draft, author, or generate new slides \u002F a presentation in this open-slide repo. Triggers on phrases like \"make slides about X\", \"make a deck about X\", \"create a presentation\", \"draft slides for\", \"new slide\", \"a deck with speaker notes \u002F a script\", or when the user asks to add content under `slides\u002F`. Do NOT use for editing the framework itself — only for authoring content inside `slides\u002F\u003Cid>\u002F`.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fcreate-slide\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M7CY57ED279GA6QC3BFMPXG5","apply-comments","Apply pending @slide-comment markers written by the open-slide inspector tool. Use when the user asks to \"apply comments\", \"process slide comments\", \"apply the inspector comments\", or references markers left inside `slides\u002F\u003Cid>\u002Findex.tsx`.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fapply-comments\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M7CY53ZCYB0P3GYM2V3MEN1N","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M7CY524E4GQJMY7V5ZNB658W","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwriting-fragments\u002FSKILL.md",[],[]]