跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

website-to-design-md

Generate a reusable design.md or DESIGN.md from a live website by deeply inspecting the site with `agent-browser` and `agent-browser eval`, then synthesizing its visual language, layout system, interaction patterns, and content style into a structured markdown design system. Use when given one or more website URLs and asked to analyze a site, reverse-engineer its design, extract its look and feel, write DESIGN.md, create a style guide, or capture a site's UI rules for later AI-assisted design or implementation. Prefer this skill when the goal is documentation rather than rebuilding the page in code. Always use `agent-browser` as the primary browser runtime; if it is missing, help the user install or expose it instead of switching platforms or browser stacks.

Paidax01 · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Paidax01/web-to-design-md --skill website-to-design-md

技能说明


name: website-to-design-md description: Generate a reusable design.md or DESIGN.md from a live website by deeply inspecting the site with agent-browser and agent-browser eval, then synthesizing its visual language, layout system, interaction patterns, and content style into a structured markdown design system. Use when given one or more website URLs and asked to analyze a site, reverse-engineer its design, extract its look and feel, write DESIGN.md, create a style guide, or capture a site's UI rules for later AI-assisted design or implementation. Prefer this skill when the goal is documentation rather than rebuilding the page in code. Always use agent-browser as the primary browser runtime; if it is missing, help the user install or expose it instead of switching platforms or browser stacks.

Website to DESIGN.md

Overview

Use this skill to turn a real website into a reusable design.md or DESIGN.md document plus a companion HTML preview.

The goal is not to clone the site. The goal is to inspect it deeply enough that another agent can recreate the same design language, content tone, and interaction feel without needing to see the original website.

The HTML preview is a practical review surface. It should translate the markdown into a glanceable design board so the user can inspect palette, typography, spacing, component cues, and the raw markdown source without reopening the site.

Universal Browser Rule

This skill should always use agent-browser first.

  • Use agent-browser open, agent-browser wait, and especially agent-browser eval as the primary extraction workflow.
  • Do not start by checking which app or platform the user is on.
  • Do not branch logic based on whether the user is using Codex, Trae, Claude, Cursor, or another host.
  • Do not start by checking whether the current project folder contains Playwright, Chrome CLI, or a local browser package.
  • If agent-browser is unavailable, help the user install it or expose it on PATH, then continue with the same workflow.
  • Do not silently switch to Playwright, Chrome CLI, or screenshot-led extraction unless the user explicitly asks for a separate fallback.

Working Style

Work browser-first and evidence-first.

  • Prefer agent-browser over raw HTML fetches. A live website often hides important behavior behind hydration, scroll state, hover state, or responsive layout changes.
  • Treat agent-browser eval as the primary extraction layer. The main evidence should come from DOM structure, rendered HTML, computed styles, CSS variables, readable stylesheet rules, and interaction states gathered inside the browser runtime.
  • Do not use screenshots as a default evidence source. When agent-browser eval or an equivalent page-eval path is available, use DOM, computed styles, CSS variables, readable stylesheet rules, and extracted text as the primary evidence.
  • Only use screenshots as an optional last-resort cross-check when DOM evidence is insufficient or the user explicitly asks for a visual verification pass.
  • Do not silently fall back to Playwright or Chrome CLI. If agent-browser is unavailable, detect that explicitly and help the user install or expose it.
  • Treat static source files as supporting evidence, not the main truth source.
  • Translate technical details into design language. Do not dump CSS blindly; synthesize it into something an agent can actually use.
  • Distinguish observed facts from inference. If something is a judgment or a likely rule rather than a directly observed value, label it clearly.
  • Treat the HTML preview as part of the default deliverable, not as an optional extra, unless the user explicitly opts out.

Preflight

  1. Normalize the target into one or more URLs.
  2. Check whether agent-browser is already usable.
  3. If agent-browser is missing, use scripts/check-browser-tooling.mjs and then help the user install or expose agent-browser.
  4. Do not inspect the current folder for Playwright, Chrome CLI, or local browser executables as the primary path.
  5. Do not silently fall back to Playwright or Chrome CLI unless the user explicitly asks for that fallback.
  6. Default the markdown output file to DESIGN.md.
  7. Default the companion preview file to the same basename plus -preview.html, for example DESIGN-preview.html or design-preview.html.
  8. If the user explicitly asks for design.md, a custom filename, or a custom folder, honor that exactly and keep the HTML preview beside it unless the user asks not to.
  9. If multiple URLs are provided, inspect each independently, then synthesize one shared design system only when the visual language is clearly consistent across pages.

Browser Tooling Bootstrap

Treat browser tooling setup as part of the skill, not as a separate user chore.

Detection

Check in this order:

  • whether agent-browser is already callable
  • if not, whether it can be installed or exposed immediately

The bundled checker script reports:

  • whether node and npm are available
  • whether agent-browser is callable
  • which tool should be used next
  • whether installation is recommended

Installation Default

If agent-browser is unavailable, help the user install it or expose it on PATH, and verify it with agent-browser --help before using the skill.

Installation Behavior

  • Explain that installation is needed so the skill can consistently use agent-browser.
  • If the first install attempt fails because of network or sandbox restrictions, request the needed approval and retry.
  • If installation succeeds, continue directly into site analysis in the same turn.
  • If installation fails, tell the user clearly what is missing and stop rather than silently switching to a different extractor.
  • Do not silently downgrade to static HTML scraping just because tooling is absent.

Required Extraction Passes

Use the checklist in [references/website-reading-checklist.md](references/website-read

阅读完整来源 ↗