Dobby Artifacts

Purpose

Use this skill when a Dobby workspace needs a visible, reusable working surface that the user and Dobby can both open, revisit, and improve.

A Dobby artifact is not just a temporary preview and not just documentation. It is a workspace-owned surface: for example an HTML worksheet, tracker, dashboard, table, calculator, map, timeline, or visual report backed by whatever local data pattern best fits the job.

Ownership Rules

• Work from the current Dobby workspace (~/GitHub/adi or ~/GitHub/angie) unless the user explicitly names another workspace.
• Keep person-private artifact content in that person's workspace.
• Put shared serving, dashboard listing, routing, or engine behavior in ~/GitHub/dobby-engine.
• Put skill/control-plane changes in ~/GitHub/agents.
• Do not use ~/GitHub/scripts for artifact behavior unless the change is truly machine-local service plumbing.
• Keep the implementation workspace-agnostic. Do not hardcode Angie or Adi unless the artifact content itself is personal.

When an Artifact Is the Right Shape