Ipollowork Template Generation
Create or update reusable iPolloWork templates through conversation for Design...
Install
npx skills add Devin-AXIS/iPolloWork --skill ipollowork-template-generation -g -a claude-code -y- Repository
- Devin-AXIS/iPolloWork7.3k
- Category
- Design
- Updated
- 3d ago
- License
- See repository
- Context cost
- Lightabout 829 tokens
- Runs scripts
- Yes, review before use
What it does
Create or update reusable iPolloWork templates through conversation for Design, Slides/native editable PPT, and HyperFrames Video. Use when planning, generating, repairing, validating, or saving a template package, manifest, reusable variables, cover, slide/PPT markers, video composition, or design-system token integration.
iPolloWork Template Generation
Create a reusable template, not a one-off artifact. The product-selected category and server validator are authoritative.
Route The Work
- Read references/template-generation-contract.md.
- Read exactly one surface reference:
- Design: the plugin-owned Design routing, then its matching category reference (site, app, poster, cards, report, article or other)
- Slides or native editable PPT: plugin-owned PPT rules, then Layout selection for reusable structure selection
- HyperFrames Video: the plugin-owned Video session contract
- When converting an existing project, preserve its category, surface, structure, and source files. Saving creates a new personal template; it never updates the source template.
Conversational Authoring
Guide the user in this order: purpose and audience, content structure, reusable variables, visual/design system, surface-specific constraints, generation and validation.
- Ask one consequential question at a time.
- Do not ask for information the user already supplied.
- Once the project is sufficiently specified, edit the project and show the result instead of extending the interview.
- Keep the package manifest, variable declarations, cover, and validation checklist current after every structural change.
- Treat the selected design system as optional context. Load only its manifest, usage guide, and design rules; never load every installed system.
- Use local assets or stable user-provided asset URLs. Do not invent dependencies.
