Design Assets
Save, iterate on, and share reusable HTML design mockups across your organization
Design assets are persistent, reusable HTML design artifacts owned by your organization. They live in the dashboard under Design Assets (currently Beta) and appear as clickable cards in chat when an agent references them.
Each asset has a title, a URL slug, HTML content, a rendered PNG thumbnail, and a draft or published status. An asset can be linked to a specific project or left project-agnostic so you can reuse it across projects.
Creating design assets
You can create a design asset in four ways:
From an HTML preview in chat
Ask Starcat Developer to mock something up. When the agent renders an HTML preview in chat, click the palette icon on the preview toolbar, enter a title, and save.
From a saved project preview
Open your project's Previews tab in settings. On any preview card, click the palette icon. The asset is created with the preview's title and HTML content.
From the dashboard
Go to Design Assets and click New asset. Enter a title and initial HTML, then open the asset to edit further.
Via the agent or MCP
An agent with write access can call save_design_asset directly in chat or through an external
MCP client connected to your organization.
Viewing and editing
Open an asset from the grid to edit its HTML and title, preview at Desktop (1280px), Tablet (768px), or Mobile (390px), and regenerate or download the PNG thumbnail. Regenerate uses the last saved content, so save first.
Agents update an asset with save_design_asset (existing slug) for full rewrites, or edit_design_asset for small find-and-replace edits after fetching it with get_design_asset.
Publishing and sharing
Assets start as draft. Only published assets are reachable on the public share page at https://www.stardeck.ai/assets/<slug>.
On the asset detail page, click Publish to make the share link available. Click Unpublish to return it to draft; the public page will no longer load it.
When published, configure Share view settings:
| Setting | What it controls |
|---|---|
| Sizes | Which viewport widths visitors can toggle on the public page (Desktop 1280px, Tablet 768px, Mobile 390px). At least one size must stay selected. |
| Display | How visitors see the asset: Live preview (interactive HTML), Live + image toggle (switch between live HTML and the PNG), or Image only (static thumbnail). |
Copy the share link from the detail page, or download the PNG thumbnail for decks, docs, and other contexts outside Stardeck.
Agent and MCP access
Design asset tools are org-level and gated by two permission keys in Settings → Roles & Permissions:
| Permission | Tools |
|---|---|
agent:design-assets:read | list_design_assets, get_design_asset |
agent:design-assets:write | save_design_asset, edit_design_asset (also requires read) |
Read tools
list_design_assets: list saved assets (slug, title, status, thumbnail, share URL, and optional project link, not full HTML content). Pass an optionalprojectIdto list that project's assets plus project-agnostic ones.get_design_asset: fetch a single asset by slug, including full HTML content.
Write tools
save_design_asset: create a new asset or update an existing one by slug.edit_design_asset: apply a targeted find-and-replace edit to stored content.
There is intentionally no delete tool. Deleting an asset is dashboard-only (Delete on the asset detail page).
In-chat rich cards
When an agent saves or references an asset in Stardeck chat, it can render a clickable card using a fenced code block with language design-asset and the asset's slug as the content:
```design-asset
my-dashboard-mock-a1b2c3
```The card shows the thumbnail, title, and status. Click it to open a live preview dialog, jump to the asset in the dashboard, or copy the public share link (when published).
Using assets in chat
You can hand an asset to an agent directly from the chat input. Click the + button and choose Design Assets to browse your library, search by title or slug, and pick one. The selection appears as a removable chip above the input, and when you send the message the agent receives a reference to the asset (your sent message shows it as a rich card).
In a project's developer chat, this is how you turn a design into a build: attach the asset (or just mention it by name) and ask the agent to implement it. The agent fetches the asset's HTML and treats it as the design spec. If you ask for changes to the design itself, the agent can also update the saved asset in place.
Design assets are org-wide. When an agent edits a saved asset from inside one project, the change is visible everywhere the asset is used.