Dokki can help create an Artifact from a description and refine it through follow-up instructions.
Start a new Artifact
Choose Create → Artifact.
Select a blank starting point or an Artifact template.
Describe the goal, audience, information to include, and important interactions.
Generate the first version, then review the preview before sharing or publishing.
Make a useful request
Be specific about the change and the reason. For example: “Move the key metric above the chart, add a date-range control, and keep the mobile layout to one column.” Small, testable requests are easier to review than a full redesign in one prompt.
Understand the states
Generating — Dokki is creating a new version.
Ready — the latest version can be previewed and edited.
Error — the request did not finish; review the message, adjust the request if needed, and try again.
Save as a template
When an Artifact is useful beyond the current task, open its settings and choose Save as template. Give it a name and description, and remove project-specific or sensitive information first.
Read live workspace data
Artifact code running inside Dokki can use the read-only window.dokki bridge:
const table = await window.dokki.readTable("<table-resource-id>")
const document = await window.dokki.readDocument("<document-resource-id>")Both the Artifact author and the current viewer must be allowed to read the target, and the target must be in the same workspace as the Artifact. The bridge supports document and table reads only, limits concurrent requests, and caps table output for rendering rather than bulk export.
Published Artifact snapshots cannot read live Dokki data. Design a public Artifact with frozen or embedded data, and handle a rejected live-data request rather than leaving the page waiting indefinitely.
Before publishing
Test every control and link.
Check desktop and narrow-screen layouts.
Confirm that the Artifact contains only information intended for public visitors.