Update to Planner5D: Plan, Build, Create
Snapshot Oct 24, 2026 · 13:13 UTC · version 1.3.3
Collection source: downloaded plugin package.
Payment or plan references changed
Skill instructions — Now says: For a subscription denial, use [subscription access responses](../planner5d-native-app/references/subscription-access.md). Explain the required plan and link...
Observed in published text. Live prices and checkout terms have not been verified by this change.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 9, 2026 · 18:02 UTC
Open the intended project through the app's navigation, then read `editorGetContext` and `getWebMcpGuide` help for `editorSubmitRender`. The live request schema defines preparation, generation and status recovery. 2. Prepare the screensh...
Oct 24, 2026 · 13:13 UTC
For a subscription denial, use [subscription access responses](../planner5d-native-app/references/subscription-access.md). Explain the required plan and link to [Planner 5D pricing](https://planner5d.com/pricing). Keep subscription-state...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -5,14 +5,18 @@ # Planner 5D AI rendering -Open the intended project through the app's navigation, then read `editorGetContext` and `getWebMcpGuide` help for `editorSubmitRender`. The live request schema defines preparation, generation and status recovery. +For a subscription denial, use [subscription access responses](../planner5d-native-app/references/subscription-access.md). Explain the required plan and link to [Planner 5D pricing](https://planner5d.com/pricing). Keep subscription-state errors, credit limits and technical failures separate. + +Open the intended project through the app's navigation, then read `editorGetContext`. Load `editorPrepareAIRender`, `editorGenerateAIRender` and `editorGetAIRenderStatus`. Their typed schemas define preparation, generation and status recovery. For the person's specific furniture, first complete `planner5d-model-import` and verify its native placement, real scale and readiness. For PDF/plan → AI render, complete `planner5d-floorplan-recheck` and the requested furnishing before capture. Reuse the existing project and verify the source before rendering; do not silently substitute a catalog lookalike. If a furnished interior is requested, an empty plan does not fulfill it. An explicit architecture-only/render-only brief preserves that narrower scope. When comparing product/finish variants, preserve verified geometry and a consistent source camera unless the person asks for different views. 1. Choose the view with native 3D preview/camera controls and inspect the actual image. Ensure needed models and materials are loaded. For camera information, request `includeCamera:true` only when the editor is already in 3D. -2. Prepare the screenshot-based AI request with the actual expected project hash and a stable request ID. Preparation persists native pixels and returns the signed price/quote; it does not submit conventional scene geometry to the server renderer. +2. Call `editorPrepareAIRender` with the actual expected project hash and a stable request ID. Preparation persists native pixels and returns the signed price/quote; it does not submit conventional scene geometry to the server renderer. 3. Describe the requested appearance using source evidence. Preserve wall/opening locations, furniture proportions, dark material texture, glass/mirror behavior and visible structural features. Describe enabled lighting and its observed positions; do not invent extra fixtures or alter the layout to improve a picture. -4. Generate only under the user's authorized credit budget, passing the prepared quote and explicit maximum credits required by the live schema. Native permissions and billing decide eligibility and charges. -5. Follow the existing generation through status using its returned identity. Check completion, saved output, visual fidelity and the accessible image. A retry must recover the previous request before creating another charged generation. +4. Call `editorGenerateAIRender` only under the user's authorized credit budget, passing the prepared quote and explicit maximum credits required by the live schema. Native permissions and billing decide eligibility and charges. +5. Call `editorGetAIRenderStatus` for the existing generation using its returned identity. Check completion, saved output, visual fidelity and the accessible image. A retry must recover the previous request before creating another charged generation. Use native screenshots/previews for source verification. Keep credentials, signed upload/download tokens and one-use login tickets out of user-facing output. Return the verified render and project link, with any visible fidelity differences. An AI image does not certify room measurements or a construction drawing. + +After the original job succeeds, use `show_planner5d_ai_render` with that requestId and current project/panel/document context. Show the real render in chat and compare it with the captured scene. The presentation step reads the completed original and does not generate, charge or change the scene. Keep host preview and original-file download outcomes separate.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: planner5d-ai-render\ndescription: Generate or refine a photorealistic AI image from a native Planner 5D scene screenshot while preserving geometry, materials and visible lighting. Use the editor's quoted screenshot-to-AI workflow.\n---\n\n# Planner 5D AI rendering\n\nOpen the intended project through the app's navigation, then read `editorGetContext` and `getWebMcpGuide` help for `editorSubmitRender`. The live request schema defines preparation, generation and status recovery.\n\nFor the person's specific furniture, first complete `planner5d-model-import` and verify its native placement, real scale and readiness. For PDF/plan → AI render, complete `planner5d-floorplan-recheck` and the requested furnishing before capture. Reuse the existing project and verify the source before rendering; do not silently substitute a catalog lookalike. If a furnished interior is requested, an empty plan does not fulfill it. An explicit architecture-only/render-only brief preserves that narrower scope. When comparing product/finish variants, preserve verified geometry and a consistent source camera unless the person asks for different views.\n\n1. Choose the view with native 3D preview/camera controls and inspect the actual image. Ensure needed models and materials are loaded. For camera information, request `includeCamera:true` only when the editor is already in 3D.\n2. Prepare the screenshot-based AI request with the actual expected project hash and a stable request ID. Preparation persists native pixels and returns the signed price/quote; it does not submit conventional scene geometry to the server renderer.\n3. Describe the requested appearance using source evidence. Preserve wall/opening locations, furniture proportions, dark material texture, glass/mirror behavior and visible structural features. Describe enabled lighting and its observed positions; do not invent extra fixtures or alter the layout to improve a picture.\n4. Generate only under the user's authorized credit budget, passing the prepared quote and explicit maximum credits required by the live schema. Native permissions and billing decide eligibility and charges.\n5. Follow the existing generation through status using its returned identity. Check completion, saved output, visual fidelity and the accessible image. A retry must recover the previous request before creating another charged generation.\n\nUse native screenshots/previews for source verification. Keep credentials, signed upload/download tokens and one-use login tickets out of user-facing output. Return the verified render and project link, with any visible fidelity differences. An AI image does not certify room measurements or a construction drawing.\n"
"---\nname: planner5d-ai-render\ndescription: Generate or refine a photorealistic AI image from a native Planner 5D scene screenshot while preserving geometry, materials and visible lighting. Use the editor's quoted screenshot-to-AI workflow.\n---\n\n# Planner 5D AI rendering\n\nFor a subscription denial, use [subscription access responses](../planner5d-native-app/references/subscription-access.md). Explain the required plan and link to [Planner 5D pricing](https://planner5d.com/pricing). Keep subscription-state errors, credit limits and technical failures separate.\n\nOpen the intended project through the app's navigation, then read `editorGetContext`. Load `editorPrepareAIRender`, `editorGenerateAIRender` and `editorGetAIRenderStatus`. Their typed schemas define preparation, generation and status recovery.\n\nFor the person's specific furniture, first complete `planner5d-model-import` and verify its native placement, real scale and readiness. For PDF/plan → AI render, complete `planner5d-floorplan-recheck` and the requested furnishing before capture. Reuse the existing project and verify the source before rendering; do not silently substitute a catalog lookalike. If a furnished interior is requested, an empty plan does not fulfill it. An explicit architecture-only/render-only brief preserves that narrower scope. When comparing product/finish variants, preserve verified geometry and a consistent source camera unless the person asks for different views.\n\n1. Choose the view with native 3D preview/camera controls and inspect the actual image. Ensure needed models and materials are loaded. For camera information, request `includeCamera:true` only when the editor is already in 3D.\n2. Call `editorPrepareAIRender` with the actual expected project hash and a stable request ID. Preparation persists native pixels and returns the signed price/quote; it does not submit conventional scene geometry to the server renderer.\n3. Describe the requested appearance using source evidence. Preserve wall/opening locations, furniture proportions, dark material texture, glass/mirror behavior and visible structural features. Describe enabled lighting and its observed positions; do not invent extra fixtures or alter the layout to improve a picture.\n4. Call `editorGenerateAIRender` only under the user's authorized credit budget, passing the prepared quote and explicit maximum credits required by the live schema. Native permissions and billing decide eligibility and charges.\n5. Call `editorGetAIRenderStatus` for the existing generation using its returned identity. Check completion, saved output, visual fidelity and the accessible image. A retry must recover the previous request before creating another charged generation.\n\nUse native screenshots/previews for source verification. Keep credentials, signed upload/download tokens and one-use login tickets out of user-facing output. Return the verified render and project link, with any visible fidelity differences. An AI image does not certify room measurements or a construction drawing.\n\nAfter the original job succeeds, use `show_planner5d_ai_render` with that requestId and current project/panel/document context. Show the real render in chat and compare it with the captured scene. The presentation step reads the completed original and does not generate, charge or change the scene. Keep host preview and original-file download outcomes separate.\n"
Full snapshot data
{
"description": "Generate or refine a photorealistic AI image from a native Planner 5D scene screenshot while preserving geometry, materials and visible lighting. Use the editor's quoted screenshot-to-AI workflow.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 381
}
],
"name": "planner5d-ai-render",
"skill_md_contents": "---\nname: planner5d-ai-render\ndescription: Generate or refine a photorealistic AI image from a native Planner 5D scene screenshot while preserving geometry, materials and visible lighting. Use the editor's quoted screenshot-to-AI workflow.\n---\n\n# Planner 5D AI rendering\n\nFor a subscription denial, use [subscription access responses](../planner5d-native-app/references/subscription-access.md). Explain the required plan and link to [Planner 5D pricing](https://planner5d.com/pricing). Keep subscription-state errors, credit limits and technical failures separate.\n\nOpen the intended project through the app's navigation, then read `editorGetContext`. Load `editorPrepareAIRender`, `editorGenerateAIRender` and `editorGetAIRenderStatus`. Their typed schemas define preparation, generation and status recovery.\n\nFor the person's specific furniture, first complete `planner5d-model-import` and verify its native placement, real scale and readiness. For PDF/plan → AI render, complete `planner5d-floorplan-recheck` and the requested furnishing before capture. Reuse the existing project and verify the source before rendering; do not silently substitute a catalog lookalike. If a furnished interior is requested, an empty plan does not fulfill it. An explicit architecture-only/render-only brief preserves that narrower scope. When comparing product/finish variants, preserve verified geometry and a consistent source camera unless the person asks for different views.\n\n1. Choose the view with native 3D preview/camera controls and inspect the actual image. Ensure needed models and materials are loaded. For camera information, request `includeCamera:true` only when the editor is already in 3D.\n2. Call `editorPrepareAIRender` with the actual expected project hash and a stable request ID. Preparation persists native pixels and returns the signed price/quote; it does not submit conventional scene geometry to the server renderer.\n3. Describe the requested appearance using source evidence. Preserve wall/opening locations, furniture proportions, dark material texture, glass/mirror behavior and visible structural features. Describe enabled lighting and its observed positions; do not invent extra fixtures or alter the layout to improve a picture.\n4. Call `editorGenerateAIRender` only under the user's authorized credit budget, passing the prepared quote and explicit maximum credits required by the live schema. Native permissions and billing decide eligibility and charges.\n5. Call `editorGetAIRenderStatus` for the existing generation using its returned identity. Check completion, saved output, visual fidelity and the accessible image. A retry must recover the previous request before creating another charged generation.\n\nUse native screenshots/previews for source verification. Keep credentials, signed upload/download tokens and one-use login tickets out of user-facing output. Return the verified render and project link, with any visible fidelity differences. An AI image does not certify room measurements or a construction drawing.\n\nAfter the original job succeeds, use `show_planner5d_ai_render` with that requestId and current project/panel/document context. Show the real render in chat and compare it with the captured scene. The presentation step reads the completed original and does not generate, charge or change the scene. Keep host preview and original-file download outcomes separate.\n"
}SHA-256 of public snapshot: e287a20ddfb77abcb874fe9e0af322e389501995321390118fff1d58b1fe7505