← PicsartCONTENT HISTORY

Update to Picsart

Snapshot Nov 7, 2026 · 00:09 UTC · version 2.4.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for large-scene-assembly

Skill instructions — Now says: ported-from: large-scene-authoring 1.1 at 55.75.0

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Picsart and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Nov 3, 2026 · 18:14 UTC

No removed lines (ordering may have changed)

After

Nov 7, 2026 · 00:09 UTC

ported-from: large-scene-authoring 1.1 at 55.75.0

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -4,6 +4,7 @@
 metadata:
   category: workflow
   version: '1.1'
+  ported-from: large-scene-authoring 1.1 at 55.75.0
 ---
 
 # Large scenes, small editing units
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: large-scene-assembly\ndescription: Build large editable scenes by decomposing a timeline into bounded scenes and reusable components, defining timing and asset contracts, then assembling and safely consolidating them. Use when authoring long videos, many scenes or layers, scene-by-scene designs, oversized JSON, fragile whole-document edits, reusable modules, or an editable handoff.\nmetadata:\n  category: workflow\n  version: '1.1'\n---\n\n# Large scenes, small editing units\n\nServed checks: `picsart_scene_check_contracts` runs contract records and reusable templates, `picsart_scene_check_motion` runs frame-complete motion records, and `picsart_scene_inspect` pages large sources; the one remaining limit is that pixel records have no automated checker, so inspect full-resolution rendered frames for them.\n\nKeep one editable source of truth and a thin assembly. Decompose by meaning and ownership, not an\narbitrary layer count. A card that travels across three beats is one persistent object, not three\nseparate scenes just because the storyboard has three frames.\n\n## Establish a manifest before growing the document\n\nRecord canvas/fps, ordered beats and durations, shared style tokens, component ids, assets, entry/exit\nstates, and the carrier (if any) across each seam. Use the compact\n[scene manifest](references/scene-manifest.md) when the timeline needs a durable handoff.\nThe manifest is authoring documentation, not an extra field injected into the scene schema.\nRecord checkable intent in a separate versioned contract sidecar (`linked-element-motion`), with\nstable contract ids, query target scopes and root-time phase windows. The same element may have\ndifferent relationships in different phases; document independent travel rather than forcing one\nparent relationship for its whole lifetime. Preserve these contracts alongside component revisions.\n\nChoose boundaries deliberately:\n\n| Unit | Representation and ownership |\n|---|---|\n| Local semantic unit: card, label, icon | Inline `composition` or a supported parent rig; animate its common placement once. |\n| Reusable independent scene | Scene asset/reference with explicit inputs, duration, dimensions and assets. |\n| Sequential beats | `track` clips; record how clip windows map into source time. |\n| Persistent foreground across beats | Parent-level layer spanning the interval, outside the replaced clips. |\n| Shared styling | Consistent authoring tokens/parameters; do not assume implicit inheritance between documents. |\n\nAsk `picsart_scene_capabilities` (`schema:<Name>` sections) for the exact relevant content/asset/parameter shapes. An inline composition\nuses its owning document's assets; a separately referenced scene owns its own asset scope. Do not\nrely on an undeclared parent asset, copied font id, or temporary URL being available in a child.\n\n## Author → verify → assemble, incrementally\n\n1. Build each semantic component with editable shapes, text, assets, keyframes and stable ids. Validate it with `picsart_scene_validate` and query entry, event and exit geometry with `picsart_scene_query_layout`.\n2. Inspect full-resolution stills with `picsart_scene_contact_sheet`, setting `resolution` to the scene dimensions; watch continuous video for motion claims.\n3. Preserve the accepted source revision and record its returned source or handle. A held handle is local to its tool surface, not a portable published URL.\n4. Assemble a thin root that owns order, clip windows, seams and persistent carriers. Children own their internal layout and motion.\n5. Check just before, at and after joins. Rerun supported `picsart_scene_lint_layout` relationships against independently recorded intent. Rerun contract records with `picsart_scene_check_contracts`; record uncovered assertions as unchecked.\n6. Continue component by component; recheck affected joins and overall playback. Show meaningful milestones during authorized autonomous iteration.\n\n## Keep edits bounded\n\n- Read the source subtree or named layer before bounded `picsart_scene_patch` edits. Page the structure with `picsart_scene_inspect` (outline, then read by patch address).\n- Keep stable semantic ids and distinguish definitions from instances. Query ids/scopes are for evaluated geometry, not guessed edit addresses.\n- Save revisions and explicitly update parent references when a child changes. An old parent does not silently follow a new child.\n- Recheck every affected instance's parameters, assets, duration and seams. Keep unrelated components unchanged.\n- Split work by component ownership only when parallel work is already authorized; one integration pass assembles accepted revisions.\n\n### Inspect authored structure before evaluating it\n\nPage authored structure with `picsart_scene_inspect`: outline (20 rows by default, up to 100, continue with `nextOffset`), then read an exact layer or field path by patch address. Keep the source document and its manifest, and read the intended component before editing. Distinguish authored layer addresses from evaluated query ids and composition scopes; never infer edit addresses from a geometric result. Use bounded `picsart_scene_patch` edits against known ids and field paths. If the source is not available, retrieve it through its saved source URL before editing; a layout query is not a complete source inventory.\n\nOutline rows also carry container pointers, `cameraExempt` and references, and the outline names the scope's authored camera fields. Only the root scene argument is loaded, through the guarded loader: follow an external scene deliberately, as its own `scene` argument, since the parent is not its editable body. `sceneSha256` is a canonical-JSON hash for paging, not a remote asset fingerprint; edit against immutable handles.\n\nInspect shared definitions in their own asset scope. Editing a shared definition affects all its instances; create an instance-specific definition and retarget only the intended consumer for a local variation. Keep the original revision and explicitly update parent references after a child changes. Revalidate and query every affected instance and seam. Source inspection cannot certify layout, media availability or motion.\n\n## Consolidate without losing the sources\n\nConsolidation means a coherent, resolvable deliverable—not indiscriminate flattening.\n\n1. Save a named source revision and its manifest before replacing references.\n2. Prefer a root with resolvable saved children when the consumer supports those handles/URLs.\n   If a self-contained document is required, inline scene assets with their scoped dependencies\n   using the current schema, or use `picsart_scene_expand_ref` for a supported local detachment.\n3. Expansion is not a universal recursive bundler. Read its diagnostics and `stillReferenced`;\n   process only the intended instance, preserve track timing, and do not delete assets still used.\n4. Check for unresolved/local-only handles, unavailable assets, namespace collisions, duration\n   changes, changed parameter defaults and missing fonts. A flat layer list is not proof of portability.\n5. Revalidate and compare pre/post geometry at component events and seams; preview those moments.\n   Run the relevant relationship lint again and watch the assembled video before claiming equivalence.\n\nDeliver the editable root, component revisions, manifest and rendered evidence. Say what is external\nand what was not verified; an MP4 alone is not an editable scene handoff.\n\nFor group vs. layout behavior use linked-element-motion (fetch with `picsart_scene_recipe`, name `linked-element-motion`);\nfor seam intent use motion-scene-continuity (fetch with `picsart_scene_recipe`, name `motion-scene-continuity`).\n\n**Research note:** independently authored for scene. General motion-design research informed the\nworkflow; no Hyperframes implementation, wording, examples or numerical presets were adopted.\n"
AFTER
"---\nname: large-scene-assembly\ndescription: Build large editable scenes by decomposing a timeline into bounded scenes and reusable components, defining timing and asset contracts, then assembling and safely consolidating them. Use when authoring long videos, many scenes or layers, scene-by-scene designs, oversized JSON, fragile whole-document edits, reusable modules, or an editable handoff.\nmetadata:\n  category: workflow\n  version: '1.1'\n  ported-from: large-scene-authoring 1.1 at 55.75.0\n---\n\n# Large scenes, small editing units\n\nServed checks: `picsart_scene_check_contracts` runs contract records and reusable templates, `picsart_scene_check_motion` runs frame-complete motion records, and `picsart_scene_inspect` pages large sources; the one remaining limit is that pixel records have no automated checker, so inspect full-resolution rendered frames for them.\n\nKeep one editable source of truth and a thin assembly. Decompose by meaning and ownership, not an\narbitrary layer count. A card that travels across three beats is one persistent object, not three\nseparate scenes just because the storyboard has three frames.\n\n## Establish a manifest before growing the document\n\nRecord canvas/fps, ordered beats and durations, shared style tokens, component ids, assets, entry/exit\nstates, and the carrier (if any) across each seam. Use the compact\n[scene manifest](references/scene-manifest.md) when the timeline needs a durable handoff.\nThe manifest is authoring documentation, not an extra field injected into the scene schema.\nRecord checkable intent in a separate versioned contract sidecar (`linked-element-motion`), with\nstable contract ids, query target scopes and root-time phase windows. The same element may have\ndifferent relationships in different phases; document independent travel rather than forcing one\nparent relationship for its whole lifetime. Preserve these contracts alongside component revisions.\n\nChoose boundaries deliberately:\n\n| Unit | Representation and ownership |\n|---|---|\n| Local semantic unit: card, label, icon | Inline `composition` or a supported parent rig; animate its common placement once. |\n| Reusable independent scene | Scene asset/reference with explicit inputs, duration, dimensions and assets. |\n| Sequential beats | `track` clips; record how clip windows map into source time. |\n| Persistent foreground across beats | Parent-level layer spanning the interval, outside the replaced clips. |\n| Shared styling | Consistent authoring tokens/parameters; do not assume implicit inheritance between documents. |\n\nAsk `picsart_scene_capabilities` (`schema:<Name>` sections) for the exact relevant content/asset/parameter shapes. An inline composition\nuses its owning document's assets; a separately referenced scene owns its own asset scope. Do not\nrely on an undeclared parent asset, copied font id, or temporary URL being available in a child.\n\n## Author → verify → assemble, incrementally\n\n1. Build each semantic component with editable shapes, text, assets, keyframes and stable ids. Validate it with `picsart_scene_validate` and query entry, event and exit geometry with `picsart_scene_query_layout`.\n2. Inspect full-resolution stills with `picsart_scene_contact_sheet`, setting `resolution` to the scene dimensions; watch continuous video for motion claims.\n3. Preserve the accepted source revision and record its returned source or handle. A held handle is local to its tool surface, not a portable published URL.\n4. Assemble a thin root that owns order, clip windows, seams and persistent carriers. Children own their internal layout and motion.\n5. Check just before, at and after joins. Rerun supported `picsart_scene_lint_layout` relationships against independently recorded intent. Rerun contract records with `picsart_scene_check_contracts`; record uncovered assertions as unchecked.\n6. Continue component by component; recheck affected joins and overall playback. Show meaningful milestones during authorized autonomous iteration.\n\n## Keep edits bounded\n\n- Read the source subtree or named layer before bounded `picsart_scene_patch` edits. Page the structure with `picsart_scene_inspect` (outline, then read by patch address).\n- Keep stable semantic ids and distinguish definitions from instances. Query ids/scopes are for evaluated geometry, not guessed edit addresses.\n- Save revisions and explicitly update parent references when a child changes. An old parent does not silently follow a new child.\n- Recheck every affected instance's parameters, assets, duration and seams. Keep unrelated components unchanged.\n- Split work by component ownership only when parallel work is already authorized; one integration pass assembles accepted revisions.\n\n### Inspect authored structure before evaluating it\n\nPage authored structure with `picsart_scene_inspect`: outline (20 rows by default, up to 100, continue with `nextOffset`), then read an exact layer or field path by patch address. Keep the source document and its manifest, and read the intended component before editing. Distinguish authored layer addresses from evaluated query ids and composition scopes; never infer edit addresses from a geometric result. Use bounded `picsart_scene_patch` edits against known ids and field paths. If the source is not available, retrieve it through its saved source URL before editing; a layout query is not a complete source inventory.\n\nOutline rows also carry container pointers, `cameraExempt` and references, and the outline names the scope's authored camera fields. Only the root scene argument is loaded, through the guarded loader: follow an external scene deliberately, as its own `scene` argument, since the parent is not its editable body. `sceneSha256` is a canonical-JSON hash for paging, not a remote asset fingerprint; edit against immutable handles.\n\nInspect shared definitions in their own asset scope. Editing a shared definition affects all its instances; create an instance-specific definition and retarget only the intended consumer for a local variation. Keep the original revision and explicitly update parent references after a child changes. Revalidate and query every affected instance and seam. Source inspection cannot certify layout, media availability or motion.\n\n## Consolidate without losing the sources\n\nConsolidation means a coherent, resolvable deliverable—not indiscriminate flattening.\n\n1. Save a named source revision and its manifest before replacing references.\n2. Prefer a root with resolvable saved children when the consumer supports those handles/URLs.\n   If a self-contained document is required, inline scene assets with their scoped dependencies\n   using the current schema, or use `picsart_scene_expand_ref` for a supported local detachment.\n3. Expansion is not a universal recursive bundler. Read its diagnostics and `stillReferenced`;\n   process only the intended instance, preserve track timing, and do not delete assets still used.\n4. Check for unresolved/local-only handles, unavailable assets, namespace collisions, duration\n   changes, changed parameter defaults and missing fonts. A flat layer list is not proof of portability.\n5. Revalidate and compare pre/post geometry at component events and seams; preview those moments.\n   Run the relevant relationship lint again and watch the assembled video before claiming equivalence.\n\nDeliver the editable root, component revisions, manifest and rendered evidence. Say what is external\nand what was not verified; an MP4 alone is not an editable scene handoff.\n\nFor group vs. layout behavior use linked-element-motion (fetch with `picsart_scene_recipe`, name `linked-element-motion`);\nfor seam intent use motion-scene-continuity (fetch with `picsart_scene_recipe`, name `motion-scene-continuity`).\n\n**Research note:** independently authored for scene. General motion-design research informed the\nworkflow; no Hyperframes implementation, wording, examples or numerical presets were adopted.\n"
Full snapshot data
{
  "description": "Build large editable scenes by decomposing a timeline into bounded scenes and reusable components, defining timing and asset contracts, then assembling and safely consolidating them. Use when authoring long videos, many scenes or layers, scene-by-scene designs, oversized JSON, fragile whole-document edits, reusable modules, or an editable handoff.",
  "included_files": [
    {
      "relative_path": "references/scene-manifest.md",
      "size_in_bytes": 1971
    }
  ],
  "name": "large-scene-assembly",
  "skill_md_contents": "---\nname: large-scene-assembly\ndescription: Build large editable scenes by decomposing a timeline into bounded scenes and reusable components, defining timing and asset contracts, then assembling and safely consolidating them. Use when authoring long videos, many scenes or layers, scene-by-scene designs, oversized JSON, fragile whole-document edits, reusable modules, or an editable handoff.\nmetadata:\n  category: workflow\n  version: '1.1'\n  ported-from: large-scene-authoring 1.1 at 55.75.0\n---\n\n# Large scenes, small editing units\n\nServed checks: `picsart_scene_check_contracts` runs contract records and reusable templates, `picsart_scene_check_motion` runs frame-complete motion records, and `picsart_scene_inspect` pages large sources; the one remaining limit is that pixel records have no automated checker, so inspect full-resolution rendered frames for them.\n\nKeep one editable source of truth and a thin assembly. Decompose by meaning and ownership, not an\narbitrary layer count. A card that travels across three beats is one persistent object, not three\nseparate scenes just because the storyboard has three frames.\n\n## Establish a manifest before growing the document\n\nRecord canvas/fps, ordered beats and durations, shared style tokens, component ids, assets, entry/exit\nstates, and the carrier (if any) across each seam. Use the compact\n[scene manifest](references/scene-manifest.md) when the timeline needs a durable handoff.\nThe manifest is authoring documentation, not an extra field injected into the scene schema.\nRecord checkable intent in a separate versioned contract sidecar (`linked-element-motion`), with\nstable contract ids, query target scopes and root-time phase windows. The same element may have\ndifferent relationships in different phases; document independent travel rather than forcing one\nparent relationship for its whole lifetime. Preserve these contracts alongside component revisions.\n\nChoose boundaries deliberately:\n\n| Unit | Representation and ownership |\n|---|---|\n| Local semantic unit: card, label, icon | Inline `composition` or a supported parent rig; animate its common placement once. |\n| Reusable independent scene | Scene asset/reference with explicit inputs, duration, dimensions and assets. |\n| Sequential beats | `track` clips; record how clip windows map into source time. |\n| Persistent foreground across beats | Parent-level layer spanning the interval, outside the replaced clips. |\n| Shared styling | Consistent authoring tokens/parameters; do not assume implicit inheritance between documents. |\n\nAsk `picsart_scene_capabilities` (`schema:<Name>` sections) for the exact relevant content/asset/parameter shapes. An inline composition\nuses its owning document's assets; a separately referenced scene owns its own asset scope. Do not\nrely on an undeclared parent asset, copied font id, or temporary URL being available in a child.\n\n## Author → verify → assemble, incrementally\n\n1. Build each semantic component with editable shapes, text, assets, keyframes and stable ids. Validate it with `picsart_scene_validate` and query entry, event and exit geometry with `picsart_scene_query_layout`.\n2. Inspect full-resolution stills with `picsart_scene_contact_sheet`, setting `resolution` to the scene dimensions; watch continuous video for motion claims.\n3. Preserve the accepted source revision and record its returned source or handle. A held handle is local to its tool surface, not a portable published URL.\n4. Assemble a thin root that owns order, clip windows, seams and persistent carriers. Children own their internal layout and motion.\n5. Check just before, at and after joins. Rerun supported `picsart_scene_lint_layout` relationships against independently recorded intent. Rerun contract records with `picsart_scene_check_contracts`; record uncovered assertions as unchecked.\n6. Continue component by component; recheck affected joins and overall playback. Show meaningful milestones during authorized autonomous iteration.\n\n## Keep edits bounded\n\n- Read the source subtree or named layer before bounded `picsart_scene_patch` edits. Page the structure with `picsart_scene_inspect` (outline, then read by patch address).\n- Keep stable semantic ids and distinguish definitions from instances. Query ids/scopes are for evaluated geometry, not guessed edit addresses.\n- Save revisions and explicitly update parent references when a child changes. An old parent does not silently follow a new child.\n- Recheck every affected instance's parameters, assets, duration and seams. Keep unrelated components unchanged.\n- Split work by component ownership only when parallel work is already authorized; one integration pass assembles accepted revisions.\n\n### Inspect authored structure before evaluating it\n\nPage authored structure with `picsart_scene_inspect`: outline (20 rows by default, up to 100, continue with `nextOffset`), then read an exact layer or field path by patch address. Keep the source document and its manifest, and read the intended component before editing. Distinguish authored layer addresses from evaluated query ids and composition scopes; never infer edit addresses from a geometric result. Use bounded `picsart_scene_patch` edits against known ids and field paths. If the source is not available, retrieve it through its saved source URL before editing; a layout query is not a complete source inventory.\n\nOutline rows also carry container pointers, `cameraExempt` and references, and the outline names the scope's authored camera fields. Only the root scene argument is loaded, through the guarded loader: follow an external scene deliberately, as its own `scene` argument, since the parent is not its editable body. `sceneSha256` is a canonical-JSON hash for paging, not a remote asset fingerprint; edit against immutable handles.\n\nInspect shared definitions in their own asset scope. Editing a shared definition affects all its instances; create an instance-specific definition and retarget only the intended consumer for a local variation. Keep the original revision and explicitly update parent references after a child changes. Revalidate and query every affected instance and seam. Source inspection cannot certify layout, media availability or motion.\n\n## Consolidate without losing the sources\n\nConsolidation means a coherent, resolvable deliverable—not indiscriminate flattening.\n\n1. Save a named source revision and its manifest before replacing references.\n2. Prefer a root with resolvable saved children when the consumer supports those handles/URLs.\n   If a self-contained document is required, inline scene assets with their scoped dependencies\n   using the current schema, or use `picsart_scene_expand_ref` for a supported local detachment.\n3. Expansion is not a universal recursive bundler. Read its diagnostics and `stillReferenced`;\n   process only the intended instance, preserve track timing, and do not delete assets still used.\n4. Check for unresolved/local-only handles, unavailable assets, namespace collisions, duration\n   changes, changed parameter defaults and missing fonts. A flat layer list is not proof of portability.\n5. Revalidate and compare pre/post geometry at component events and seams; preview those moments.\n   Run the relevant relationship lint again and watch the assembled video before claiming equivalence.\n\nDeliver the editable root, component revisions, manifest and rendered evidence. Say what is external\nand what was not verified; an MP4 alone is not an editable scene handoff.\n\nFor group vs. layout behavior use linked-element-motion (fetch with `picsart_scene_recipe`, name `linked-element-motion`);\nfor seam intent use motion-scene-continuity (fetch with `picsart_scene_recipe`, name `motion-scene-continuity`).\n\n**Research note:** independently authored for scene. General motion-design research informed the\nworkflow; no Hyperframes implementation, wording, examples or numerical presets were adopted.\n"
}

SHA-256 of public snapshot: c1fd8b357da58ed74f973f7bf2057aa6d6222924729dae6d675069844cb61534