project-artifactlisted

Generate and publish a project status artifact — an opinionated, tabbed status page for a project too big for one update (overview & success criteria, the workstream sequence, next steps, plus background, plan, risks & open questions, and decisions/FAQ when they earn a tab) — published with the built-in Artifact tool to a default-private claude.ai page the user can share with teammates. Use when a piece of work spans several workstreams and you want a shareable overview kept current. Each artifact is backed by a small per-project config in the plugin data dir, so refreshing it re-gathers live state, redeploys the same URL, and reports only the delta. For software projects whose workstreams are PRs, also read swe.md (the X.Y PR-numbering convention; pulling PR state with gh/git; a per-PR detail block). Needs the built-in Artifact tool (claude.ai login). Not for single-PR changes or public docs.
mrkhachaturov/ccode-personal-plugins · ★ 0 · Data & Documents · score 65

Install: claude install-skill mrkhachaturov/ccode-personal-plugins

# 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