image-generation
Generate image assets through the active iPolloWork Image Studio while preserving structured style, camera, lighting, size, and quality choices.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/image-generation && cp -r /tmp/image-generation/examples/plugin-packages/image-studio/skills/image-generation ~/.claude/skills/image-generationSKILL.md
# Image generation Use this Skill when the user wants a new image and Image Studio is active. 1. Preserve the user's subject, composition, text, brand, and format requirements. 2. Put visual style, camera, and lighting into the matching structured Image Studio fields when possible instead of repeating them throughout the prompt. 3. Use the installed provider exposed by Image Studio. Never request, print, or place API keys in a prompt or workspace file. 4. Save generated results as new workspace artifacts and report the exact returned path. 5. Keep the first pass focused. Generate variants only when the user asks for alternatives.
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.