[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K5V5PPEYZGPW80S9QAF7WZ":3,"skill-same:01M6K5V5PPEYZGPW80S9QAF7WZ":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":29,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6K5V5PPEYZGPW80S9QAF7WZ","visual-aid",null,"Use when the user asks for a quick visual aid, visual explainer, concept card, one-pager, poster, cheat sheet, infographic, visual summary, summary card, or mini explainer page — especially from input like a block of text, attached images, an attached song (lyrics\u002Faudio), a web link, a CSV\u002Fdataset, a math formula, a code snippet to walk through, a tutorial's steps, a timeline, or an A-vs-B comparison. Triggers include \"make me a quick visual aid\", \"turn this into a one-pager \u002F cheat sheet \u002F explainer\", \"summarize this visually\", \"give me a visual of\", \"explain this on a single page\", \"make a concept card for\", \"whip up a page about\", \"build a mini page that shows\", \"something I can paste into a doc explaining X\", or any request to render a topic\u002Ftext\u002Flink\u002Fimage-set\u002Fsong\u002Fdata into a standalone page. Prefer this skill over frontend-design when the ask is an explanatory single-file page (not a production UI), over playground when the output is static information display (not an interactive configurator), and over a Markdown\u002Fcode answer when the user explicitly wants a *page* (HTML). Produces a single self-contained HTML file that opens on double-click without a server.","laurac8r\u002Fclaude-damn","laurac8r","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F23003243?v=4","01M6K5HCAJJR4Q5BCBRRZF8E5D","Laura Kaminskiy","01M6K5HCEQRFFJFK32A0VR7AS3",3,"MIT","https:\u002F\u002Fgithub.com\u002Flaurac8r\u002Fclaude-damn\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-aid\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"visual aid","visual","click","static","frontend-design","standalone","song","quick","information","render","card","frontend","infographic","formula","images","up","visual explainer","Audio","SET","design","2026-11-10 10:12:30",false,"---\nname: visual-aid\ndescription:\n   Use when the user asks for a quick visual aid, visual explainer, concept\n   card, one-pager, poster, cheat sheet, infographic, visual summary, summary\n   card, or mini explainer page — especially from input like a block of text,\n   attached images, an attached song (lyrics\u002Faudio), a web link, a CSV\u002Fdataset,\n   a math formula, a code snippet to walk through, a tutorial's steps, a\n   timeline, or an A-vs-B comparison. Triggers include \"make me a quick visual\n   aid\", \"turn this into a one-pager \u002F cheat sheet \u002F explainer\", \"summarize this\n   visually\", \"give me a visual of\", \"explain this on a single page\", \"make a\n   concept card for\", \"whip up a page about\", \"build a mini page that shows\",\n   \"something I can paste into a doc explaining X\", or any request to render a\n   topic\u002Ftext\u002Flink\u002Fimage-set\u002Fsong\u002Fdata into a standalone page. Prefer this skill\n   over frontend-design when the ask is an explanatory single-file page (not a\n   production UI), over playground when the output is static information display\n   (not an interactive configurator), and over a Markdown\u002Fcode answer when the\n   user explicitly wants a *page* (HTML). Produces a single self-contained HTML\n   file that opens on double-click without a server.\n---\n\n# Visual Aid\n\n## Overview\n\nA **visual aid** is a single self-contained HTML file (one SPA) that presents a\ntopic clearly enough to show someone on a screen, print it, or paste it into a\ndoc. It favors clarity, hierarchy, and accessibility over interactivity. It\nopens on double-click, has no build step, no external network fetches, and\nrenders well on phone and laptop.\n\nThis is the lightweight sibling of `frontend-design` (production UI) and\n`playground` (interactive configurator). Reach for \u002Fvisual-aid when the user\nwants a readable page fast — not a dashboard, not a tool.\n\n## Input shapes — pick a layout from the shape\n\nEach input shape has a default layout. The defaults are starting points, not\nmandates: if the content wants a different shape, deliver that shape.\n\n| Input provided                      | Default layout                                                                                     |\n| ----------------------------------- | -------------------------------------------------------------------------------------------------- |\n| Block of text \u002F concept prompt      | Hero title → intro line → 3–6 titled cards or numbered steps                                       |\n| Attached image(s)                   | Annotated grid (captions as `\u003Cfigcaption>`, always `alt`)                                          |\n| Song (lyrics ± audio file)          | Lyrics-first column with highlighted chorus; `\u003Caudio controls>` if file given                      |\n| Web link                            | Title + source line + 3–6 key points + \"Read more\" anchor back to the link                         |\n| Dataset \u002F CSV \u002F numbers             | Chart-first (inline SVG or `\u003Ccanvas>` rendered once, no JS framework) + 2–4 anchor callouts        |\n| Math \u002F equation \u002F formula           | Large rendered expression (MathML or static SVG) + 2–3 \"what each symbol means\" rows               |\n| Code snippet \u002F function walkthrough | Preformatted block on the left\u002Ftop, numbered annotations on the right\u002Fbelow tying lines to meaning |\n| Tutorial \u002F how-to steps             | Numbered vertical step list; each step has one action verb, one screenshot\u002Fdiagram slot            |\n| Timeline \u002F history                  | Horizontal (wide screen) or vertical (narrow) ordered list with year\u002Flabel → event → one-line why  |\n| Comparison \u002F A-vs-B \u002F A-vs-B-vs-C   | Side-by-side columns (one per thing), shared attribute rows down the side                          |\n\nIf the shape is genuinely unclear from the input, ask **one** short question and\nstop there (e.g., \"grid comparison or single-story flow?\"). Don't guess and\ndon't stack a default \"mixed\" layout — a confused layout is worse than a delayed\none. In non-interactive \u002F one-shot contexts where you can't ask, pick the shape\nclosest to the dominant input and note your choice at the top of the file in an\nHTML comment (`\u003C!-- Input: text; layout: cards -->`).\n\n## Output requirements\n\n1. **One file, no server.** All CSS and JS inline inside `\u003Cstyle>`\u002F`\u003Cscript>`.\n   No `\u003Clink rel=stylesheet>`, no `\u003Cscript src>` pointing off-disk, no CDN\n   imports unless the user explicitly approves them (fonts: use system stack).\n   The file must open on double-click with no network.\n2. **Semantic HTML, landmark-correct.** Exactly one `\u003Ch1>`. `\u003Ch2>`\u002F`\u003Ch3>`\n   descend in order — never skip a level. `\u003Cheader>` and `\u003Cfooter>` are\n   **siblings of `\u003Cmain>`**, not descendants (descendant `\u003Cheader>`\u002F`\u003Cfooter>`\n   lose their `banner`\u002F`contentinfo` landmark roles). Use `\u003Csection>` with a\n   heading for each top-level chunk. Prefer `\u003Cdiv class=\"card\">` over\n   `\u003Carticle>` unless the card is genuinely independently redistributable\n   content.\n3. **Accessible by default** (from a11y-debugging):\n   - `alt` on every `\u003Cimg>` (`alt=\"\"` only for decorative — prove it's\n     decorative before choosing empty).\n   - `\u003Chtml lang=\"...\">` matches the primary content language. For non-English\n     inline runs, add `lang` on the span.\n   - Color contrast ≥ 4.5:1 for body text, ≥ 3:1 for large text and focus rings.\n     If unsure, run a Lighthouse a11y audit (e.g. via the `chrome-devtools-mcp`\n     plugin's `lighthouse_audit` tool, if installed). A score below 90 should be\n     treated as a fail — see the Verification SOP below.\n   - `:focus-visible` ring on every interactive element — cover\n     `a, button, input, select, textarea, summary, [tabindex], [contenteditable]`\n     in the selector. Never `outline: none` without a replacement.\n   - Tap targets ≥ 44×44 CSS px.\n   - Respect `@media (prefers-reduced-motion: reduce)` — use the WCAG pattern\n     `animation-duration: 0.01ms !important; transition-duration: 0.01ms !important`\n     (not `transition: none !important`, which also kills focus\u002Fhover\n     transitions you may add later).\n   - Don't use color alone to convey meaning (pair with icon or text).\n4. **Responsive, zoom-safe, print-safe.** Mobile-first. CSS grid \u002F flex with\n   `clamp()` for typography. No fixed pixel widths on content containers. The\n   `minmax()` in your grid must allow columns to shrink below their min when the\n   container is narrower (use `minmax(min(220px, 100%), 1fr)`). Include a\n   `@media print` block that lightens backgrounds, collapses grids to one\n   column, and drops decorative chrome — the skill's stated use cases include\n   \"print\" and \"paste into a doc.\"\n5. **No information dump.** Pick 3–6 anchor points. If the source has more, the\n   skill's job is to _choose_ — include the chosen anchors in an HTML comment at\n   the top (`\u003C!-- Anchors: X, Y, Z -->`) so the user can see what was curated\n   out.\n6. **No hardcoded color literals in rule bodies.** Every color goes through `--`\n   custom properties set on `:root` (and re-set under\n   `prefers-color-scheme: light`). `color: #fff` in a class body is a bug — it\n   breaks dark mode and theming.\n7. **Save path.** Default to `~\u002F.visual-aid\u002Fvisual-aid-\u003Cslug>.html` on\n   macOS\u002FLinux, `%USERPROFILE%\\.visual-aid\\visual-aid-\u003Cslug>.html` on Windows.\n   Create the directory if it doesn't exist (`mkdir -p ~\u002F.visual-aid\u002F` or\n   Windows equivalent) before writing. If the user names a path, use it. Print\n   the resolved `file:\u002F\u002F` URL on its own line. Put a\n   `\u003C!-- Generated from: \"{one-line prompt summary}\" -->` comment at the very\n   top for traceability.\n\n   **Why `~\u002F.visual-aid\u002F` and not `\u002Ftmp\u002F`:** visual aids are durable artifacts\n   the operator archives and re-opens days later; `\u002Ftmp\u002F` wipes on reboot, so\n   the prior default lost renders silently. The home-directory default keeps\n   prior renders around. Override by naming an explicit path (including\n   `\u002Ftmp\u002F...`) when ephemeral is actually what's wanted.\n\n## Exporting to PDF\n\nThis skill produces HTML, not PDF. When the user asks for a PDF of the rendered\npage, hand off to the operating system's print-to-PDF flow — don't reach for\n`wkhtmltopdf`, headless Chrome scripts, or Playwright unless the user explicitly\nrequests automation.\n\n**The OS-level dialogs that actually export PDF vary by platform.** The SOP\nbelow is the macOS + Chrome path, which is the only one documented here. Other\nplatforms have different system dialogs; if the user is on Linux or Windows,\noffer a short equivalent or ask what flow they prefer before prescribing one.\n\n**macOS + Chrome SOP:**\n\n1. `open \u003Cpath\u002Fto\u002Ffile.html>` from a shell.\n2. In Chrome, adjust zoom if needed, then `⌘P`.\n3. In Chrome's print preview, open the `More settings` dropdown and tune\n   rendering settings there — paper size, margins, scale, headers\u002Ffooters,\n   background graphics.\n4. Click `Print using system dialog… (⌥⌘P)`.\n5. In the macOS Print dialog, click the `PDF` dropdown button (bottom left).\n6. Choose the export target: **Save as PDF…** (default), Open in Preview, Save\n   as Postscript…, Save to iCloud Drive, Save to Web Receipts, or Send in Mail.\n\n**Why two stages:** Chrome's print preview tunes the _render_; the macOS Print\ndialog tunes the _export target_. Skipping straight to the system dialog loses\nChrome's render controls; staying in Chrome limits the export destinations.\n\n**Other platforms (not documented, pointers only):**\n\n- **Linux + Chrome\u002FChromium:** `⌘P` → \"Save as PDF\" destination in Chrome's own\n  dialog; GTK\u002FQt print dialogs vary by distro and don't always offer PDF\n  directly.\n- **Windows + Chrome\u002FEdge:** `Ctrl+P` → \"Microsoft Print to PDF\" as the printer,\n  or \"Save as PDF\" destination.\n- **Firefox \u002F Safari:** different dialog flows; Safari in particular goes\n  straight to the native macOS dialog and skips Chrome's two-stage split.\n\nIf the user is on a platform that isn't macOS + Chrome, ask one question before\nprescribing a flow rather than guessing from documentation written for a\ndifferent OS.\n\n## Baseline template\n\nThe full HTML skeleton lives in the sibling file\n`skills\u002Fvisual-aid\u002Fbaseline.html`. When scaffolding a new visual aid, **copy**\n`baseline.html` as your starting point, then fill in the content slots and prune\nany unused blocks. Never drop the a11y guards (motion, focus, contrast, print).\n\n### Slot conventions\n\nThe template uses placeholder slots that you must replace before saving. **The\nlist below names the structural slots; the rule is broader: every `{{...}}`\npattern in `baseline.html` must be replaced with real content (or the\nsurrounding block deleted) before shipping. Grep the output for `{{` as a final\ncheck — any survivor is a bug.**\n\nSlots in `baseline.html`:\n\n- `{{Title}}` — the page title, used in both `\u003Ctitle>{{Title}}\u003C\u002Ftitle>` and the\n  visible `\u003Ch1>`.\n- `{{one-line prompt summary}}` — a brief description of the user's request,\n  placed in the traceability comment\n  `\u003C!-- Generated from: \"{{one-line prompt summary}}\" -->` at the very top.\n- `{{X}}`, `{{Y}}`, `{{Z}}` — the 3–6 anchor points you curated from the source,\n  listed in `\u003C!-- Anchors: {{X}}, {{Y}}, {{Z}} -->` so the user can see what was\n  included and what was left out.\n- `{{One-line intro — what this page is and who it's for}}` — the lede paragraph\n  under the `\u003Ch1>`. Replace with a real sentence; do not leave the hint text.\n- `{{Point 1}}`, `{{Point 2}}`, `{{Point 3}}` — card titles in the default\n  three-card layout. Add or remove cards to match your chosen shape from the\n  Input shapes table; don't pad to three if the source has two.\n- `{{…}}` — card body text under each card title. One per card; replace with the\n  curated content for that anchor.\n- `{{link or \"—\"}}` — the source link in the footer. Use the URL the user\n  provided, or replace with `—` (em dash) if there's no canonical source.\n\n## Worked examples — different inputs, different shapes\n\nThe worked examples below are **illustrative of shape-diversity**, not a\ntemplate to clone. A comparison input doesn't get the three-body card layout; a\nsong doesn't get a chart.\n\n**Input:** \"make me a quick visual aid on the three-body problem\" Shape: concept\nprompt → hero + 3 cards + small inline SVG (motion-guarded) + source link.\n\n**Input:** \"compare REST vs GraphQL vs gRPC\" Shape: comparison → one column per\napproach, shared attribute rows (protocol, streaming, caching, type safety);\ntraffic-light indicators always paired with **text** (Yes\u002FNo\u002FPartial), never\ncolor alone.\n\n**Input:** \"turn these lyrics into a concept card: \u003Clyrics>\" Shape: song →\nsingle reading column, chorus visually highlighted (border\u002Fbackground shift),\n`\u003Caudio controls>` only if an audio file was provided. No cards.\n\n**Bad output, regardless of input:** transcribing every equation\u002Frow\u002Fline from\nthe source, dark-on-dark text, missing `alt`, CDN imports, motion without a\nreduced-motion guard, \"helpful\" interactive controls the user never asked for.\n\n## Process\n\n1. **Read the input** and pick the layout from the Input shapes table. If\n   genuinely ambiguous, ask one question; if you can't ask (non-interactive),\n   pick the closest shape and record your choice in the top-of-file\n   `\u003C!-- Input: … -->` comment.\n2. **Fill the template.** Prune unused blocks. Inline every asset as a `data:`\n   URI — any local relative path breaks the \"opens on double-click anywhere\"\n   promise and must be called out in the response if the user provided a file\n   that's too large to inline.\n3. **Run the self-check below.** Fix every failure before emitting. Don't mark a\n   box unless you actually verified it — if you can't verify (e.g., real browser\n   zoom), say so in the response instead of ticking it.\n4. **Write the file**, then print the resolved `file:\u002F\u002F` path on its own line so\n   the user can click it.\n\n## A11y self-check (run before emitting)\n\nVerifiable by the agent:\n\n- [ ] Exactly one `\u003Ch1>`; headings never skip a level.\n- [ ] `\u003Chtml lang=\"...\">` matches the primary content language.\n- [ ] `\u003Cheader>` and `\u003Cfooter>` are siblings of `\u003Cmain>` (so their landmark\n      roles survive).\n- [ ] Every `\u003Cimg>` has `alt` (empty only if decorative and that's deliberate).\n- [ ] Text contrast computed for **every custom color value** against the\n      background it sits on, in both light and dark palettes. No \"borderline\"\n      escape hatch — if you picked the color, you compute the ratio. **Compute\n      means apply the WCAG sRGB formula**\n      (`L = 0.2126·R' + 0.7152·G' + 0.0722·B'` on linearized channels, then\n      `ratio = (L_light + 0.05)\u002F(L_dark + 0.05)`). Estimating luminances by eye\n      is not computing. \"These are baseline-template colors, known-passing\" is\n      not computing. If you didn't run the formula, don't tick — write the\n      ratios (or note \"estimated, flag for human verification\") in your response\n      instead.\n- [ ] `:focus-visible` selector covers a, button, input, select, textarea,\n      summary, [tabindex], [contenteditable].\n- [ ] Motion guard uses the WCAG `0.01ms` pattern, not `transition: none`.\n- [ ] Nothing relies on color alone (every status\u002Fpill has text or an icon too).\n- [ ] No hardcoded color literals outside `:root`.\n- [ ] `@media print` block exists and collapses the grid to 1 column.\n- [ ] The file contains a `\u003C!-- Anchors: … -->` comment listing what was curated\n      in.\n- [ ] File opens without network: grep the HTML — zero `http:\u002F\u002F`\u002F`https:\u002F\u002F`\n      outside anchor `href`s that the user explicitly asked for.\n\nLayout (automated) and print (manual) checks:\n\n- [ ] Renders sanely at 320px width and at 200% browser zoom — **automated** via\n      mobile-viewport screenshot in the chrome-devtools verification step below.\n- [ ] Printed preview looks right — **manual**: run the OS print-to-PDF flow\n      (see `reference_html_to_pdf_sop`) after the chrome-devtools verification\n      passes. The chrome-devtools SOP does not cover print rendering.\n\n## Verification (chrome-devtools)\n\nAutomated browser verification runs **by default** on every `\u002Fvisual-aid`\ninvocation. It drives Chrome via the `chrome-devtools-mcp` plugin. Pass\n`--no-verify` to skip (e.g., when chrome-devtools-mcp is not installed, or for\nrapid iteration where you only want the HTML output).\n\n### SOP\n\n> **Note on artifact vs verification URL.** The HTTP server below exists _only_\n> for the verification pass. The final artifact the agent surfaces to the user\n> is always the durable `file:\u002F\u002F` path to the on-disk HTML — the localhost URL\n> disappears the moment the server stops in step 8.\n\n1. **Resolve slug + dirs.** Lowercase the prompt, replace spaces\u002Fpunctuation\n   with dashes. Create `\u002Ftmp\u002Fvisual-aid\u002F\u003Cslug>\u002F` (`mkdir -p`).\n\n2. **Start a local HTTP server.** Pick an unused high port (e.g., 8765), then\n   run `python3 -m http.server \u003Cport>` rooted at the _directory containing the\n   output HTML_ in the background. Capture the PID\u002Fjob id so you can stop it in\n   step 8. _Why HTTP:_ Lighthouse rejects `file:\u002F\u002F` URLs with `INVALID_URL` and\n   requires an HTTP origin — a bare `file:\u002F\u002F` path causes the Lighthouse audit\n   to fail before it can score the page.\n\n3. **Open in browser.** Use `navigate_page` to load\n   `http:\u002F\u002Flocalhost:\u003Cport>\u002F\u003Cfilename>` (not the `file:\u002F\u002F` URL).\n\n   **Profile-lock fallback.** If `new_page` \u002F `navigate_page` \u002F `list_pages`\n   return the error\n   `The browser is already running for \u003CuserDataDir>. Use --isolated to run multiple browser instances`,\n   the operator's own Chrome session is holding the profile lock and you cannot\n   drive a second instance against the same `userDataDir`. Do **not** retry the\n   same call — it will keep returning the same error. Either:\n   - Retry chrome-devtools-mcp invocations with the `--isolated` flag (creates a\n     separate ephemeral profile dir, no conflict with the operator's session),\n     then resume the SOP from step 3, **or**\n   - Stop the SOP, **execute step 8 (kill the http.server) before exiting** —\n     the server was started in step 2 and leaving it running risks port\n     collisions on the next invocation — and skip verification per the matching\n     `chrome-devtools-mcp profile lock` opt-out below. Name the actual cause in\n     your response — do **not** repackage a profile-lock under \"fast iteration\"\n     or \"not installed.\"\n\n4. **Desktop screenshot.** Use `take_screenshot` — save to\n   `\u002Ftmp\u002Fvisual-aid\u002F\u003Cslug>\u002Fdesktop.png`.\n\n5. **Mobile viewport screenshot.** Use `resize_page` (width 375, height 812) to\n   switch to a mobile viewport, then `take_screenshot` — save to\n   `\u002Ftmp\u002Fvisual-aid\u002F\u003Cslug>\u002Fmobile.png`. This covers the \"renders sanely at 320\n   px \u002F small viewport\" self-check.\n\n6. **Console check.** Use `list_console_messages`. If any error-level console\n   errors are present, **execute step 8 (kill the http.server) before\n   aborting**, then attach the console errors to the response. Do not emit the\n   file path until all console errors are resolved.\n\n7. **Lighthouse a11y audit.** Use `lighthouse_audit` (threshold 90) against the\n   same `http:\u002F\u002Flocalhost:\u003Cport>\u002F\u003Cfilename>` URL. If the accessibility score is\n   below 90, **execute step 8 (kill the http.server) before aborting**, then\n   attach the failing audits. A score below that threshold means the page ships\n   with real a11y defects — fix them before surfacing the output.\n\n8. **Stop the server.** Kill the background `http.server` job (e.g.,\n   `pkill -f \"http.server \u003Cport>\"`). The server is one-shot — leaving it running\n   risks port collisions on subsequent invocations.\n\n9. **Surface artifacts.** On success, print the artifact paths inline:\n   - `file:\u002F\u002F\u003Cabsolute-path-to-output.html>` ← the durable on-disk HTML\n   - `file:\u002F\u002F\u002Ftmp\u002Fvisual-aid\u002F\u003Cslug>\u002Fdesktop.png`\n   - `file:\u002F\u002F\u002Ftmp\u002Fvisual-aid\u002F\u003Cslug>\u002Fmobile.png`\n\n   The screenshots are ephemeral — `\u002Ftmp\u002Fvisual-aid\u002F` is not persisted across\n   reboots. The HTML output is durable at its original write path.\n\n### Opt-out\n\nPass `--no-verify` when:\n\n- `chrome-devtools-mcp` is not installed in the current environment.\n- Fast iteration: you want the raw HTML first and will verify manually.\n- CI \u002F headless environments without a browser.\n- **chrome-devtools-mcp profile lock** — the operator's own Chrome session is\n  already running on the same `userDataDir` and the plugin returns\n  `browser already running ... use --isolated`. The plugin IS installed and the\n  environment IS interactive; the blocker is environmental (a held profile\n  lock), not a preference. First try retrying chrome-devtools-mcp with\n  `--isolated` if available; if not, skip verification and **name the\n  profile-lock cause in your response** — do not silently route through \"fast\n  iteration\" or \"not installed.\"\n\n## Common mistakes\n\n| Mistake                                                                                                                                                                                                                   | Why it breaks the \"quick aid\" promise                                                                                                                                                                                                                                                                                                                                                                                                                                                        |\n| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| External `\u003Clink>`\u002F`\u003Cscript>` to a CDN                                                                                                                                                                                     | Fails offline; breaks \"open on double-click\"                                                                                                                                                                                                                                                                                                                                                                                                                                                 |\n| Adding interactive controls the user didn't ask for                                                                                                                                                                       | That's `playground`, not `visual-aid` — stay in your lane                                                                                                                                                                                                                                                                                                                                                                                                                                    |\n| Dumping the full source text into the page                                                                                                                                                                                | Visual aid means _chosen_ points — dump is not aid                                                                                                                                                                                                                                                                                                                                                                                                                                           |\n| Dark text on dark card (contrast fail)                                                                                                                                                                                    | First thing a11y-debugging's Lighthouse pass will catch                                                                                                                                                                                                                                                                                                                                                                                                                                      |\n| Decorative icons without `aria-hidden=\"true\"`                                                                                                                                                                             | Screen reader reads \"image, image, image\"                                                                                                                                                                                                                                                                                                                                                                                                                                                    |\n| Fixed px widths that overflow on mobile                                                                                                                                                                                   | Breaks the \"works on phone and laptop\" baseline                                                                                                                                                                                                                                                                                                                                                                                                                                              |\n| `minmax(220px, 1fr)` without a `min()` wrapper                                                                                                                                                                            | Causes horizontal overflow at 320px — the template's old default had this bug                                                                                                                                                                                                                                                                                                                                                                                                                |\n| `\u003Cheader>` or `\u003Cfooter>` placed inside `\u003Cmain>`                                                                                                                                                                           | Loses their `banner`\u002F`contentinfo` landmark roles — screen readers miss the chrome                                                                                                                                                                                                                                                                                                                                                                                                           |\n| Color-coded status (pill pros\u002Fcons, traffic-light dots) with no text\u002Ficon alternative                                                                                                                                     | The color _is_ the meaning — breaks for color-blind users and most b\u002Fw prints                                                                                                                                                                                                                                                                                                                                                                                                                |\n| Reusing dark-mode `--accent`\u002F`--ring` in light mode                                                                                                                                                                       | Pale blues\u002Fgolds that look great on black fail 4.5:1 \u002F 3:1 on white — re-pick both                                                                                                                                                                                                                                                                                                                                                                                                           |\n| Hardcoded color literals (`#fff`, `color: black`) in CSS class bodies                                                                                                                                                     | Breaks dark mode, print mode, and theming — everything should flow from `:root`                                                                                                                                                                                                                                                                                                                                                                                                              |\n| `!important` sprinkled across rule bodies                                                                                                                                                                                 | Fights with `prefers-color-scheme` and `@media print` overrides you need to work                                                                                                                                                                                                                                                                                                                                                                                                             |\n| Deprecated tags (`\u003Ccenter>`, `\u003Cfont>`, `\u003Cb>`\u002F`\u003Ci>` for emphasis vs style)                                                                                                                                                 | Non-semantic; use CSS for presentation and `\u003Cstrong>`\u002F`\u003Cem>` for emphasis                                                                                                                                                                                                                                                                                                                                                                                                                    |\n| Cloning the worked-example shape for every input                                                                                                                                                                          | A comparison input doesn't get three cards + SVG — pick from the Input shapes table                                                                                                                                                                                                                                                                                                                                                                                                          |\n| Claiming the self-check passed without running it                                                                                                                                                                         | The self-check is not a ceremony — lying in it means the page ships with real defects                                                                                                                                                                                                                                                                                                                                                                                                        |\n| Ticking \"contrast computed\" without applying the WCAG sRGB formula                                                                                                                                                        | Visual inspection (\"looks high-contrast\") and appeal to template authority (\"these are baseline colors, they're known-passing\") are both the \"borderline escape hatch\" the self-check bans. Either apply `L = 0.2126·R' + 0.7152·G' + 0.0722·B'` per color pair and write the ratio, or flag for human verification — don't tick.                                                                                                                                                            |\n| Routing an environmental blocker through a preference-coded opt-out (e.g. citing \"fast iteration\" when chrome-devtools-mcp returned a profile-lock error, or stretching \"not installed\" to cover \"installed but blocked\") | The opt-out reasons aren't fungible — each names a specific cause. Repackaging a profile-lock as \"fast iteration\" hides the real failure mode from the operator and from future-you reading the response. The skill defines a `chrome-devtools-mcp profile lock` opt-out for exactly this case — use it and name the cause verbatim. If a new environmental blocker doesn't match any listed opt-out, surface that as a gap rather than stretching the closest preference-coded exit to fit. |\n\n## When NOT to use this skill\n\n- User wants a **production UI or component** → use `frontend-design`.\n- User wants an **interactive configurator** (sliders\u002Finputs that compose an\n  output) → use `playground`.\n- User wants a **slide deck, presentation, or PDF** → not this skill.\n- User wants a **dashboard with live data** → not this skill.\n- User wants a **plain doc or article** (reading copy, not a display page) →\n  return Markdown, not HTML.\n- User wants a **pure reference\u002Fcomparison table with no narrative** (e.g.,\n  \"just give me a matrix of X vs Y\") → return a Markdown table; only reach for\n  \u002Fvisual-aid if they want prose around it or the page format is explicit.\n","# Visual Aid\n\n## Overview\n\nA **visual aid** is a single self-contained HTML file (one SPA) that presents a\ntopic clearly enough to show someone on a screen, print it, or paste it into a\ndoc. It favors clarity, hierarchy, and accessibility over interactivity. It\nopens on double-click, has no build step, no external network fetches, and\nrenders well on phone and laptop.\n\nThis is the lightweight sibling of `frontend-design` (production UI) and\n`playground` (interactive configurator). Reach for \u002Fvisual-aid when the user\nwants a readable page fast — not a dashboard, not a tool.\n\n## Input shapes — pick a layout from the shape\n\nEach input shape has a default layout. The defaults are starting points, not\nmandates: if the content wants a different shape, deliver that shape.\n\n| Input provided                      | Default layout                                                                                     |\n| ----------------------------------- | -------------------------------------------------------------------------------------------------- |\n| Block of text \u002F concept prompt      | Hero title → intro line → 3–6 titled cards or numbered steps                                       |\n| Attached image(s)                   | Annotated grid (captions as `\u003Cfigcaption>`, always `alt`)                                          |\n| Song (lyrics ± audio file)          | Lyrics-first column with highlighted chorus; `\u003Caudio controls>` if file given                      |\n| Web link                            | Title + source line + 3–6 key points + \"Read more\" anchor back to the link                         |\n| Dataset \u002F CSV \u002F numbers             | Chart-first (inline SVG or `\u003Ccanvas>` rendered once, no JS framework) + 2–4 anchor callouts        |\n| Math \u002F equation \u002F formula           | Large rendered expression (MathML or static SVG) + 2–3 \"what each symbol means\" rows               |\n| Code snippet \u002F function walkthrough | Preformatted block on the left\u002Ftop, numbered annotations on the right\u002Fbelow tying lines to meaning |\n| Tutorial \u002F how-to steps             | Numbered vertical step list; each step has one action verb, one screenshot\u002Fdiagram slot            |\n| Timeline \u002F history                  | Horizontal (wide screen) or vertical (narrow) ordered list with year\u002Flabel → event → one-line why  |\n| Comparison \u002F A-vs-B \u002F A-vs-B-vs-C   | Side-by-side columns (one per thing), shared attribute rows down the side                          |\n\nIf the shape is genuinely unclear from the input, ask **one** short question and\nstop there (e.g., \"grid comparison or single-story flow?\"). Don't guess and\ndon't stack a default \"mixed\" layout — a confused layout is worse than a delayed\none. In non-interactive \u002F one-shot contexts where you can't ask, pick the shape\nclosest to the dominant input and note your choice at the top of the file in an\nHTML comment (`\u003C!-- Input: text; layout: cards -->`).\n\n## Output requirements\n\n1. **One file, no server.** All CSS and JS inline inside `\u003Cstyle>`\u002F`\u003Cscript>`.\n   No `\u003Clink rel=stylesheet>`, no `\u003Cscript src>` pointing off-disk, no CDN\n   imports unless the user explicitly approves them (fonts: use system stack).\n   The file must open on double-click with no network.\n2. **Semantic HTML, landmark-correct.** Exactly one `\u003Ch1>`. `\u003Ch2>`\u002F`\u003Ch3>`\n   descend in order — never skip a level. `\u003Cheader>` and `\u003Cfooter>` are\n   **siblings of `\u003Cmain>`**, not descendants (descendant `\u003Cheader>`\u002F`\u003Cfooter>`\n   lose their `banner`\u002F`contentinfo` landmark roles). Use `\u003Csection>` with a\n   heading for each top-level chunk. Prefer `\u003Cdiv class=\"card\">` over\n   `\u003Carticle>` unless the card is genuinely independently redistributable\n   content.\n3. **Accessible by default** (from a11y-debugging):\n   - `alt` on every `\u003Cimg>` (`alt=\"\"` only for decorative — prove it's\n     decorative before choosing empty).\n   - `\u003Chtml lang=\"...\">` matches the primary content language. For non-English\n     inline runs, add `lang` on the span.\n   - Color contrast ≥ 4.5:1 for body text, ≥ 3:1 for large text and focus rings.\n     If unsure, run a Lighthouse a11y audit (e.g. via the `chrome-devtools-mcp`\n     plugin's `lighthouse_audit` tool, if installed). A score below 90 should be\n     treated as a fail — see the Verification SOP below.\n   - `:focus-visible` ring on every interactive element — cover\n     `a, button, input, select, textarea, summary, [tabindex], [contenteditable]`\n     in the selector. Never `outline: none` without a replacement.\n   - Tap targets ≥ 44×44 CSS px.\n   - Respect `@media (prefers-reduced-motion: reduce)` — use the WCAG pattern\n     `animation-duration: 0.01ms !important; transition-duration: 0.01ms !important`\n     (not `transition: none !important`, which also kills focus\u002Fhover\n     transitions you may add later).\n   - Don't use color alone to convey meaning (pair with icon or text).\n4. **Responsive, zoom-safe, print-safe.** Mobile-first. CSS grid \u002F flex with\n   `clamp()` for typography. No fixed pixel widths on content containers. The\n   `minmax()` in your grid must allow columns to shrink below their min when the\n   container is narrower (use `minmax(min(220px, 100%), 1fr)`). Include a\n   `@media print` block that lightens backgrounds, collapses grids to one\n   column, and drops decorative chrome — the skill's stated use cases include\n   \"print\" and \"paste into a doc.\"\n5. **No information dump.** Pick 3–6 anchor points. If the source has more, the\n   skill's job is to _choose_ — include the chosen anchors in an HTML comment at\n   the top (`\u003C!-- Anchors: X, Y, Z -->`) so the user can see what was curated\n   out.\n6. **No hardcoded color literals in rule bodies.** Every color goes through `--`\n   custom properties set on `:root` (and re-set under\n   `prefers-color-scheme: light`). `color: #fff` in a class body is a bug — it\n   breaks dark mode and theming.\n7. **Save path.** Default to `~\u002F.visual-aid\u002Fvisual-aid-\u003Cslug>.html` on\n   macOS\u002FLinux, `%USERPROFILE%\\.visual-aid\\visual-aid-\u003Cslug>.html` on Windows.\n   Create the directory if it doesn't exist (`mkdir -p ~\u002F.visual-aid\u002F` or\n   Windows equivalent) before writing. If the user names a path, use it. Print\n   the resolved `file:\u002F\u002F` URL on its own line. Put a\n   `\u003C!-- Generated from: \"{one-line prompt summary}\" -->` comment at the very\n   top for traceability.\n\n   **Why `~\u002F.visual-aid\u002F` and not `\u002Ftmp\u002F`:** visual aids are durable artifacts\n   the operator archives and re-opens days later; `\u002Ftmp\u002F` wipes on reboot, so\n   the prior default lost renders silently. The home-directory default keeps\n   prior renders around. Override by naming an explicit path (including\n   `\u002Ftmp\u002F...`) when ephemeral is actually what's wanted.\n\n## Exporting to PDF\n\nThis skill produces HTML, not PDF. When the user asks for a PDF of the rendered\npage, hand off to the operating system's print-to-PDF flow — don't reach for\n`wkhtmltopdf`, headless Chrome scripts, or Playwright unless the user explicitly\nrequests automation.\n\n**The OS-level dialogs that actually export PDF vary by platform.** The SOP\nbelow is the macOS + Chrome path, which is the only one documented here. Other\nplatforms have different system dialogs; if the user is on Linux or Windows,\noffer a short equivalent or ask what flow they prefer before prescribing one.\n\n**macOS + Chrome SOP:**\n\n1. `open \u003Cpath\u002Fto\u002Ffile.html>` from a shell.\n2. In Chrome, adjust zoom if needed, then `⌘P`.\n3. In Chrome's print preview, open the `More settings` dropdown and tune\n   rendering settings there — paper size, margins, scale, headers\u002Ffooters,\n   background graphics.\n4. Click `Print using system dialog… (⌥⌘P)`.\n5. In the macOS Print dialog, click the `PDF` dropdown button (bottom left).\n6. Choose the export target: **Save as PDF…** (default), Open in Preview, Save\n   as Postscript…, Save to iCloud Drive, Save to Web Receipts, or Send in Mail.\n\n**Why two stages:** Chrome's print preview tunes the _render_; the macOS Print\ndialog tunes the _export target_. Skipping straight to the system dialog loses\nChrome's render controls; staying in Chrome limits the export destinations.\n\n**Other platforms (not documented, pointers only):**\n\n- **Linux + Chrome\u002FChromium:** `⌘P` → \"Save as PDF\" destination in Chrome's own\n  dialog; GTK\u002FQt print dialogs vary by distro and don't always offer PDF\n  directly.\n- **Windows + Chrome\u002FEdge:** `Ctrl+P` → \"Microsoft Print to PDF\" as the printer,\n  or \"Save as PDF\" destination.\n- **Firefox \u002F Safari:** different dialog flows; Safari in particular goes\n  straight to the native macOS dialog and skips Chrome's two-stage split.\n\nIf the user is on a platform that isn't macOS + Chrome, ask one question before\nprescribing a flow rather than guessing from documentation written for a\ndifferent OS.\n\n## Baseline template\n\nThe full HTML skeleton lives in the sibling file\n`skills\u002Fvisual-aid\u002Fbaseline.html`. When scaffolding a new visual aid, **copy**\n`baseline.html` as your starting point, then fill in the content slots and prune\nany unused blocks. Never drop the a11y guards (motion, focus, contrast, print).\n\n### Slot conventions\n\nThe template uses placeholder slots that you must replace before saving. **The\nlist below names the structural slots; the rule is broader: every `{{...}}`\npattern in `baseline.html` must be replaced with real content (or the\nsurrounding block deleted) before shipping. Grep the output for `{{` as a final\ncheck — any survivor is a bug.**\n\nSlots in `baseline.html`:\n\n- `{{Title}}` — the page title, used in both `\u003Ctitle>{{Title}}\u003C\u002Ftitle>` and the\n  visible `\u003Ch1>`.\n- `{{one-line prompt summary}}` — a brief description of the user's request,\n  placed in the traceability comment\n  `\u003C!-- Generated from: \"{{one-line prompt summary}}\" -->` at the very top.\n- `{{X}}`, `{{Y}}`, `{{Z}}` — the 3–6 anchor points you curated from the source,\n  listed in `\u003C!-- Anchors: {{X}}, {{Y}}, {{Z}} -->` so the user can see what was\n  included and what was left out.\n- `{{One-line intro — what this page is and who it's for}}` — the lede paragraph\n  under the `\u003Ch1>`. Replace with a real sentence; do not leave the hint text.\n- `{{Point 1}}`, `{{Point 2}}`, `{{Point 3}}` — card titles in the default\n  three-card layout. Add or remove cards to match your chosen shape from the\n  Input shapes table; don't pad to three if the source has two.\n- `{{…}}` — card body text under each card title. One per card; replace with the\n  curated content for that anchor.\n- `{{link or \"—\"}}` — the source link in the footer. Use the URL the user\n  provided, or replace with `—` (em dash) if there's no canonical source.\n\n## Worked examples — different inputs, different shapes\n\nThe worked examples below are **illustrative of shape-diversity**, not a\ntemplate to clone. A comparison input doesn't get the three-body card layout; a\nsong doesn't get a chart.\n\n**Input:** \"make me a quick visual aid on the three-body problem\" Shape: concept\nprompt → hero + 3 cards + small inline SVG (motion-guarded) + source link.\n\n**Input:** \"compare REST vs GraphQL vs gRPC\" Shape: comparison → one column per\napproach, shared attribute rows (protocol, streaming, caching, type safety);\ntraffic-light indicators always paired with **text** (Yes\u002FNo\u002FPartial), never\ncolor alone.\n\n**Input:** \"turn these lyrics into a concept card: \u003Clyrics>\" Shape: song →\nsingle reading column, chorus visually highlighted (border\u002Fbackground shift),\n`\u003Caudio controls>` only if an audio file was provided. No cards.\n\n**Bad output, regardless of input:** transcribing every equation\u002Frow\u002Fline from\nthe source, dark-on-dark text, missing `alt`, CDN imports, motion without a\nreduced-motion guard, \"helpful\" interactive controls the user never asked for.\n\n## Process\n\n1. **Read the input** and pick the layout from the Input shapes table. If\n   genuinely ambiguous, ask one question; if you can't ask (non-interactive),\n   pick the closest shape and record your choice in the top-of-file\n   `\u003C!-- Input: … -->` comment.\n2. **Fill the template.** Prune unused blocks. Inline every asset as a `data:`\n   URI — any local relative path breaks the \"opens on double-click anywhere\"\n   promise and must be called out in the response if the user provided a file\n   that's too large to inline.\n3. **Run the self-check below.** Fix every failure before emitting. Don't mark a\n   box unless you actually verified it — if you can't verify (e.g., real browser\n   zoom), say so in the response instead of ticking it.\n4. **Write the file**, then print the resolved `file:\u002F\u002F` path on its own line so\n   the user can click it.\n\n## A11y self-check (run before emitting)\n\nVerifiable by the agent:\n\n- [ ] Exactly one `\u003Ch1>`; headings never skip a level.\n- [ ] `\u003Chtml lang=\"...\">` matches the primary content language.\n- [ ] `\u003Cheader>` and `\u003Cfooter>` are siblings of `\u003Cmain>` (so their landmark\n      roles survive).\n- [ ] Every `\u003Cimg>` has `alt` (empty only if decorative and that's deliberate).\n- [ ] Text contrast computed for **every custom color value** against the\n      background it sits on, in both light and dark palettes. No \"borderline\"\n      escape hatch — if you picked the color, you compute the ratio. **Compute\n      means apply the WCAG sRGB formula**\n      (`L = 0.2126·R' + 0.7152·G' + 0.0722·B'` on linearized channels, then\n      `ratio = (L_light + 0.05)\u002F(L_dark + 0.05)`). Estimating luminances by eye\n      is not computing. \"These are baseline-template colors, known-passing\" is\n      not computing. If you didn't run the formula, don't tick — write the\n      ratios (or note \"estimated, flag for human verification\") in your response\n      instead.\n- [ ] `:focus-visible` selector covers a, button, input, select, textarea,\n      summary, [tabindex], [contenteditable].\n- [ ] Motion guard uses the WCAG `0.01ms` pattern, not `transition: none`.\n- [ ] Nothing relies on color alone (every status\u002Fpill has text or an icon too).\n- [ ] No hardcoded color literals outside `:root`.\n- [ ] `@media print` block exists and collapses the grid to 1 column.\n- [ ] The file contains a `\u003C!-- Anchors: … -->` comment listing what was curated\n      in.\n- [ ] File opens without network: grep the HTML — zero `http:\u002F\u002F`\u002F`https:\u002F\u002F`\n      outside anchor `href`s that the user explicitly asked for.\n\nLayout (automated) and print (manual) checks:\n\n- [ ] Renders sanely at 320px width and at 200% browser zoom — **automated** via\n      mobile-viewport screenshot in the chrome-devtools verification step below.\n- [ ] Printed preview looks right — **manual**: run the OS print-to-PDF flow\n      (see `reference_html_to_pdf_sop`) after the chrome-devtools verification\n      passes. The chrome-devtools SOP does not cover print rendering.\n\n## Verification (chrome-devtools)\n\nAutomated browser verification runs **by default** on every `\u002Fvisual-aid`\ninvocation. It drives Chrome via the `chrome-devtools-mcp` plugin. Pass\n`--no-verify` to skip (e.g., when chrome-devtools-mcp is not installed, or for\nrapid iteration where you only want the HTML output).\n\n### SOP\n\n> **Note on artifact vs verification URL.** The HTTP server below exists _only_\n> for the verification pass. The final artifact the agent surfaces to the user\n> is always the durable `file:\u002F\u002F` path to the on-disk HTML — the localhost URL\n> disappears the moment the server stops in step 8.\n\n1. **Resolve slug + dirs.** Lowercase the prompt, replace spaces\u002Fpunctuation\n   with dashes. Create `\u002Ftmp\u002Fvisual-aid\u002F\u003Cslug>\u002F` (`mkdir -p`).\n\n2. **Start a local HTTP server.** Pick an unused high port (e.g., 8765), then\n   run `python3 -m http.server \u003Cport>` rooted at the _directory containing the\n   output HTML_ in the background. Capture the PID\u002Fjob id so you can stop it in\n   step 8. _Why HTTP:_ Lighthouse rejects `file:\u002F\u002F` URLs with `INVALID_URL` and\n   requires an HTTP origin — a bare `file:\u002F\u002F` path causes the Lighthouse audit\n   to fail before it can score the page.\n\n3. **Open in browser.** Use `navigate_page` to load\n   `http:\u002F\u002Flocalhost:\u003Cport>\u002F\u003Cfilename>` (not the `file:\u002F\u002F` URL).\n\n   **Profile-lock fallback.** If `new_page` \u002F `navigate_page` \u002F `list_pages`\n   return the error\n   `The browser is already running for \u003CuserDataDir>. Use --isolated to run multiple browser instances`,\n   the operator's own Chrome session is holding the profile lock and you cannot\n   drive a second instance against the same `userDataDir`. Do **not** retry the\n   same call — it will keep returning the same error. Either:\n   - Retry chrome-devtools-mcp invocations with the `--isolated` flag (creates a\n     separate ephemeral profile dir, no conflict with the operator's session),\n     then resume the SOP from step 3, **or**\n   - Stop the SOP, **execute step 8 (kill the http.server) before exiting** —\n     the server was started in step 2 and leaving it running risks port\n     collisions on the next invocation — and skip verification per the matching\n     `chrome-devtools-mcp profile lock` opt-out below. Name the actual cause in\n     your response — do **not** repackage a profile-lock under \"fast iteration\"\n     or \"not installed.\"\n\n4. **Desktop screenshot.** Use `take_screenshot` — save to\n   `\u002Ftmp\u002Fvisual-aid\u002F\u003Cslug>\u002Fdesktop.png`.\n\n5. **Mobile viewport screenshot.** Use `resize_page` (width 375, height 812) to\n   switch to a mobile viewport, then `take_screenshot` — save to\n   `\u002Ftmp\u002Fvisual-aid\u002F\u003Cslug>\u002Fmobile.png`. This covers the \"renders sanely at 320\n   px \u002F small viewport\" self-check.\n\n6. **Console check.** Use `list_console_messages`. If any error-level console\n   errors are present, **execute step 8 (kill the http.server) before\n   aborting**, then attach the console errors to the response. Do not emit the\n   file path until all console errors are resolved.\n\n7. **Lighthouse a11y audit.** Use `lighthouse_audit` (threshold 90) against the\n   same `http:\u002F\u002Flocalhost:\u003Cport>\u002F\u003Cfilename>` URL. If the accessibility score is\n   below 90, **execute step 8 (kill the http.server) before aborting**, then\n   attach the failing audits. A score below that threshold means the page ships\n   with real a11y defects — fix them before surfacing the output.\n\n8. **Stop the server.** Kill the background `http.server` job (e.g.,\n   `pkill -f \"http.server \u003Cport>\"`). The server is one-shot — leaving it running\n   risks port collisions on subsequent invocations.\n\n9. **Surface artifacts.** On success, print the artifact paths inline:\n   - `file:\u002F\u002F\u003Cabsolute-path-to-output.html>` ← the durable on-disk HTML\n   - `file:\u002F\u002F\u002Ftmp\u002Fvisual-aid\u002F\u003Cslug>\u002Fdesktop.png`\n   - `file:\u002F\u002F\u002Ftmp\u002Fvisual-aid\u002F\u003Cslug>\u002Fmobile.png`\n\n   The screenshots are ephemeral — `\u002Ftmp\u002Fvisual-aid\u002F` is not persisted across\n   reboots. The HTML output is durable at its original write path.\n\n### Opt-out\n\nPass `--no-verify` when:\n\n- `chrome-devtools-mcp` is not installed in the current environment.\n- Fast iteration: you want the raw HTML first and will verify manually.\n- CI \u002F headless environments without a browser.\n- **chrome-devtools-mcp profile lock** — the operator's own Chrome session is\n  already running on the same `userDataDir` and the plugin returns\n  `browser already running ... use --isolated`. The plugin IS installed and the\n  environment IS interactive; the blocker is environmental (a held profile\n  lock), not a preference. First try retrying chrome-devtools-mcp with\n  `--isolated` if available; if not, skip verification and **name the\n  profile-lock cause in your response** — do not silently route through \"fast\n  iteration\" or \"not installed.\"\n\n## Common mistakes\n\n| Mistake                                                                                                                                                                                                                   | Why it breaks the \"quick aid\" promise                                                                                                                                                                                                                                                                                                                                                                                                                                                        |\n| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| External `\u003Clink>`\u002F`\u003Cscript>` to a CDN                                                                                                                                                                                     | Fails offline; breaks \"open on double-click\"                                                                                                                                                                                                                                                                                                                                                                                                                                                 |\n| Adding interactive controls the user didn't ask for                                                                                                                                                                       | That's `playground`, not `visual-aid` — stay in your lane                                                                                                                                                                                                                                                                                                                                                                                                                                    |\n| Dumping the full source text into the page                                                                                                                                                                                | Visual aid means _chosen_ points — dump is not aid                                                                                                                                                                                                                                                                                                                                                                                                                                           |\n| Dark text on dark card (contrast fail)                                                                                                                                                                                    | First thing a11y-debugging's Lighthouse pass will catch                                                                                                                                                                                                                                                                                                                                                                                                                                      |\n| Decorative icons without `aria-hidden=\"true\"`                                                                                                                                                                             | Screen reader reads \"image, image, image\"                                                                                                                                                                                                                                                                                                                                                                                                                                                    |\n| Fixed px widths that overflow on mobile                                                                                                                                                                                   | Breaks the \"works on phone and laptop\" baseline                                                                                                                                                                                                                                                                                                                                                                                                                                              |\n| `minmax(220px, 1fr)` without a `min()` wrapper                                                                                                                                                                            | Causes horizontal overflow at 320px — the template's old default had this bug                                                                                                                                                                                                                                                                                                                                                                                                                |\n| `\u003Cheader>` or `\u003Cfooter>` placed inside `\u003Cmain>`                                                                                                                                                                           | Loses their `banner`\u002F`contentinfo` landmark roles — screen readers miss the chrome                                                                                                                                                                                                                                                                                                                                                                                                           |\n| Color-coded status (pill pros\u002Fcons, traffic-light dots) with no text\u002Ficon alternative                                                                                                                                     | The color _is_ the meaning — breaks for color-blind users and most b\u002Fw prints                                                                                                                                                                                                                                                                                                                                                                                                                |\n| Reusing dark-mode `--accent`\u002F`--ring` in light mode                                                                                                                                                                       | Pale blues\u002Fgolds that look great on black fail 4.5:1 \u002F 3:1 on white — re-pick both                                                                                                                                                                                                                                                                                                                                                                                                           |\n| Hardcoded color literals (`#fff`, `color: black`) in CSS class bodies                                                                                                                                                     | Breaks dark mode, print mode, and theming — everything should flow from `:root`                                                                                                                                                                                                                                                                                                                                                                                                              |\n| `!important` sprinkled across rule bodies                                                                                                                                                                                 | Fights with `prefers-color-scheme` and `@media print` overrides you need to work                                                                                                                                                                                                                                                                                                                                                                                                             |\n| Deprecated tags (`\u003Ccenter>`, `\u003Cfont>`, `\u003Cb>`\u002F`\u003Ci>` for emphasis vs style)                                                                                                                                                 | Non-semantic; use CSS for presentation and `\u003Cstrong>`\u002F`\u003Cem>` for emphasis                                                                                                                                                                                                                                                                                                                                                                                                                    |\n| Cloning the worked-example shape for every input                                                                                                                                                                          | A comparison input doesn't get three cards + SVG — pick from the Input shapes table                                                                                                                                                                                                                                                                                                                                                                                                          |\n| Claiming the self-check passed without running it                                                                                                                                                                         | The self-check is not a ceremony — lying in it means the page ships with real defects                                                                                                                                                                                                                                                                                                                                                                                                        |\n| Ticking \"contrast computed\" without applying the WCAG sRGB formula                                                                                                                                                        | Visual inspection (\"looks high-contrast\") and appeal to template authority (\"these are baseline colors, they're known-passing\") are both the \"borderline escape hatch\" the self-check bans. Either apply `L = 0.2126·R' + 0.7152·G' + 0.0722·B'` per color pair and write the ratio, or flag for human verification — don't tick.                                                                                                                                                            |\n| Routing an environmental blocker through a preference-coded opt-out (e.g. citing \"fast iteration\" when chrome-devtools-mcp returned a profile-lock error, or stretching \"not installed\" to cover \"installed but blocked\") | The opt-out reasons aren't fungible — each names a specific cause. Repackaging a profile-lock as \"fast iteration\" hides the real failure mode from the operator and from future-you reading the response. The skill defines a `chrome-devtools-mcp profile lock` opt-out for exactly this case — use it and name the cause verbatim. If a new environmental blocker doesn't match any listed opt-out, surface that as a gap rather than stretching the closest preference-coded exit to fit. |\n\n## When NOT to use this skill\n\n- User wants a **production UI or component** → use `frontend-design`.\n- User wants an **interactive configurator** (sliders\u002Finputs that compose an\n  output) → use `playground`.\n- User wants a **slide deck, presentation, or PDF** → not this skill.\n- User wants a **dashboard with live data** → not this skill.\n- User wants a **plain doc or article** (reading copy, not a display page) →\n  return Markdown, not HTML.\n- User wants a **pure reference\u002Fcomparison table with no narrative** (e.g.,\n  \"just give me a matrix of X vs Y\") → return a Markdown table; only reach for\n  \u002Fvisual-aid if they want prose around it or the page format is explicit.\n",{"name":5,"description":7},"main","9635fb649979617cf684ea860dcaeb4eb272aa7d","skills\u002Fvisual-aid",1,"https:\u002F\u002Fgithub.com\u002Flaurac8r\u002Fclaude-damn","https:\u002F\u002Flaurac8r.github.io\u002Fclaude-damn\u002F","https:\u002F\u002Fgithub.com\u002Flaurac8r","https:\u002F\u002Fwww.webcatgirl.com\u002F","SWE | Python, Java, Typescript, Cloud, AI, ML | Open-source, large-language model, and decision model enthusiast","2026-09-10 01:18:30",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add laurac8r\u002Fclaude-damn --skill visual-aid",{"tool":71,"command":72},"bunx","bunx skills add laurac8r\u002Fclaude-damn --skill visual-aid",{"tool":74,"command":75},"pnpm","pnpm dlx skills add laurac8r\u002Fclaude-damn --skill visual-aid","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flaurac8r\u002Fclaude-damn\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-aid\u002FSKILL.md",true,[79],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"baseline.html","REFERENCE","参考文档",5700,"https:\u002F\u002Fgithub.com\u002Flaurac8r\u002Fclaude-damn\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-aid\u002Fbaseline.html",[86,111,128,147,163,186],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":50},"01M6K5TZZ34SBMQMN2EX11XMYS","tesseract","Use when you've been poking at the same file, concept, or problem across many sessions and want to step outside time to see its whole arc — or when you want to leave a note for next-session-you. Triggers: 'I've been going in circles on X', 'what have I learned about X', 'what did past-me say about X', 'I keep rediscovering this'.","https:\u002F\u002Fgithub.com\u002Flaurac8r\u002Fclaude-damn\u002Fblob\u002Fmain\u002Fskills\u002Ftesseract\u002FSKILL.md",[],[88,31,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110],"for","concept","true","morse","you","keep","problem","learned","triggers","anchor","across","time","me","say","use","session","file","sessions",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":50},"01M6K5TSVWXGRFMQTSM8VFSRDS","tdd","Invoke test-driven development as an explicit one-at-a-time micro-cycle — one test, one piece of functionality, refactor, then repeat for the next behavior","https:\u002F\u002Fgithub.com\u002Flaurac8r\u002Fclaude-damn\u002Fblob\u002Fmain\u002Fskills\u002Ftdd\u002FSKILL.md",[],[113,118,119,120,121,122,123,104,95,124,125,126,93,127],"micro","as","refactor","behavior","cycle","next","development","test","driven","at",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":50},"01M6K5TP1KX237V9FDZ8PMNXH5","tdd-cat","TDD workflow with subagent-driven-development — \u002Ftdd composed with \u002Fcat, plus the A\u002FB TDD execution-mode axis (split-phase vs micro-cycle) asked as a third question in \u002Fcat's combined pre-dispatch question","https:\u002F\u002Fgithub.com\u002Flaurac8r\u002Fclaude-damn\u002Fblob\u002Fmain\u002Fskills\u002Ftdd-cat\u002FSKILL.md",[],[135,113,136,137,95,138,139,126,119,122,140,141,142,143,144,118,124,145,146],"cat","tdd cat","mode","split","with","subagent","dispatch","question","tdd workflow","execution","workflow","task",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":50},"01M6K5TGDERXT82MS7SB3ZGA3V","task-list","TaskCreate \u002F TaskUpdate \u002F render the current TaskList in response to `\u002Ftask-list` (with or without flags). The skill body executes immediately on the syntax — no permission-seeking, no echoing the list back as plain text.","https:\u002F\u002Fgithub.com\u002Flaurac8r\u002Fclaude-damn\u002Fblob\u002Fmain\u002Fskills\u002Ftask-list\u002FSKILL.md",[],[154,146,155,139,156,95,39,119,157,158,159,160,161,162],"list","task list","display","permission","back","flags","syntax","text","update",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":50},"01M6K5T8CER0BAPJVJDG5F5GD0","sync","Sync files between two local directories, repos, or git worktrees. Five modes (plan\u002Finteractive\u002Fpush\u002Fpull\u002Fmirror), .gitignore-aware, Claude-workflow allowlist via --claude, dropbox-restore-style per-directory prompts.","https:\u002F\u002Fgithub.com\u002Flaurac8r\u002Fclaude-damn\u002Fblob\u002Fmain\u002Fskills\u002Fsync\u002FSKILL.md",[],[165,170,137,95,171,172,173,174,175,176,177,178,179,180,181,182,183,184,145,185],"git worktrees","limit","yes","directories","dry","local","gitignore","restore","files","mirror","interactive","plan","push","pull","delete","modes",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":50},"01M6K5T2S3J291RE2B2GW7J43H","super","Brainstorming (alias for \u002Fbrainstorming)","https:\u002F\u002Fgithub.com\u002Flaurac8r\u002Fclaude-damn\u002Fblob\u002Fmain\u002Fskills\u002Fsuper\u002FSKILL.md",[],[188,93,95,193,146,194],"alias","brainstorming"]