Update

.agents/skills/image-editing/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: image-editing
+description: Edit an image from the active iPolloWork Image Studio selection or mask without overwriting the source image.
+---
+
+# Image editing
+
+Use this Skill when an existing workspace image is open in Image Studio.
+
+1. Treat the active source path and current selection as authoritative.
+2. Change only the requested region when a mask is present. Preserve unselected composition, identity, typography, and brand details.
+3. Ask for a clearer selection only when the requested target cannot be inferred from the mask and prompt.
+4. Save every generated edit as a new workspace image. Never overwrite or delete the source image.
+5. Return the edited workspace path so Design, Video, websites, and chat artifacts can reuse it.

.agents/skills/image-generation/SKILL.md

@@ -0,0 +1,15 @@
+---
+name: image-generation
+description: Generate image assets through iPolloWork's image service, whether Image Studio is open or closed.
+---
+
+# Image generation
+
+Use this Skill for a requested new image or a missing supporting image identified while authoring a PPT, website or video. Image Studio does not need to be open. Plan assets during initial creation/full redesign; preserve narrow edit scopes and explicit no-image requests. Reuse suitable assets first; visual clarity and context are valid reasons to generate, not only absolute necessity. Assess the visual purpose, existing assets and best medium internally; no separate assessment report is required. Keep diagrams editable, treat pure decoration as optional, and never present generated illustrative scenes as real evidence.
+
+1. Preserve the user's subject, composition, text, brand, and format requirements.
+2. Discover `openai-image-generation` using `ipollowork_extension_list_actions`, then call its `status` action. Call status first and check authorization, capabilities and supported parameters. Preserve a model explicitly selected for this task or captured workbench request. An ordinary requested image or a supporting asset inside an authorized Design, PPT or Video task is an approved automatic-selection flow: use a suitable authorized saved preference when present; otherwise use the suitable authorized `defaultModel`, or the first suitable authorized model in returned product order when `defaultModel` cannot perform the operation. Do not ask or leave the asset pending solely because multiple suitable models are authorized. Ask once only when the user requested a choice, an explicit model is unavailable and substitution materially changes provider, cost or capability, or no automatic candidate satisfies the task scope and allowed cost settings. Reuse the resolved task selection for compatible assets and disclose the model used after generation. `defaultModel` is a computed automatic candidate, not a persisted preference; never save it without an explicit request. Missing authorization or an unqueryable capability must not block the caller or open settings: report the state and continue. Never request keys in chat. Do not invent preferences or budgets. Pass the chosen stable model ID explicitly. Never submit variants outside scope; query or recover uncertain jobs before resubmitting. For an explicit workbench settings/annotation request, honor its captured selection instructions; do not change the workbench model through UI automation.
+3. After resolving the model by this policy, call `image_generate` through `ipollowork_extension_call` with that exact stable `model` ID, the prompt, and optional quality/size. Include style, camera, and lighting requirements in the prompt.
+4. Use this server action for ordinary chat requests even when Image Studio is open. UI tool discovery and opening the workbench are unnecessary. Use workbench tools only when the user explicitly requests the current workbench settings or selection. Never request, print, or place API keys in a prompt or workspace file.
+5. Save generated results as new workspace artifacts and include a Markdown image link to the exact returned path in the final response. Never claim success until the action returns the saved file. For a composition, place the saved image under its existing assets directory, use a project-relative reference, and verify loading, crop and export compatibility before delivering the composition. Standalone images can be opened in Image Studio from the conversation.
+6. Keep the first pass focused. Generate variants only when the user asks for alternatives.

.agents/skills/ipollowork-design-editorial/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: ipollowork-design-editorial
+description: Create or edit articles and reports in the current iPolloWork Design session.
+---
+
+# iPolloWork Articles and Reports
+
+Use for manifest category `article` or `report`; route other categories through `ipollowork-design-studio` before editing. Do not recategorize.
+
+Use the injected exact source inside `design/<session-id>/`; read it and `design-tokens.css`. Preserve `--ipw-*` tokens/variable bindings, component IDs, editable/locked markers, runtime and selected scope. A stale locator requires a new selection before editing. Theme-only edits preserve content/assets/geometry. The host owns preview/export; no replacement project, preview host or application-source edits.
+
+Use only [Article rules](../ipollowork-design-studio/references/design-article.md) for `article`, or [Report rules](../ipollowork-design-studio/references/design-report.md) for `report`.
+
+Targeted copy/selection/theme edits read affected type sections only; skip catalogs and unchanged layout/media guidance. Creation/structural work reads applicable content/style/layout sections of [Shared guidance](../ipollowork-design-studio/references/shared-guidelines.md); catalogs are for layout selection. Asset work uses its media workflow; initial/full authoring plans before layout and checks saved placement. Valid unchanged local/theme assets need no new plan/generation.
+
+Follow active type acceptance for reading, evidence and destination through supported host preview; actual email also needs the [Other rules](../ipollowork-design-studio/references/design-other.md) email boundary. Shared style/token changes require whole-artifact rechecking. Verify affected editing/interaction and requested supported exports; disclose unavailable/unperformed checks. Resolve installed links once; report missing references without searching other checkouts.

