ring/dev-team/skills/shared-patterns/anti-rationalization-visual-report.md
Jefferson Rodrigues 8c110bd2fa
fix(skills): fix broken relative links, lexical salience, and output schema
Fix broken relative paths for anti-rationalization-visual-report.md in dev-cycle-frontend (../../dev-team/ to ../), production-readiness-audit and requesting-code-review (../../ to ../../../). Apply lexical salience guidelines to anti-rationalization table (lowercase context words WRONG/MORE/BEFORE). Add change-report.html to output_schema in both dev-refactor skills.

X-Lerian-Ref: 0x1
2026-02-25 11:46:09 -03:00

1.2 KiB

Anti-Rationalization: Visual Change Report Generation

MANDATORY: Visual HTML report MUST be generated before any user approval checkpoint.

Rationalization Why It's Wrong Required Action
"User can read the markdown output" Markdown requires mental parsing. HTML provides visual severity, diffs, and interactive navigation. Generate HTML report
"Too many findings for HTML" Large reports benefit more from visual structure, not less. Collapsible sections handle scale. Generate HTML report
"Template read slows execution" Template patterns ensure consistent output quality. Skipping produces inconsistent HTML. Read template before generating
"Report is informational, not blocking" Report informs the approval decision. Skipping degrades decision quality. Generate before presenting approval question
"Headless environment, no browser" Still generate and save the file. User can open it later or transfer it. Generate and save; skip open command only if no display
"Previous report already covers this" Each checkpoint is independent. New data may have changed. Generate fresh report at each checkpoint