ipollowork-presentations
Create, revise, and verify slide presentations in an active iPolloWork Design session while retaining the selected template's visual and editable contracts.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/ipollowork-presentations && cp -r /tmp/ipollowork-presentations/examples/plugin-packages/design-agent/skills/ipollowork-presentations ~/.claude/skills/ipollowork-presentationsSKILL.md
# 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 1. Use the exact presentation entry file supplied by the active session and read it before editing. 2. Read the confirmed brief and template metadata when present. 3. 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. 4. 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. 5. For targeted and follow-up edits, preserve unrelated user-authored slides and content. Never replace the deck with a generic presentation. 6. Keep source files, supporting assets, and requested exports inside the current `design/<session-id>/` directory. 7. 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.
Search and summarize material from the Acme research service.
Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.