.agents/skills/ipollowork-design-graphics/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: ipollowork-design-graphics
+description: Create or edit posters and social card series in the current iPolloWork Design session.
+---
+
+# iPolloWork Posters and Cards
+
+Use for manifest category `poster` or `cards`; route other categories through `ipollowork-design-studio` before editing. Do not recategorize.
+
+Use the injected exact source inside `design/<session-id>/`; read it and `design-tokens.css`. Preserve `--ipw-*` tokens/variable bindings, component IDs, editable/locked markers, runtime and selected scope. A stale locator requires a new selection before editing. Theme-only edits preserve content/assets/geometry. The host owns preview/export; no replacement project, preview host or application-source edits.
+
+Use only [Poster rules](../ipollowork-design-studio/references/design-poster.md) for `poster`, or [Card rules](../ipollowork-design-studio/references/design-cards.md) for `cards`.
+
+Targeted copy/selection/theme edits read affected type sections only; skip catalogs and unchanged layout/media guidance. Creation/structural work reads applicable content/style/layout sections of [Shared guidance](../ipollowork-design-studio/references/shared-guidelines.md); catalogs are for layout selection. Asset work uses its media workflow; initial/full authoring plans before layout and checks saved placement. Valid unchanged local/theme assets need no new plan/generation.
+
+Follow active type acceptance for the whole canvas or every card in order at final dimensions, using supported host preview. Shared style/token changes require whole-artifact rechecking. Verify affected editing/interaction and requested supported exports; disclose unavailable/unperformed checks. Resolve installed links once; report missing references without searching other checkouts.

.agents/skills/ipollowork-design-studio/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: ipollowork-design-studio
+description: Route iPolloWork Design sessions by category and author other designs.
+---
+
+# iPolloWork Design Studio
+
+Hand off by manifest category before source reads/edits or shared/type guidance; retain the category.
+
+| Category | Handoff |
+| --- | --- |
+| `site`, `app` | [Websites and app interfaces](../ipollowork-design-web/SKILL.md) |
+| `poster`, `cards` | [Posters and cards](../ipollowork-design-graphics/SKILL.md) |
+| `article`, `report` | [Articles and reports](../ipollowork-design-editorial/SKILL.md) |
+| `slides` | [Presentations](../ipollowork-presentations/SKILL.md) |
+| `video` | `ipollowork-video-studio` on the Video surface |
+| `other` | Continue below |
+
+## Other designs only
+
+Read the injected exact source under `design/<session-id>/` and `design-tokens.css`. Preserve `--ipw-*` tokens/variable bindings, component IDs, editable/locked markers, runtime and selected scope. Stale selection requires a new locator before edits. No replacement project, preview host or application-source edits.
+
+Read only affected [Other rules](references/design-other.md) for targeted/theme edits; protect unrelated work, and preserve content/assets/geometry for themes. Creation/structural work uses applicable [Design authoring](references/design.md) and [Shared guidance](references/shared-guidelines.md) sections; assets follow shared media plan/check. Apply Other acceptance, affected editing/interaction and requested supported export checks; disclose unverified results.
+
+Resolve installed links once; report missing references without other-checkout searches.

.agents/skills/ipollowork-design-studio/references/design-app.md

