What it is
project-artifact generates and publishes a "living status page" for a project that's too big for one update. The README gives a migration, a launch, or a research effort as examples, meaning anything with several workstreams tracked over time. The page is a single self-contained tabbed HTML file. It always includes an overview with success criteria, the workstream sequence, and an always-visible "Next steps" strip. Background, plan, risks and open questions, and decisions/FAQ tabs are added only when they earn their place. The page is published with Claude Code's built-in Artifact tool to a private claude.ai/code/artifact/... page. It stays private to you until you share it from the claude.ai viewer. Artifact URLs are minted by the server, and the plugin records yours after the first publish so later refreshes land on the same address. Each artifact is backed by a per-project config. The config and the latest render live in the plugin's data directory on your machine, while the published artifact is the shareable copy. When you say "refresh the artifact" in a later session, the plugin: - remembers the project's sources and the published URL - re-gathers live state - redeploys to the same URL - replies with a short summary of what changed The plugin is domain-neutral but has a software specialization. For projects whose workstreams are pull requests, the page numbers the PR sequence so the dependency order is obvious. It also pulls live PR, CI and review state via the gh CLI.
Who it's for
- Teams running large projects with several workstreams tracked over time, such as migrations, launches, or research efforts
- People who want a shareable status page for teammates that stays up to date at a stable URL
- Software teams whose workstreams are pull requests and who want live PR/CI/review state on the page
- Claude Code users on Team or Enterprise plans with a claude.ai login
Requirements
Requirements
- Claude Code's built-in Artifact tool, which requires a claude.ai login (sessions on an API key, Bedrock, or Vertex don't have it)
- Claude Code Artifacts are available in beta on Team and Enterprise plans
- An interactive session for publishing (headless
claude -pruns don't have the Artifact tool) - Optional: the
ghCLI, for PR-driven projects
بلَغِن لـ Claude Code بيعمل صفحة حالة لمشروعك الكبير، صفحة HTML فيها تابات، وبينشرها بأداة Artifact على صفحة خاصة بـ claude.ai فيك تشاركها مع فريقك. وكل ما بدك تحدّثها بتقول "refresh the artifact" وبيرجع ينشرها على نفس الرابط.
Examples
Create a status page
text/project-artifactWhat it does: Run the command, or just ask for a status page for your project, and point it at the project's sources: the repo and its PRs, a tracker, or a design doc. It builds the page, publishes it, and tells you the URL.
Refresh an existing status page
Promptrefresh the artifactExpected output: Say this in any later session. The plugin re-gathers live state from the remembered sources, redeploys to the same URL, and replies with a short summary of what changed.