Skip to content

Edit website artifact workflow

Change a website artifact you already have. Describe the change, preview each new revision, and keep it or discard it.

Updated View as Markdown

The Edit website artifact workflow changes one website artifact that already exists, such as one a Website artifact session built. Every change is stored as a new revision that you preview and then keep or discard. Its name is Edit website artifact (v1).

At a glance

  • Best for: Fixing, extending or restyling a website artifact
  • Project type: Any
  • Steps: Describe → Review, repeated as often as you need
  • Changes: The one artifact you started from. It writes no spec files and creates no new artifact.

Start a session

You do not pick this workflow in the chat picker. Start it from the artifact:

  • In the artifact viewer, open the newest revision and select Edit with AI.
  • Or select Edit with AI on the card that ends a Website artifact session.

The session edits that artifact and only that artifact. To edit another one, start another session from it. If someone stores a newer revision before your session starts, the AI edits the newest one and tells you so.

Steps

Describe

Say what to change, in plain language, for example “Add a contact page and link it from the header”. The AI can read the artifact’s text files, and the project’s spec files, attachments and other artifacts you reference with @.

Review

The AI writes the changed files and stores them as one new revision. While it writes, the chat shows a line for each file that updates until the file is written. The revision card shows the file count, the total size, the outside hosts the pages load from, and a preview you can expand. Choose:

  • Keep to keep the revision and describe the next change.
  • Discard to undo it. MySpec restores the revision before it by adding a new revision, so history is never lost. If someone stored another revision after it, Discard is refused, so their work is not undone.

When nothing is waiting for Keep or Discard, type /complete to finish.

The rules a site follows

The same rules apply as in a Website artifact session:

  • File types: The AI writes .html, .htm, .css, .js, .mjs, .json, .svg, .txt, .md, .xml and .webmanifest files. It keeps the other files of the artifact, images and fonts included, as they are.
  • Relative paths: Pages refer to their files with relative paths, never with a path that starts with /.
  • Third-party libraries: Pages can load scripts, styles and fonts from any CDN over https.
  • The preview: It has no origin of its own, so localStorage, sessionStorage, cookies and IndexedDB do not work in it.

Tips

  • One change per round. A small revision is quicker to check in the preview, and to discard if it is wrong.
  • Check the history. Every kept and discarded revision stays in the artifact’s history in the viewer. See Artifacts.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close