@@ -0,0 +1,24 @@
+<!-- Distribution reference: maintained in examples/plugin-packages/design-agent/skills/ipollowork-design-studio/references/; checked against the source by plugin-package-manifest.test.ts. -->
+
+# Application Interface Rules
+
+Use for `app`: screens, dashboards and interactive prototypes. Follow this installed Skill's task scope; consult only applicable shared sections and type rules for the requested change.
+
+## Tasks and structure
+
+- Identify the main user task, entry state, action and observable outcome. Select screens and states from that flow rather than copying a sample dashboard.
+- Reuse navigation, controls, spacing and state language. Do not fill space with invented analytics, customers or activity.
+- Choose suitable forms, tables, lists, inspectors and detail views. Marketing sections are not a substitute for a usable application flow.
+- Keep the implementation boundary explicit: an HTML prototype may demonstrate local interaction, but does not establish authentication, persistence, payment or remote integration.
+
+## States and assets
+
+- Cover normal, loading, empty, invalid, failed and completed states needed by the flow. Keep transitions consistent; success must reflect an actual or clearly labeled simulated outcome.
+- Preserve input after validation errors. Explain unavailable actions and protect destructive actions appropriately within the artifact's scope.
+- Use labeled inputs, accessible state feedback, keyboard navigation and visible focus. Test menus, dialogs, escape/close and forms; do not rely on hover alone.
+- Adapt dense navigation/data to narrow screens through intentional scrolling or alternate views, rather than clipping controls or squeezing labels.
+- Follow shared media rules for meaningful product/content visuals. Prefer editable charts for data and consistent icons for navigation; decorative generation remains optional.
+
+## Acceptance
+
+Drive the primary flow from entry to outcome, including relevant empty/error/recovery cases. Check representative widths, long labels and realistic data volumes. Verify edit/save claims in the supported runtime. Distinguish prototype behavior from connected services and identify untested states.

.agents/skills/ipollowork-design-studio/references/design-article.md

@@ -0,0 +1,23 @@
+<!-- Distribution reference: maintained in examples/plugin-packages/design-agent/skills/ipollowork-design-studio/references/; checked against the source by plugin-package-manifest.test.ts. -->
+
+# Article Rules
+
+Use for `article`: editorial pages, long-form reading and WeChat articles. Follow this installed Skill's task scope; consult only applicable shared sections and type rules for the requested change.
+
+## Reading and editorial structure
+
+- Preserve facts, meaning and the requested voice. Derive title, introduction, sections, quotes and conclusion from content rather than a fixed template structure.
+- Prioritize sustained reading: suitable line measure, paragraph rhythm and heading relationships. Check Chinese punctuation, mixed scripts and meaningful line breaks in the final font.
+- Avoid turning every paragraph into a decorative card or slide. Use lists, emphasis and pull quotes to clarify; do not duplicate passages merely to fill slots.
+- Keep captions, credits, links and sources associated with their passage/image. Never invent bylines, publication dates or attribution.
+
+## Assets and destination
+
+- Apply shared media rules to useful cover, setting, subject and supporting illustrations. Atmosphere is a valid purpose; there is no image quota.
+- Preserve fixed brand header/footer images and nodes marked `data-ipw-fixed="true"`. Targeted text editing does not authorize changing locked elements.
+- Distinguish browser articles from publishing-platform content. Use supported styles, links and interactions for the destination; browser preview does not establish WeChat paste/publishing fidelity.
+- For actual email delivery, also read `design-other.md`'s email boundary. An article preview is not email-client verification.
+
+## Acceptance
+
+Read the full article in order and inspect its beginning, middle and ending at narrow and wide widths. Check loading/crops, captions, long links, spacing and CTA destinations. Verify requested transfer/export where available; otherwise retain the editable file and identify the unverified destination. Never claim publication without performing the authorized action.

.agents/skills/ipollowork-design-studio/references/design-cards.md

@@ -0,0 +1,23 @@
+<!-- Distribution reference: maintained in examples/plugin-packages/design-agent/skills/ipollowork-design-studio/references/; checked against the source by plugin-package-manifest.test.ts. -->
+
+# Card Series Rules
+
+Use for `cards`: social carousels and shareable information card series. Follow this installed Skill's task scope; consult only applicable shared sections and type rules for the requested change.
+
+## Sequence and capacity
+
+- Content determines card count unless explicitly constrained. Give each card a clear role and maintain opening, progression and conclusion without forcing separate cards for each.
+- Preserve requested channel dimensions and consistent series geometry. Do not convert cards into PPT or impose long-page scrolling on export canvases.
+- Reuse typography, margins, attribution and numbering. Vary structure for different content relationships, not simply for decoration.
+- Retain sufficient context when cards are shared alone. Keep values, units, sources and qualifications together; do not split claims from conditions to fit.
+- Recompose or split dense content within user constraints rather than shrinking text. Keep content editable where supported.
+
+## Assets and behavior
+
+- Apply shared media rules across the series. Reuse a coherent visual family and check each crop; avoid redundant generation for repeated subjects.
+- Do not bake final copy, figures or real logos into generated illustrations when separate editable objects are required.
+- If interactive carousel behavior is requested, test next/previous, focus and touch. Static card exports do not need invented navigation or hover effects.
+
+## Acceptance
+
+Inspect every card and the series in order at final size and typical mobile reading scale. Check blank/duplicate cards, lost endings, numbering, safe areas and visual consistency. Verify requested export count, dimensions and order; report untested export behavior separately.

