project-artifact

# project-artifact — an opinionated project status page This skill produces one specific *kind* of artifact: a tabbed status page that represents a project too big for one update — a software migration, a research effort, a launch, an org initiative; anything with a set of parallel/dependent workstreams tracked over time. It generates the HTML (one file, self-contained — the Artifact CSP blocks all external hosts, so everything is inlined; the only `<script>` is the tab switcher) and publishes it with the built-in `Artifact` tool to `https://claude.ai/code/artifact/<uuid>`. The page is default-private; the viewer gives the owner a version picker and lets them share it with teammates. (The general "render any HTML/Markdown to a web page" capability is the built-in `Artifact` tool; this is the project-tracker structure on top — defining what an artifact *is* belongs to that tool, not here.) The SWE specifics for PR-driven projects are in `swe.md`, kept out of this file so the project-artifact structure stays domain-neutral. ## Workflow 1. **Resolve the artifact config, then locate the project.** Each project gets a directory at `${CLAUDE_PLUGIN_DATA}/artifacts/<slug>/` holding `config.md` (see **"The artifact config"** below) and `page.html` (the current render); listing `artifacts/` is the registry of this skill's artifacts on this machine. If the user names a project, load that slug; if exactly one config matches the session (its repo is the cwd, or its ...