iPolloWork Presentations
Use this Skill for slide and presentation work inside the current iPolloWork Design session. It does not provide or control the built-in presentation canvas, template library, editor, or export UI.
Workflow
- Use the exact presentation entry file supplied by the active session and read it before editing.
- Read the confirmed brief and template metadata when present.
- On the initial brief application, plan a content-led narrative and page count, then select, repeat, recombine, remove, or reorder the installed template's slide patterns. Do not inherit its sample slide count, order, copy, or assets unless they fit the brief.
- Preserve the template's distinctive visual system, fixed stage, navigation/runtime behavior, editable object contract, and
design-tokens.css link so Design System controls and exports continue to work.
- For targeted and follow-up edits, preserve unrelated user-authored slides and content. Never replace the deck with a generic presentation.
- Keep source files, supporting assets, and requested exports inside the current
design/<session-id>/ directory.
- Check narrative order, visible content, canvas bounds, editability, and requested export output before reporting completion.
The active session's injected Design and template contracts remain authoritative whenever they are more specific.
1---2name: ipollowork-presentations3description: Create, revise, and verify slide presentations in an active iPolloWork Design session while retaining the selected template's visual and editable contracts.4---5
6# iPolloWork Presentations
7
8Use this Skill for slide and presentation work inside the current iPolloWork Design session. It does not provide or control the built-in presentation canvas, template library, editor, or export UI.
9
10## Workflow
11
121. Use the exact presentation entry file supplied by the active session and read it before editing.
132. Read the confirmed brief and template metadata when present.
143. On the initial brief application, plan a content-led narrative and page count, then select, repeat, recombine, remove, or reorder the installed template's slide patterns. Do not inherit its sample slide count, order, copy, or assets unless they fit the brief.
154. Preserve the template's distinctive visual system, fixed stage, navigation/runtime behavior, editable object contract, and `design-tokens.css` link so Design System controls and exports continue to work.
165. For targeted and follow-up edits, preserve unrelated user-authored slides and content. Never replace the deck with a generic presentation.
176. Keep source files, supporting assets, and requested exports inside the current `design/<session-id>/` directory.
187. Check narrative order, visible content, canvas bounds, editability, and requested export output before reporting completion.
19
20The active session's injected Design and template contracts remain authoritative whenever they are more specific.
gabrielmoreira