skills.rest
ProLeadAppt
ProLeadApptCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

vanity-engineering-review

Detect vanity engineering patterns and output a Vanity Score with kill criteria.

Updated Mar 23, 2026
Search Tags:#architecture#governance#complexity#engineering#detection#code-review#vanity
One-click install
npx skills add https://github.com/ProLeadAppt/doggroomerdemo --skill vanity-engineering-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vanity-engineering-review
Source: https://github.com/ProLeadAppt/doggroomerdemo/tree/main/.agents/skills/bencium-vanity-engineering-review
Command: npx skills add https://github.com/ProLeadAppt/doggroomerdemo --skill vanity-engineering-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vanity engineering adds complexity that doesn't translate to user value; it hinders maintainability and delivery speed.

Core Features & Use Cases

  • Phase 1: Establish the Requirement Anchor to define what the system actually needs.
  • Phase 2: Detection Scan against patterns in references/detection-patterns.md and score findings with Vanity Severity.
  • Phase 3: Vanity Score and Phase 4: Kill Criteria Generation to codify when to stop vanity efforts.

Quick Start

Run a vanity-engineering review on a chosen codebase to surface non-value-added complexity and propose concrete simplifications.

Frequently Asked Questions about vanity-engineering-review

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

FAQPage Schema
What is vanity engineering and how does it add unnecessary complexity to a codebase?▼

Vanity engineering adds complexity that hinders maintainability and delivery speed without translating to user value. Identifying these patterns in a codebase surfaces unnecessary architecture and simplifies technology decisions.

How do I detect vanity engineering patterns in a pull request or architecture proposal?▼

Apply a vanity engineering review to establish a requirement anchor, scan against detection patterns, and generate a vanity score. This identifies unnecessary complexity in PRs, RFCs, and architecture proposals.

Can I use a vanity engineering review on RFCs and technology decisions?▼

Yes, you can apply a vanity engineering review to RFCs and technology decisions. It determines whether proposed complexity aligns with actual requirements by enforcing a requirement anchor and scoring findings against detection patterns.

How do I establish kill criteria to stop unnecessary engineering efforts?▼

Run a vanity engineering review to generate a kill-criteria framework. This codifies exactly when to stop vanity efforts by scoring the severity of detected complexity patterns against actual system requirements.

What is the best way to score code complexity against actual requirements?▼

The best way to score code complexity is using a vanity engineering review. It establishes a requirement anchor, applies a detection scan, and outputs a vanity score to determine if complexity aligns with actual needs.

When should I not use a vanity engineering review approach?▼

Avoid a vanity engineering review when a codebase lacks defined actual requirements. The review depends on a Phase 1 requirement anchor to effectively score complexity and generate kill criteria.

Related Skills

Explore More Software Engineering Skills→
Doyajin174Doyajin174
1

planning

Convert vague ideas into structured plans with tasks and file paths.

Community
Intermediate
nachopalmerinachopalmeri

distill

Remove unnecessary complexity from design systems and UI mockups.

Community
Advanced
linardsblinardsb

launch-governance

Manage launch governance with kill gates, portfolio reviews, and decision logging.

Community
Advanced
StudentCristianStudentCristian

nw-sar-critique-dimensions

Evaluate architecture decision records against a predefined critique framework.

Community
Advanced