project-judge

Reviews vibe-coded projects against a weighted rubric and hard gates, emitting structured verdicts.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill project-judge-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-judge
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/software-development/project-judge
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill project-judge-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated projects often ship with generic design patterns, broken builds, or fabricated results, and there is no objective gatekeeper deciding whether a project is actually done. This Skill acts as a strict design and engineering reviewer that blocks completion until quality standards are met. ## Core Features & Use Cases - Weighted Rubric Scoring: Scores six dimensions including frontend design (35%), engineering craft (20%), and functionality (15%), requiring a weighted total of 8.5/10 and frontend score of 9/10 for approval. - Hard Gates: Automatically rejects projects with failing builds, three or more compositional slop tells (centered layouts, gradient heroes, default Inter font), neon colors, or fabricated placeholder results. - Structured Verdict Loop: Emits a VERDICT schema with P0/P1 punchlist items referencing exact files and lines, plus recommended skills and MCPs, so a builder agent can iterate until approved. - Use Case: An orchestrator agent finishes a landing page and submits it for review; the judge opens it in Playwright, pulls computed styles, runs a slop scan, and returns REVISION with concrete fixes until the design passes. ## Quick Start Judge the project in the current directory against the stated goal and emit a verdict with a punchlist.

Frequently Asked Questions about project-judge

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

FAQPage Schema
How do I review AI-generated frontend code for design quality?▼

Submit the project path, stated goal, and constraints to the judge, which scores six weighted dimensions with frontend design at 35%. It verifies actual rendering in Playwright rather than trusting code inspection alone.

What is the approval bar for the project judge verdict?▼

Approval requires a weighted total of at least 8.5/10, a frontend design score of at least 9/10, and zero hard-gate failures. Anything below that returns REVISION with a prioritized punchlist.

What design patterns cause automatic rejection?▼

Hard gates fail on three or more slop tells such as centered-everything layouts, gradient heroes, default Inter font, emoji icons, and identical border-radius everywhere. Any neon color or glow is an automatic fail regardless of count.

Does the project judge verify builds and rendering?▼

Yes, it runs builds and typechecks when available and opens web projects in Playwright to pull computed styles like fonts, shadows, and focus outlines. Claiming completion without an actual render check is a hard-gate failure.

How does the builder-reviewer revision loop work?▼

The builder submits the project, the judge emits APPROVED or REVISION with a P0/P1 punchlist, and the builder applies fixes and resubmits. The loop repeats until the judge approves, and the project never completes otherwise.