Vanity Engineering Review

This is a code review tool with a specific angle: it hunts for engineering decisions made to pad resumes or satisfy intellectual curiosity rather than solve actual user problems. Point it at a codebase, PR, or architecture doc and it scores what it calls the "requirement to complexity ratio," flags patterns like premature optimization and unnecessary abstraction, and estimates the ongoing maintenance cost of vanity decisions. The most useful output is probably the kill criteria framework, which forces teams to define upfront what would make a feature or system worth removing. Blunt and opinionated, but if you've ever inherited a microservice architecture built for 10 million users serving 500, you'll recognize what it's diagnosing.

skills.sh installs: 3.3K
GitHub stars: 491
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add bencium/bencium-marketplace --skill vanity-engineering-review --agent claude-code

Installs into .claude/skills of the current project.

Files

Vanity Engineering Review

A diagnostic skill that identifies code, architecture, and technical decisions built to impress rather than to ship. Vanity engineering is entropy disguised as craftsmanship — it increases complexity without proportional capability gain, and it compounds maintenance cost while delivering zero additional user value.

Core Premise

The only legitimate purpose of engineering is to solve a problem someone actually has.

Everything else — elegant abstractions nobody traverses, microservices that serve one endpoint, custom frameworks that replicate existing tools, type systems more complex than the domain they model — is vanity. It may feel productive. It is not.

This skill does not oppose quality, rigour, or good engineering. It opposes engineering that exists to satisfy the builder rather than the user.