explaingit

eplecheck/vibecheck

Analysis updated 2026-05-18

1AstroAudience · vibe coderComplexity · 3/5LicenseSetup · moderate

TLDR

A headless CMS you edit by chatting with an AI: describe a change in plain language and the system validates, commits, and redeploys the site automatically.

Mindmap

mindmap
  root((VibeCheck))
    How it works
      Chat with Claude
      Schema validation
      Git commit
      Auto redeploy
    Architecture
      Schema package
      Astro site
      MCP server
    Content Types
      Hero sections
      Pricing tables
      Feature grids
      Forms
    Deployment
      Vercel
      Netlify
      Cloudflare Pages
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Build and update a static marketing site by chatting with Claude instead of using an admin dashboard.

USE CASE 2

Add a full landing page with hero, pricing, and FAQ sections by typing one prompt to an AI agent.

USE CASE 3

Let non-technical team members update website content safely without risking broken builds.

USE CASE 4

Self-host a schema-validated CMS that stores all content in a reviewable Git history.

What is it built with?

AstroTypeScriptZodMCPGitHub APIDocker

How does it compare?

eplecheck/vibecheckyorukot/blosgaandreicristi88/vexyn
Stars119
LanguageAstroAstroAstro
Last pushed2025-07-10
MaintenanceQuiet
Setup difficultymoderateeasyeasy
Complexity3/52/51/5
Audiencevibe coderpm foundergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires a GitHub token and repo name in .env for the MCP server, Vercel deployment needs Root Directory set to apps/site.

MIT license: use, modify, and distribute freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

VibeCheck is a content management system, or CMS, that you operate by chatting with an AI assistant instead of clicking through an admin panel. The idea is straightforward: you type a sentence describing what you want on your website, the system translates that into validated content, commits it to a GitHub repository, and the site redeploys automatically. The whole cycle takes about 30 seconds. The system is built as a monorepo with three parts. One package defines a schema, meaning a set of rules describing what content can look like. A second package is an Astro-based website that reads content files and builds static HTML pages. A third package is an MCP server, a type of connector that lets Claude access tools to create, update, or delete pages. Because the site and the MCP server share the same schema, any edit the AI attempts is validated before it lands in the repo. If the content would break the site, the change fails without affecting the live pages. Content is stored as YAML files rather than raw HTML. Pages are made up of typed sections: heroes, feature grids, pricing tables, call-to-action banners, forms, and a single richtext section type for situations where HTML is needed. Keeping most content in typed data means AI-generated edits cannot accidentally introduce broken markup. There are two ways to use VibeCheck. If you run Claude Code locally with the repo open, you can ask Claude to edit pages directly and the schema validates at build time. If you run the MCP server, you can connect to it from claude.ai or the Claude desktop app and edit the live site from anywhere. Publish modes let you either open a pull request for review or commit directly to the default branch. The project deploys as static output to Vercel, Netlify, or Cloudflare Pages. A public live demo lets visitors try editing the site themselves. The project is MIT-licensed.

Copy-paste prompts

Prompt 1
I've cloned VibeCheck and deployed the Astro site to Vercel. Now I want to connect the MCP server so I can edit from claude.ai. Walk me through setting up the .env file and starting the MCP server.
Prompt 2
Using the VibeCheck MCP connected to Claude, create a pricing page with three tiers: Starter ($9/mo), Pro ($29/mo), and Scale ($99/mo), each with four feature bullets. Publish directly.
Prompt 3
Explain how VibeCheck's schema validation prevents an AI from breaking the site build, and show me where the schema is defined in the codebase.
Prompt 4
I want to add a new section type to VibeCheck for a testimonials block with author name, quote, and star rating. Where do I add it in the schema package and how does it flow to the site renderer?

Frequently asked questions

What is vibecheck?

A headless CMS you edit by chatting with an AI: describe a change in plain language and the system validates, commits, and redeploys the site automatically.

What language is vibecheck written in?

Mainly Astro. The stack also includes Astro, TypeScript, Zod.

What license does vibecheck use?

MIT license: use, modify, and distribute freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is vibecheck to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is vibecheck for?

Mainly vibe coder.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub eplecheck on gitmyhub

Verify against the repo before relying on details.