Diagnose Contentstack preview issues with AI
Work from the onboarding result and one redacted request to find why an editor sees a blank frame, stale content or an uneditable field.
Diagnose Contentstack preview issues with AI when an editor changes a headline but still sees the published version in the preview pane. The cms-live-preview-visual-editor-support-assistant skill starts with what the deployed preview actually reports and narrows the problem to a particular step. A configuration file can show intent while a redacted request reveals the host that really served the page.
If the problem affects only one language or one route, that detail can save considerable work. It helps the agent distinguish a locale mismatch from a failing connection, missing edit markers or cached content.
What it does
- Read the onboarding check before proposing configuration changes.
- Identify whether an affected page uses client or server rendering.
- Compare the preview host and locale with the content requested.
- Inspect edit markers for a visible field that cannot be selected.
- Prepare a focused verification using redacted evidence.
Install and use
- Provide an authorised preview or sanitised screenshots and request details. Keep token values, cookies and private draft contents out of shared diagnostics.
- Ask, “English headlines stay stale while the other locale updates. Which single request would distinguish a locale issue from a cached response?”
- Test the proposed change only in the intended preview environment, then repeat the original edit.
FAQ
Source
Made by Contentstack. Original skill: cms-live-preview-visual-editor-support-assistant, published on GitHub under the MIT licence.
View on GitHub