sitewarming-template-tools

sitewarming-template-tools

A Claude Code plugin that lets anyone on the team turn a customer's design.md into a delivered, org-private astro template — no MCP server, no DB access, no manual API calls. Just paste the design.md and run the skill.

It replaces the old sitewarming-template-mcp stdio server. The skill drives the same flow (author 3 .astro files → scaffold → patch registry → build check → register + deliver via the worker admin API) using Claude Code's built-in file/bash tools, so there's nothing to install per machine beyond this plugin.

Install (one time, per teammate)

# Add this repo as a marketplace
/plugin marketplace add /abs/path/to/sitewarming-template-skill

# Install the plugin
/plugin install sitewarming-template-tools@sitewarming-template-tools

(Or point the marketplace at the git remote once this is pushed.)

Configure (one time, per teammate)

Create .claude/sitewarming-template-tools.local.md with the worker URL, the TEMPLATE_MCP_API_KEY, and the absolute path to your astro-warming-template checkout. See skills/build-custom-template/references/settings-template.md for the exact format. This file is gitignored — it holds a secret.

Use

Paste the customer's design.md into Claude Code and say something like "build the custom template for this org". The skill asks for the org id, the approved request id, and a slug, then does the rest. At the end it tells you to commit + deploy the astro repo to make the template live.

Worker dependency

The skill talks to two existing worker admin endpoints, authenticated with the X-Template-MCP-Key header:

• POST /api/admin/astro-templates
• POST /api/admin/custom-template-requests/:id/mark-delivered

That auth path (sitewarming-worker/src/middleware/auth/templateMcpAuth.ts) must stay in place — it's what lets the skill act as a template-delivery admin without a Clerk login.