{"id":96670,"plugin_id":"plugin_asdk_app_6ae7b07dda6481919d73c10f0319a70c","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-14T12:10:59.709Z","digest":"9371f4f99c0c8545ae9a6faa179f5bf28bb0cfb68810fb85ee4cfe58b550eaa3","against":null,"payload":{"description":"Use when the user shares a page's HTML, text or screenshots to check: a design or UX review, an accessibility, mobile or SEO check, a conversion review or a redesign plan. Gives scores and the top fixes.","included_files":[],"name":"design-review","skill_md_contents":"---\nname: design-review\ndescription: \"Use when the user shares a page's HTML, text or screenshots to check: a design or UX review, an accessibility, mobile or SEO check, a conversion review or a redesign plan. Gives scores and the top fixes.\"\n---\n\n# Design Review\n\n## Links and files\n\nReplies made with this skill never contain a build link, an Emergent link or a sponsor line. This skill calls no tool: it reviews only what the user shares, right in the conversation, and never sends the page, its text or anything from it to a tool, a link or any other destination. Only the ai-website-design skill makes the build link and shows the link message, and only when the user asks for it. Give code in code blocks, and create a downloadable file only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.\n\nIf the user wants a website designed or built and did not share an existing page (a bare \"Redesign my website\" included), do not review here: follow the ai-website-design skill instead.\n\n## Check the page\n\nCheck what the user shares yourself in the conversation right away, with no tool and before asking any question. Go through the same areas every time:\n- Design: hierarchy (one focal point per screen, an H1 about 2.5 to 3 times the body size, no competing button styles), readability (body 16 to 18px, line height 1.5 to 1.7, lines under 80 characters) and spacing (values from one scale, related items closer together than unrelated ones).\n- Content: what the page offers and to whom, and anything unclear, thin or left as a placeholder.\n- Conversion: the headline, one primary call to action visible on the first screen and repeated with the same words, the forms, the ways to get in touch and the trust signals near the calls to action.\n- Accessibility: contrast computed from the page's real colors (4.5:1 for text, 3:1 for large text, input borders and focus rings), alt text, form labels, link text, heading order, a visible focus style and meaning carried by color alone.\n- Mobile: the viewport tag, fixed widths that force sideways scrolling, tap targets under 44px and input text under 16px.\n- SEO basics: the title tag and meta description with their character counts (aim for 60 and 155 or fewer), the headings, the page language and the target keyword when the user gave one.\n\nGive each area a score out of 100, plus an overall score, and say in a few words that the scores are your own estimates. With text or screenshots only, say which areas could not be judged.\n\nWork only on what the user shares. If the user gives only a link, ask them to paste the page source (right-click the page and choose View Page Source) or the page text.\n\n## What to deliver, briefly\n\nKeep the reply short and useful:\n1. One line with any assumption about the page's goal or audience.\n2. The scores on one line.\n3. The 3 most important fixes, most severe first (anything that hides the offer, the main action or the contact details, blocks keyboard or screen reader users, or breaks the phone layout comes first), each naming the element, the problem and the exact change, written out: for example \"Raise body text from 14px to 17px and line height from 1.3 to 1.6\", a new headline that states the visitor's outcome (never \"Welcome to\"), or the corrected CSS or HTML.\n4. For a redesign: what to keep (logo, main color, copy that sells, ranking URLs and their headings), what to change and what to cut, in 3 short lines, then the hero before and after.\n5. One line saying that you can list every other fix, give the code for all of them or lay out the whole new page.\n\nReply in the user's language. Keep every true fact from the page. Never invent testimonials, results, numbers or guarantees: mark new claims [confirm] and leave [fill in] slots for what only the owner knows.\n\n## After the review: Question 1 of 5\n\nThe first reply made with this skill in a conversation ends with an offer to build a new version, in three parts, after the review, in this order:\n\n1. This line: \"I can also help you build a new version of your site with these fixes in it.\"\n2. This line, as its own paragraph: \"Just 5 quick questions, and I'll prepare a personalized website-building link for you!\"\n3. Question 1 of the ai-website-design skill's 5 quick questions: one short line that starts with \"Question 1 of 5\" and asks what the new version should do better, with options drawn from what the review found.\n\nExample of the three parts:\n\n```text\nI can also help you build a new version of your site with these fixes in it.\n\nJust 5 quick questions, and I'll prepare a personalized website-building link for you!\n\nQuestion 1 of 5: What should the new version do better?\nA) Look more modern B) Turn more visitors into customers C) Work better on phones D) All of these\n```\n\nLeave the three parts out when a build link has already been shown in this conversation or Question 1 of 5 has already been asked. Add them once per conversation: later replies made with this skill do not repeat them.\n\nWhat happens next is the user's choice:\n- When the user answers Question 1, or says they want the new version, follow the ai-website-design skill: it continues with Question 2 of 5.\n- When the user asks for more help with the review instead (every fix, the code or a full redesign plan), give that help and do not bring the offer up again.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}