VibeSpec Score 30: Subjective Language

A score of 30 highlights wording that expresses personal taste or opinion. Subjective requirements are difficult to validate because they hinge on individual interpretation.

Example requirements

1. “The dashboard must have a gorgeous design that users love.”
   • Designer interpretation: Requires intricate visuals and animations.
   • Developer interpretation: Could simply mean clean layouts.
   • Fix: “Follow our design system and achieve a satisfaction rating over 85% in user tests.”
2. “The tool should feel modern and stylish.”
   • Designer interpretation: Favors bold colors and animations.
   • Engineer interpretation: May equate modern with minimalism.
   • Fix: “Implement the latest UI theme with responsive layouts.”
3. “The app must be extremely easy to use.”
   • Designer interpretation: Requires tutorials and onboarding flows.
   • Developer interpretation: Possibly just fewer menus.
   • Fix: “New users should complete the first task in under two minutes without guidance.”

How VibeSpec detects and explains

VibeSpec points out adjectives like “gorgeous” or “amazing” and recommends focusing on measurable criteria instead. It may suggest referencing design guidelines or user studies to back up claims.

Why interpretations differ

A designer might interpret “gorgeous” as requiring advanced visuals and animations, while a developer may equate it with simple, clean layouts. By calling out these subjective terms, VibeSpec encourages the team to specify concrete design goals or usability metrics.