.agents/skills/ipollowork-design-studio/references/design-other.md

@@ -0,0 +1,22 @@
+<!-- Distribution reference: maintained in examples/plugin-packages/design-agent/skills/ipollowork-design-studio/references/; checked against the source by plugin-package-manifest.test.ts. -->
+
+# Other Design Rules
+
+Use for `other` when no existing category fits the active artifact. Follow this installed Skill's task scope; consult only applicable shared sections and type rules for the requested change. Do not silently change an existing manifest to fit the routing table.
+
+## Establish the contract
+
+- Infer purpose, audience, canvas/viewport, editable content and format from the request/current files. Ask only about missing choices that materially change delivery.
+- Record constraints briefly in the task. Do not invent a new category, runtime, app scaffold or specification file.
+- Borrow relevant checks from the nearest type: site responsiveness, poster geometry, report evidence or article readability. Do not import unrelated navigation, pagination or exports.
+- Apply shared layout/media rules. Without a dedicated catalog, reuse local patterns or create scoped structures with the existing theme.
+
+## Special delivery boundaries
+
+- Email: distinguish web mockups from actual email HTML. Establish target clients and a supported export/transfer path. Use compatible structure/styles, non-scripted actions and supported asset delivery. Check narrow layouts, image blocking, fallback text and links. Claim compatibility only for clients actually inspected.
+- Image-led work: use media Skills for raster generation/editing; use Design for surrounding editable composition when needed. Raster references do not establish recoverable text layers or native vectors.
+- Unusual print/interactive formats: inspect actual runtime/export capabilities before promising them. Continue independent work and identify concrete unsupported requirements.
+
+## Acceptance
+
+Verify the inferred contract using real content and the supported preview. Check completeness, readability, geometry, assets and relevant interactions; inspect requested exports when available. Identify which type checks were used and remaining limitations. HTML validity alone cannot establish acceptance of an unknown format.

.agents/skills/ipollowork-design-studio/references/design-poster.md

@@ -0,0 +1,22 @@
+<!-- Distribution reference: maintained in examples/plugin-packages/design-agent/skills/ipollowork-design-studio/references/; checked against the source by plugin-package-manifest.test.ts. -->
+
+# Poster and Banner Rules
+
+Use for `poster`: a single promotional canvas, poster or banner. Follow this installed Skill's task scope; consult only applicable shared sections and type rules for the requested change.
+
+## Canvas and hierarchy
+
+- Use requested dimensions, aspect ratio and viewing context. Preserve the existing canvas when unspecified; clarify only consequential missing dimensions. Do not inherit PPT's 16:9 requirement.
+- Establish a focal message, supporting information and action. Preserve required dates, locations, terms, logos and contact details without treating sample copy as mandatory.
+- Maintain safe margins and deliberate alignment. Fixed export canvases scale for preview without composition reflow. Responsive web banners may need a separate narrow composition; inspect each requested variant.
+- Keep text/graphics editable where supported. Do not replace all content with a generated raster poster when editability is required.
+
+## Assets and output
+
+- Follow shared media rules for campaign, subject and atmosphere imagery. Preserve real product geometry and brand marks; never fabricate sponsors or endorsements.
+- Judge resolution at final export size. Check crops, contrast, important subjects and text over images. Keep QR codes undistorted and test their destination when present.
+- Apply print bleed, color-space and production requirements only when requested and supported. Browser HTML alone does not prove press-ready output.
+
+## Acceptance
+
+Inspect the entire canvas at final dimensions and intended reading scale. Check required copy, safe margins, overlap, sharpness and brand proportions. Inspect actual exports when requested; distinguish editable HTML from verified raster/print output. Static delivery needs no decorative animation.