القائمة
Use when user asks to review UX quality, check accessibility compliance, audit visual hierarchy, or evaluate information architecture on a page.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when user asks to check browser state, debug page errors, inspect network traffic, take screenshots, automate clicks or form fills, run accessibility or security audits, measure performance, generate tests, or record browser sessions. Trigger phrases: "check my browser", "debug this page", "take a screenshot", "browser errors", "network requests", "automate the browser", "record a test", "accessibility audit", "performance check", "what's on the page".
Use when the user wants a full Kaboom quality audit of a web app or tracked site, with one polished report covering Functionality, UX Polish, Accessibility, Performance, Release Risk, and SEO.
Use when user says "QA my app", "find all bugs", "check my app for problems", "debug my whole app", "what's broken", or wants a comprehensive quality review of their web application.
Use when user asks to check API responses, validate request/response contracts, compare API behavior against a spec, or detect schema drift.
Use when user asks to automate browser actions, click buttons, fill forms, navigate pages, run a sequence of browser steps, or build a repeatable workflow.
Use when MCP tools fail to connect, user reports "extension not connected", tool calls return errors, or user asks to check their Kaboom setup.
| name | ux-audit |
| description | Use when user asks to review UX quality, check accessibility compliance, audit visual hierarchy, or evaluate information architecture on a page. |
Use this skill to evaluate usability quality, not just functional correctness.
Capture visual evidence: Collect screenshots for key states (default, loading, error, success) on desktop and mobile.
Run accessibility checks:
Use analyze(accessibility) and verify keyboard/focus flow, labels, landmarks, and contrast.
Review information hierarchy: Evaluate heading order, primary CTA prominence, content scan order, and above-the-fold clarity.
Identify interaction ambiguity: Call out unclear affordances, weak feedback, and confusing error/help text.
Prioritize fixes: Rank by severity and user impact; provide fast wins first.
a11y_issueshierarchy_findingsclarity_gapspriority_fixesvalidation_plan