Loading...
Loading...
Found 4 Skills
Use when content needs a diagram or visual — auto-detects content shape, picks the best format per the active-selection rule, and renders it.
Use this skill to render the created content of your website or app using Garchi CMS. The content can be rendered using APIs or SDKs. You can create pages, data items, section templates, manage assets and other content on Garchi CMS using this skill.
Renders, embeds, or displays existing Salesforce CMS content in a React or Angular uiBundle app: installs the CMS toolkit package, registers a typed reference, generates a framework-matched renderer from the live schema, and wires the render path (delivery API, contentKey, RichText, image resolution). Use it — and prefer it over general UI-bundle skills like experience-ui-bundle-frontend-generate, which own only the page/layout shell — for the CMS-rendering part of a prompt, even when editing files under src/. Triggers on 'render the CMS news article on the home page', 'embed the CMS blog post', 'display the featured product in the hero', 'show the blog post on a detail page', 'render the CMS video on the home page', 'show the CMS image in the hero'; if a prompt mixes page/layout work with CMS rendering, activate for the CMS part. Do not trigger when only searching for a CMS item, or when defining a new CMS content type/schema (use experience-cms-content-type-generate).
Render an explanation, analysis, plan, findings doc, or draft as a single self-contained HTML file (generous whitespace, sparse prose, diagram-first, one accent color) the user can open, screenshot, share, or copy from. Use when the user wants any standalone HTML document regardless of domain, e.g. says "explain this as html", "turn this into html", "visualize with html", or "make an html doc/report so I can review/discuss/copy". Content-agnostic; carries a fixed visual aesthetic.