القائمة
Use when user asks to audit a website, review all pages, check for broken links, capture full site state, or do a comprehensive product review.
التثبيت باستخدام 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 | site-audit |
| description | Use when user asks to audit a website, review all pages, check for broken links, capture full site state, or do a comprehensive product review. |
Use this skill when the user wants a full-product, screenshot-backed audit of a site or web app after login. Goal: maximize meaningful coverage inside strict scope/budget limits, then produce a detailed report with strengths, weaknesses, risks, and technical notes.
Define scope and budget: Set strict crawl bounds to avoid unbounded exploration. Use best-effort exhaustive discovery within those bounds.
Confirm authenticated starting state: Begin only after the user/session is logged in and on the intended start page.
Build a discovery queue: Seed from global navigation, sidebars, footers, in-page links, and major CTAs. De-duplicate by canonical URL (ignore tracking query params unless they change behavior).
Capture complete menu inventory: Expand and record every menu and submenu before broad traversal. For each menu item, capture label, destination, visibility rules, and behavior (navigation/action/modal).
Traverse pages and key states: Visit queued pages, then discover more URLs from each page. Also capture state-level views (tabs, modals, drawers, filters, accordions, pagination).
Capture per-page visual evidence: For each page/state, capture:
Capture per-page diagnostics: Collect page summary, console/runtime errors, warning/error logs, failing network requests, and notable performance clues.
Build feature-by-feature inventory: Record each major feature and its key interactions:
Analyze UX and accessibility: Assess hierarchy, clarity, affordances, feedback, error handling, empty/loading states, consistency, and accessibility basics (labels, focus flow, landmarks, contrast signals).
Extract technical implementation signals: Infer likely stack and implementation details from observable evidence:
Build reproducibility packet: Compile route map, menu map, feature map, key user flows, major states, and implementation clues so another team can reproduce the product structure and behavior.
Synthesize findings into a final report: Rank issues by severity and user impact. Include concrete evidence references (screenshots, logs, endpoints, page URLs).
For every audited page/state, capture all of:
page_id and canonical URLFor every feature, capture all of:
feature_id and feature namesite_mapcoverage_summarymenu_inventorypage_dossiersfeature_inventoryinteraction_resultsusability_reportux_findingsaccessibility_findingstechnical_observationsreproducibility_packetissue_inventory (severity, impact, evidence, owner suggestion)strengths (what is working well)priority_backlog (ranked fixes with expected impact)open_questions_and_gapsUse this section structure in order for every full site audit. If a section is not applicable, write Not observed with a short reason.