Vanity Engineering Review

bencium/bencium-claude-code-design-skill

This is a code review lens that asks the uncomfortable question: did you build this for users or for your LinkedIn profile? It scans codebases, PRs, and architecture docs for patterns like premature optimization, unnecessary abstractions, and resume-driven technology choices, then scores findings by severity and maintenance cost. The best part is the kill criteria framework it generates: hard rules for when to automatically delete features, review triggers that force you to justify keeping things, and soft-go metrics that make continuation something you have to earn rather than default into. Use it when evaluating refactors, reviewing architectures, or auditing why your three-person startup has a microservices mesh.

skills.sh installs: 236
GitHub stars: 267
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add bencium/bencium-claude-code-design-skill --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.