Skip to content

fix(prompts): align quality-evaluator.md with new VQ-01 + proportional rules#7392

Merged
MarkusNeusinger merged 1 commit into
mainfrom
style/quality-evaluator-align
May 19, 2026
Merged

fix(prompts): align quality-evaluator.md with new VQ-01 + proportional rules#7392
MarkusNeusinger merged 1 commit into
mainfrom
style/quality-evaluator-align

Conversation

@MarkusNeusinger
Copy link
Copy Markdown
Owner

Summary

quality-evaluator.md is the standalone/offline reviewer (not workflow-active — ai-quality-review.md is what `impl-review.yml` actually invokes). After #7391's wording changes the two prompts drifted on VQ-01.

Changes

  • Header note clarifies role + points to ai-quality-review.md as the authoritative source on contradiction
  • VQ-01 row: dropped "(not defaults)" constraint, added mobile-readability check
  • VQ-05 row: added title-width / overflow guidance
  • New "Proportional sizing notes" block matches default-style-guide.md + ai-quality-review.md Section 5d + quality-criteria.md VQ-01

Test plan

  • CI green

🤖 Generated with Claude Code

…l rules

quality-evaluator.md is the standalone/offline reviewer (NOT workflow-active —
ai-quality-review.md is what impl-review.yml actually invokes). The two
prompts had drifted: quality-evaluator.md still demanded "Font sizes
explicitly set (not defaults)" while quality-criteria.md (just updated in
#7391) now says source-of-values is irrelevant and only the visual result
matters.

Changes:
- Header note clarifies the file's standalone role and points to
  ai-quality-review.md as the authoritative workflow-active reviewer
  when the two contradict.
- VQ-01 row: dropped the "(not defaults)" constraint, added mobile-
  readability check.
- VQ-05 row: added title-width / overflow guidance.
- New "Proportional sizing notes" block under the Visual Quality table:
  matches the rules in default-style-guide.md, ai-quality-review.md
  Section 5d, and quality-criteria.md VQ-01 — including the mandated-
  long-title exception and the "source-of-values irrelevant" principle.
Copilot AI review requested due to automatic review settings May 19, 2026 12:56
@MarkusNeusinger MarkusNeusinger enabled auto-merge (squash) May 19, 2026 12:56
@MarkusNeusinger MarkusNeusinger merged commit 330081c into main May 19, 2026
8 checks passed
@MarkusNeusinger MarkusNeusinger deleted the style/quality-evaluator-align branch May 19, 2026 12:56
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Aligns the standalone quality-evaluator.md reviewer prompt with the wording changes made to the workflow-active ai-quality-review.md in #7391, so the two rubrics no longer drift on VQ-01 / VQ-05 and proportional sizing.

Changes:

  • Adds a header note clarifying that ai-quality-review.md is authoritative when the two prompts disagree.
  • Updates VQ-01 (drops "not defaults", adds mobile readability) and VQ-05 (title width / overflow guidance).
  • Adds a "Proportional sizing notes" block matching the style guide and the workflow reviewer.

MarkusNeusinger added a commit that referenced this pull request May 19, 2026
…w VQ-01 philosophy (#7393)

## Summary
After #7391/#7392 changed the VQ-01 rubric (source-of-values irrelevant;
defaults vs AI-tuned score equally), the example JSON output and example
weaknesses in \`quality-evaluator.md\` were still showing the OLD
philosophy:

- \`vq01_text_legibility\` example note: \"Readable but relying on
defaults (font sizes not explicitly set)\" → \"Title slightly oversized
for content...\"
- \`weaknesses[0]\`: \"Relying on default font sizes instead of explicit
settings\" → \"Title at fontsize=18pt squeezes against the right edge\"

These examples are the most concrete guidance for the reviewer; if they
show old reasoning, the reviewer follows old reasoning regardless of
what the rubric tables say.

## Test plan
- [ ] CI green

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants