Design Audit

Overview

Use this skill to inspect a website or frontend surface and produce a practical design audit: evidence, scores, concrete issues, and prioritized fixes. Prefer direct inspection of the running page whenever possible.

Use re-audit mode when the user asks to compare before/after, check improvements, re-run the audit after fixes, or verify whether a previous audit's issues were solved.

Language

Match the user's language for the entire audit. Support English and Italian explicitly.

• If the user writes in Italian, write headings, table labels, statuses, priorities, verdicts, category notes, and fix sections in Italian.
• If the user writes in English, write the audit in English.
• If the user mixes languages, use the dominant language of the request.
• Keep preset IDs unchanged (landing-page, saas-dashboard, etc.) so prompts and comparisons remain stable.
• Keep standard frontend terms in English when they are clearer or commonly used: CTA, focus state, keyboard navigation, layout shift, responsive, mock, hero, dashboard.

Italian label mapping: