claude-code-builder

Build and deploy single-file web artifacts to Vercel via the BLAST protocol.

Updated May 16, 2026
One-click install
npx skills add https://github.com/jaredcroxton/hermes-mirror --skill claude-code-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-builder
Source: https://github.com/jaredcroxton/hermes-mirror/tree/main/agents/skills/software-development/claude-code-builder
Command: npx skills add https://github.com/jaredcroxton/hermes-mirror --skill claude-code-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of turning a user’s build and deploy request into a live, public web artifact with the right stack and prerequisites, without drifting or skipping workflow phases.

Core Features & Use Cases

  • BLAST Build Orchestration: Runs the fixed phases Blueprint, Link, Architect, Stylize, Trigger and reports status using the required phase names.
  • Provider-Aware Build Execution: Verifies which reasoning/build engine is active for Bob’s profile before choosing Claude Code versus Codex-style workflows, preventing incorrect tool usage.
  • GitHub Source of Truth + Vercel Production URL: Creates or updates a GitHub repo, then deploys via the Vercel CLI and returns the live vercel.app URL on success.
  • Common Artifact Targets: Dashboards, decks, static tools, calculators, training/onboarding pages, briefing docs, and PerformOS website pages.
  • Auth & Prerequisite Guardrails: Checks vercel whoami, gh auth status, and profile-isolated auth for the build profile before proceeding.

Quick Start

Use this skill when the user says they want a dashboard or page built and deployed to Vercel, and ensure the build includes both a GitHub push and a final live URL.

Frequently Asked Questions about claude-code-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and deploy a single-file HTML dashboard to Vercel?

To build and deploy a single-file HTML dashboard to Vercel, this Skill orchestrates a structured build brief through a five-phase protocol, pushes the monolithic artifact to a GitHub repository, and deploys it via the Vercel CLI to generate a live vercel.app URL.

Do I need GitHub and Vercel CLI authentication to deploy web artifacts?

Yes, you need GitHub and Vercel CLI authentication to deploy web artifacts. The Skill enforces prerequisite guardrails by checking `gh auth status` and `vercel whoami` to verify valid auth paths before proceeding with any repository creation or frontend build execution.

What is the BLAST protocol for frontend build orchestration?

The BLAST protocol for frontend build orchestration is a fixed five-phase workflow that stands for Blueprint, Link, Architect, Stylize, and Trigger. It ensures structured progression from initial dashboard or tool design through to the final Vercel deployment trigger without skipping phases.

Can I use this to build and deploy calculators and static tools?

Yes, you can use this to build and deploy calculators and static tools. The Skill handles common artifact targets including dashboards, decks, calculators, and static tools by compiling them into single-file web artifacts before pushing them to GitHub and deploying via Vercel.

What's the best way to automate GitHub pushes and Vercel deployment for web pages?

The best way to automate GitHub pushes and Vercel deployment for web pages is using an orchestration Skill that enforces a structured build protocol. It creates or updates a GitHub repo as the source of truth, then executes Vercel CLI deployment to return a live production URL.

Why does my web deployment require a single-file HTML artifact?

Your web deployment requires a single-file HTML artifact because the Skill enforces monolithic output rules. This constraint ensures the structured build brief produces a self-contained file that is easily validated and deployed directly through the Vercel CLI without external asset dependencies.