grimartifacts

# Artifacts ## What an artifact is A small interactive page generated by an agent: a visualization, a calculator, a mockup, a report, a game, a demo. The user opens it in a browser and it works. This skill is the standard for **artifacts** in general. If the artifact needs a live data layer that both the user and the agent can edit — persistent state, media review, two-way sync — that is a **Workbench Artifact**: a standardized, heavier pattern. Read `grim:dev:workbench-artifact` instead. ## The Standard Start minimal, and only escalate when the job demands it. **The minimal artifact — the default:** 1. **One self-contained `.html` file.** Inline the CSS and JS. No separate files, no folders. Opening it directly (`file://`) just works. 2. **No build step.** No bundlers, no frameworks that require compilation, no package.json. 3. **No dependencies by default.** Vanilla HTML/CSS/JS first. If a library genuinely earns its place (a chart, 3D, markdown rendering), load it from a CDN with a pinned version — never more than a couple. 4. **No network requirements at runtime** beyond those pinned CDN tags. The artifact should work on a plane. 5. **Readable source.** The user may open the file in an editor; keep it inspectable, commented where non-obvious, and small. **Escalate deliberately.** Artifacts can grow beyond the minimal form when they need to — a small local server (one Python or Node file), a couple of split-out files, a data file to read. Each addition must earn its p...