plugin official · Anthropic

project-artifact — Claude Code plugin: status pages and install

Q: How do I install project-artifact in Claude Code?

Add the marketplace with `/plugin marketplace add anthropics/claude-plugins-official`, then install the plugin with `/plugin install project-artifact@claude-plugins-official`.

Q: What is required to publish an artifact?

Claude Code needs its built-in `Artifact` tool and a claude.ai login. Publishing runs interactively; `gh` CLI is optional for projects organized around pull requests.

This plugin builds a living project status page and publishes it as a claude.ai artifact. Later refreshes reread project sources, keep the same URL, and report changes.

Install into Claude Code · Plugin marketplace All methods and platforms ↓

/plugin install project-artifact@claude-plugins-official
/plugin marketplace add anthropics/claude-plugins-official

Open on GitHub

What project-artifact does

project-artifact creates a self-contained HTML page with tabs for the project overview, success criteria, and workstream order. It can add next steps plus background, planning, risks, open questions, decisions, and FAQ when those sections help explain the project.

The plugin stores project configuration and the latest render in its local data directory. When you ask it to refresh the artifact, it gathers current state from the saved sources, redeploys the page at the existing URL, and returns a short change report. For pull-request workstreams, the optional gh CLI supplies live PR, CI, and review state while the page numbers the dependency sequence.

Publishing needs Claude Code’s built-in Artifact tool and a claude.ai login. Headless claude -p sessions cannot publish because they do not expose that tool; API key, Bedrock, and Vertex sessions have the same limitation.

What it helps with

assemble a project status page from repository and planning sources
show the dependency order between workstreams
publish a shareable status artifact for teammates
refresh the page without changing its URL
summarize changes since the previous render

Example prompts for the agent

Create a status page for this project from the repository, pull requests, and planning document.
Run /project-artifact and include success criteria, workstream order, and next steps.
Refresh the artifact and report only what changed since the last update.

How to install project-artifact

Plugin marketplace

/plugin install project-artifact@claude-plugins-official

/plugin marketplace add anthropics/claude-plugins-official

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about project-artifact

How do I install project-artifact in Claude Code?

Add the marketplace with /plugin marketplace add anthropics/claude-plugins-official, then install the plugin with /plugin install project-artifact@claude-plugins-official.

What does project-artifact do?

It builds and publishes a living project status page with an overview, success criteria, workstreams, and next steps. A later refresh uses the saved sources, updates the same URL, and reports the delta.

What is required to publish an artifact?

Claude Code needs its built-in Artifact tool and a claude.ai login. Publishing runs interactively; gh CLI is optional for projects organized around pull requests.

Source text

project-artifact · Apache-2.0

# project-artifact

Generate and publish a **living status page** for a project that's too big for one update —
a migration, a launch, a research effort, anything with several workstreams tracked over
time. The page is a single self-contained tabbed HTML file (overview & success criteria,
the workstream sequence, an always-visible "Next steps" strip, plus background / plan /
risks / FAQ tabs when they earn their place), published with Claude Code's built-in
`Artifact` tool to a private `claude.ai/code/artifact/...` page that you can share with
teammates.

## Usage

- **Create one:** run `/project-artifact` (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, a design doc.
It builds the page, publishes it, and tells you the URL.
- **Share it:** the page is private to you until you share it from the claude.ai viewer.
- **Keep it current:** say "refresh the artifact" in any later session. The plugin
remembers the project's sources and the published URL, re-gathers live state, redeploys
to the **same URL**, and replies with a short summary of what changed.

For software projects whose workstreams are pull requests, the page numbers the PR
sequence so the dependency order is obvious and pulls live PR/CI/review state via the
`gh` CLI.

## 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.
- Optional: the `gh` CLI, for PR-driven projects.

## Notes

- Per-project state (the config and the latest render) lives in the plugin's data
directory on your machine; the published artifact is the shareable copy.
- Artifact URLs are minted by the server. The plugin records yours after the first publish
so refreshes land on the same address — bookmark it or add it to your team's hub so
others can find it.
- Publishing needs an interactive session: headless (`claude -p`) runs don't have the
Artifact tool, so automation can build and update pages but the publish step happens
interactively.

discernment-nudge official anthropics This plugin adds two or three short follow-up questions after a substantive answer. Use it to check facts, probe reasoning, and spot missing context. ★ 183,839repo stars superpowers obra The plugin guides an agent from task discussion and planning through subagent development, code review, debugging, and TDD. Use it when the workflow matters. CX Codex ★ 305,248repo stars mattpocock-skills Matt Pocock A set of skills for grilling, TDD, code review, and specification work. Use it when an agent needs to clarify the task before changing the code. ★ 303,516repo stars claude-hud jarrodwatts Shows context usage, rate limits, running tools and todo progress under your input line. Useful when a session runs long and you want to watch the spend. ★ 28,841repo stars caveman JuliusBrussee A plugin that makes your agent answer shorter and read less of your logs, while code stays exact. One install, works with Claude and dozens more agents. ★ 115,125repo stars

From the same set123

The whole set →

ruby-lsp Connects the Ruby language server to Claude Code for code intelligence across .rb, .rake, .gemspec, .ru, and .erb files. ★ 44,635repo stars receipts Turns your Claude session transcripts into a report: what shipped, which projects it went to, and each project's share of usage. ★ 44,635repo stars ralph-loop Runs Claude on the same prompt over and over until the task is finished. Useful when the work needs retries: tests, debugging, building an API. ★ 44,635repo stars pyright-lsp Connects the Pyright language server to Claude Code for static type checking. Catches type mismatches in .py and .pyi files. ★ 44,635repo stars pr-review-toolkit Six subagents for pull request review: comments, tests, error handling, type design, code quality and simplification. ★ 44,635repo stars plugin-dev A developer toolkit with seven specialized skills and a guided workflow command for building Claude Code plugins, hooks, agents, and MCP integrations. ★ 44,635repo stars playwright This plugin lets Claude Code interact with web pages, fill forms, click elements, and take screenshots. Use it for browser automation and end-to-end testing. ★ 44,635repo stars playground Builds a single-file HTML playground with visual controls, a live preview and a prompt you can copy back into Claude. ★ 44,635repo stars