[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BXNWFMVST2VDPYDKJAW994":3,"skill-same:01M7BXNWFMVST2VDPYDKJAW994":53},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7BXNWFMVST2VDPYDKJAW994","glmv-web-replication",null,"Frontend visual replication skill. Explores a target website’s publicly visible pages via Playwright MCP or agent-browser, captures screenshots and layout information, then generates a static or client-side frontend replica that approximates the original’s visual appearance and page structure. This skill replicates FRONTEND PRESENTATION ONLY — it does not reproduce backend logic, server-side behavior, databases, or any non-public content. The user is responsible for ensuring they have proper authorization (ownership, license, or explicit permission) before replicating any website.\n⚠️ Authorization gate: Before starting, the agent MUST confirm with the user that they have the legal right to replicate the target site. If the user cannot confirm, the skill MUST refuse to proceed.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-GLM-skills\u002Fskills\u002Fglmv-web-replication\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: glmv-web-replication\ndescription: >\n  Frontend visual replication skill. Explores a target website’s publicly visible pages\n  via Playwright MCP or agent-browser, captures screenshots and layout information,\n  then generates a static or client-side frontend replica that approximates the original’s\n  visual appearance and page structure. This skill replicates FRONTEND PRESENTATION ONLY —\n  it does not reproduce backend logic, server-side behavior, databases, or any\n  non-public content. The user is responsible for ensuring they have proper authorization\n  (ownership, license, or explicit permission) before replicating any website.\n\n  ⚠️ Authorization gate: Before starting, the agent MUST confirm with the user that\n  they have the legal right to replicate the target site. If the user cannot confirm,\n  the skill MUST refuse to proceed.\n\nread_when:\n  - When the user wants to create a frontend visual replica of a website they own or have explicit permission to replicate\n  - When the user needs a static\u002FHTML approximation of a website’s visual design and layout\n  - When the user wants to study and reproduce a website’s frontend page structure and styling\nallowed-tools: Bash(glmv-web-replication:*)\n---\n\n# Website Frontend Visual Replication\n\n## Prerequisites\nThis workflow depends on either Playwright MCP or the agent-browser skill. As long as at least one of them is installed and available, the workflow can run normally. If neither is available in your environment, remind the user to install one.\n\n## Authorization Gate (MUST execute first)\n\nBefore proceeding, the agent **MUST** ask the user:\n\n> “Do you own this website, or do you have explicit written permission from the owner to replicate it? Unauthorized replication may violate copyright, terms of service, or applicable law.”\n\n- If the user confirms authorization → proceed.\n- If the user cannot confirm → **STOP**. Do not proceed with replication. Suggest alternatives (e.g., building an original design inspired by general layout patterns).\n\n## Scope & Limitations\n\n**This skill replicates FRONTEND VISUAL PRESENTATION only.** Specifically:\n\n| Included | NOT Included |\n|----------|-------------|\n| Page layout & visual styling | Backend \u002F server-side logic |\n| Navigation structure | Databases & data stores |\n| Publicly visible text & images | Authentication systems \u002F sessions |\n| CSS\u002Fdesign tokens | API business logic |\n| Client-side interaction patterns | Non-public or behind-login content |\n| Static asset files (images, fonts) | Credentials, secrets, or API keys |\n\n**Data handling rules:**\n1. **Never scrape behind a login wall.** Only capture publicly accessible pages.\n2. **Never collect or store credentials**, API keys, session tokens, or personal data (PII).\n3. **Never reproduce copyrighted content verbatim** (articles, copy text) unless the user holds rights.\n4. **Respect robots.txt and rate limits.** If the site signals crawl restrictions, honor them.\n5. **Output is for reference & mockup purposes** unless the user has confirmed full rights.\n\n## Core Idea\n1. Recursively explore every **public** page of the target website, systematically record its visual content, client-side interaction logic, and publicly available asset files, and organize everything into a structured “website replication blueprint.” This blueprint should comprehensively include detailed information for each page, and naturally map the site’s navigation relationships through folder hierarchy. Specifically, during exploration, use nested folders to organize and record the collected page information: represent the current page as a folder, and represent all pages reachable from it as child folders. At the same time, save that page’s screenshots, component interaction records, and related asset files inside the page folder. With this structure, the final blueprint will clearly present both the content and interaction details of each page, while also implicitly reflecting the website’s overall information architecture and navigation paths.\n\nAn example blueprint folder structure:\n```text\nblueprint\u002F\n├── _meta.md                      # Site-wide metadata\n├── _sitemap.md                   # Sitemap\n├── _assets\u002F                      # Global assets (fonts, favicon, etc.)\n├── home\u002F                         # Homepage\n│   ├── _page.md                  # Page blueprint (sections, components, interaction summary)\n│   ├── _full.png                 # Full-page screenshot\n│   ├── _scroll_00.png ~ N.png    # Scrolling screenshot sequence\n│   ├── _interactions.md          # Record of all interactions\n│   ├── _interactions\u002F            # Interaction state screenshots (organized by interaction type)\n│   ├── _assets\u002F                  # Assets for this page (images, videos, etc.)\n│   ├── products\u002F                 # \"Product list\" reachable from homepage\n│   │   ├── _page.md\n│   │   ├── _full.png\n│   │   ├── _scroll_00.png ~ N.png \n│   │   ├── _interactions.md\n│   │   ├── _interactions\u002F\n│   │   ├── _assets\u002F\n│   │   ├── product-detail\u002F       # \"Product detail\" reachable from product list\n│   │   │   ├── _page.md\n│   │   │   └── ...\n│   │   └── category\u002F             # \"Category filter\" reachable from product list\n│   │       └── ...\n│   ├── about\u002F                    # \"About us\" reachable from homepage\n│   │   └── ...\n│   ├── blog\u002F                     # \"Blog\" reachable from homepage\n│   │   └── ...\n│   └── login\u002F                    # \"Login\" reachable from homepage\n│       └── ...\n└── _navigation_graph.md          # Site-wide navigation graph (Mermaid)\n```\n\n2. After completing the blueprint construction above, build a **frontend visual replica** of the target website based on that blueprint, approximating the original's page-to-page navigation, visual layout, and client-side interaction patterns. This is a frontend-only reproduction and does not include backend behavior replication.\n\n## Replication Workflow\nThe whole process is divided into five phases: initialization → recursively collect pages and build the sitemap → generate summary outputs → frontend visual replication → visual comparison and revision.\n\nThe first three phases focus on exploration and documentation, while the final two phases focus on implementing the frontend replica based on the collected blueprint and visually verifying it. Below, the agent-browser workflow is used as an example; if using Playwright MCP, the overall process and usage are essentially the same and can be followed with the same approach.\n\n### Step 1: Initialize the project\n```bash\n# Create the blueprint root directory\nmkdir -p blueprint\u002F_assets\n# Open the browser and visit the target site\nagent-browser open \u003Ctarget URL>\nagent-browser set viewport 1920 1080\nagent-browser wait --load networkidle\n```\n\nWrite the following content into `blueprint\u002F_meta.md`:\n```markdown\n# Website Replication Blueprint\n- Target website: \u003CURL>\n- Exploration date: \u003Cdate>\n- Viewport size: 1920×1080\n```\n\n### Step 2: Recursively collect pages and build the sitemap\nFor every recursively discovered page, execute the following standard procedure:\n\nFirst capture a full-page screenshot → download assets → traverse interaction states → scroll down → download assets again → traverse interaction states again → scroll down again → ... → continue until reaching the bottom of the page.\n\n#### 2.1: Asset download\nAfter opening the page and waiting for it to fully load, collect all asset links on the page (images, videos, fonts, etc.) and download them into that page’s `_assets\u002F` directory whenever possible. Record all failed downloads and the reasons for failure.\n\n#### 2.2: Traverse interaction states\nObtain the list of interactive elements on the page, interact with all of them, capture UI changes, and record all newly discovered pages.\n\n```bash\n# === Example using a product list page before any downward scrolling ===\nagent-browser open \u003CProduct List URL>\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002F_scroll_00.png\nagent-browser wait --load networkidle\nagent-browser snapshot -i \n# Suppose the output is:\n# button \"All\" [ref=e1]                ← filter tab\n# button \"Electronics\" [ref=e2]\n# card \"Product A\" [ref=e3]            ← product card\n# select \"Sort\" [ref=e4]               ← sort dropdown\n# link \"Home\" [ref=e5]                 ← breadcrumb link\n# button \"Learn More\" [ref=e6]         ← button inside product card\n# --- Interaction 1: hover over product card ---\nagent-browser hover @e3\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002F_interactions\u002Fcard_hover.png\n# --- Interaction 2: click filter tab ---\nagent-browser click @e2\nagent-browser wait --load networkidle\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002F_interactions\u002Ffilter_electronics.png\n# --- Interaction 3: change sorting ---\nagent-browser select @e4 \"Price: Low to High\"\nagent-browser wait --load networkidle\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002F_interactions\u002Fsort_price_asc.png\n# --- Interaction 4: click product card (triggers navigation) ---\nagent-browser click @e3\nagent-browser wait --load networkidle\nagent-browser get url    # → \u002Fproducts\u002F123\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002Fproduct-detail\u002F_full.png --full\nagent-browser back\n# --- Interaction 5: click breadcrumb \"Home\" ---\nagent-browser click @e5\nagent-browser wait --load networkidle\nagent-browser get url    # → \u002F\nagent-browser screenshot blueprint\u002Fhome\u002F_full.png --full\nagent-browser back\n# --- Interaction 6: click \"Learn More\" button (external navigation) ---\nagent-browser click @e6\nagent-browser wait --load networkidle\nagent-browser get url    # → https:\u002F\u002Fwww.angelokeirsebilck.be\u002F\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002F_interactions\u002Flearn_more_external.png --full\nagent-browser back\n```\n\nWrite the updated sitemap into `blueprint\u002F_sitemap.md`.\n\nWrite the updated page collection results into `blueprint\u002Fhome\u002Fproducts\u002F_page.md`:\n```markdown\n# Product List Page\n- URL: \u002Fproducts\n- Source: Homepage main navigation \"Products\" link\n\n## Section Structure\n| No. | Section Name | Layout Pattern | Content Type |\n|------|--------------|----------------|--------------|\n| 1 | Page header | Full-width single column | H1 heading + descriptive text |\n| 2 | Filter bar | Horizontal layout | Category tabs + sorting dropdown |\n| 3 | Product grid | 3-column grid | Product cards × N |\n| 4 | Pagination | Centered single column | Pagination button group |\n\n## Screenshots\n- Full page: ![Full page screenshot](.\u002F_full.png)\n- Scroll sequence: ![Screen 1](.\u002F_scroll_00.png) ![Screen 2](.\u002F_scroll_01.png)\n\n## Outbound Navigation\n| Trigger Element | Trigger Method | Target | Child Folder |\n|----------------|----------------|--------|--------------|\n| Product card | Click | \u002Fproducts\u002F:id | .\u002Fproduct-detail\u002F |\n| Category tab | Click | \u002Fproducts\u002Fcategory\u002F:slug | .\u002Fcategory\u002F |\n| Breadcrumb \"Home\" | Click | \u002F | (return to parent) |\n| Learn More button | Click | https:\u002F\u002Fwww.angelokeirsebilck.be\u002F | None |\n\n## Page Assets\n| File | Purpose |\n|------|---------|\n| _assets\u002Fproduct-01.jpg | Product card thumbnail |\n| _assets\u002Fproduct-02.jpg | Product card thumbnail |\n```\n\nWrite all updated interactions into `blueprint\u002Fhome\u002Fproducts\u002F_interactions.md`:\n```markdown\n# Product List Page - Interaction Behavior\n\n## Interaction List\n| Element | Trigger Method | Behavior | Navigation | Screenshot |\n|---------|----------------|----------|------------|------------|\n| Product card | hover | Card rises + shadow deepens | No | ![](.\u002F_interactions\u002Fcard_hover.png) |\n| Product card | click | Navigates to product detail | Yes → .\u002Fproduct-detail\u002F | — |\n| Filter tab \"Electronics\" | click | List refreshes to electronics category | No (AJAX) | ![](.\u002F_interactions\u002Ffilter_electronics.png) |\n| Sort dropdown | select | Product list reorders | No (AJAX) | ![](.\u002F_interactions\u002Fsort_price_asc.png) |\n| Breadcrumb \"Home\" | click | Navigates to homepage | Yes → ..\u002F | — |\n| Learn More button | click | Opens external link | Yes → https:\u002F\u002Fwww.angelokeirsebilck.be\u002F | — |\n\n## State Transitions\nDefault list --[click filter tab]--> Filtered list\nDefault list --[change sorting]--> Sorted list\nProduct card (default) --[hover]--> Product card (hover state)\nProduct card --[click]--> \u002Fproducts\u002F:id (navigation)\nLearn More button --[click]--> External link (navigation to https:\u002F\u002Fwww.angelokeirsebilck.be\u002F)\n```\n\n### Step 3: Generate summary outputs\nAfter all page collection is complete, generate the global summary files.\n\n#### `blueprint\u002F_sitemap.md`\n```markdown\n# Sitemap\nhome\u002F                          # \u002F (homepage)\n├── products\u002F                  # \u002Fproducts (product list)\n│   ├── product-detail\u002F        # \u002Fproducts\u002F:id (product detail)\n│   └── category\u002F              # \u002Fproducts\u002Fcategory\u002F:slug (category)\n├── about\u002F                     # \u002Fabout (about us)\n├── blog\u002F                      # \u002Fblog (blog list)\n│   └── blog-post\u002F             # \u002Fblog\u002F:slug (blog post)\n├── contact\u002F                   # \u002Fcontact (contact us)\n└── login\u002F                     # \u002Fauth\u002Flogin (login)\n    └── register\u002F              # \u002Fauth\u002Fregister (register)\n```\n\n#### `blueprint\u002F_navigation_graph.md`\n```markdown\n# Site-wide Navigation Graph\ngraph LR\n    Home[\"home \u002F\"] -->|Nav - Products| Products[\"products \u002Fproducts\"]\n    Home -->|Nav - About| About[\"about \u002Fabout\"]\n    Home -->|Nav - Blog| Blog[\"blog \u002Fblog\"]\n    Home -->|Header - Login| Login[\"login \u002Fauth\u002Flogin\"]\n    Products -->|Card click| Detail[\"product-detail \u002Fproducts\u002F:id\"]\n    Products -->|Filter tab| Category[\"category \u002Fproducts\u002Fcategory\u002F:slug\"]\n    Blog -->|Post card| Post[\"blog-post \u002Fblog\u002F:slug\"]\n    Login -->|Register link| Register[\"register \u002Fauth\u002Fregister\"]\n\n## Navigation Details\n| ID | Source Folder | Trigger Element | Target Folder | Navigation Type |\n|----|---------------|----------------|---------------|-----------------|\n| N001 | home\u002F | Main nav \"Products\" | home\u002Fproducts\u002F | Internal |\n| N002 | home\u002F | Hero CTA button | home\u002Fproducts\u002F | Internal |\n| N003 | home\u002Fproducts\u002F | Product card | home\u002Fproducts\u002Fproduct-detail\u002F | Internal |\n| N004 | home\u002Fproducts\u002F | Category tab \"Electronics\" | home\u002Fproducts\u002Fcategory\u002F | Internal |\n| N005 | home\u002Fproducts\u002F | Breadcrumb \"Home\" | home\u002F | Internal |\n| N006 | home\u002Fproducts\u002F | Learn More button | External link https:\u002F\u002Fwww.angelokeirsebilck.be\u002F | External |\n| ... | ... | ... | ... | ... |\n```\n\n#### Close the browser\n```bash\nagent-browser close\n```\n\n### Step 4: Frontend Visual Replication\nAfter completing website exploration and blueprint generation, build a **frontend visual replica** based on the collected blueprint. During replication, refer to the blueprint’s page structures, visual styles, and publicly available assets, and use your preferred frontend tools and frameworks to rebuild the website’s client-side presentation. The goal is to approximate the original’s visual design and navigation — not to reproduce backend behavior or non-public functionality.\n\n### Step 5: Visual Comparison & Revision\nAfter finishing the frontend replication, use Playwright MCP or the agent-browser skill to render both the original website and the replicated version, systematically compare them for visual consistency in layout, colors, typography, and navigation structure, verify the degree of visual approximation page by page, and make adjustments based on the comparison results.\n\n## Key Rules\n1. **Authorization first.** Never begin replication without user confirmation of legal right to replicate.\n2. **Public pages only.** Only explore and capture publicly accessible pages. Do not attempt to access login-protected areas, admin panels, or authenticated endpoints.\n3. **No credential\u002FPII handling.** If any captured content contains credentials, tokens, or personal data, redact or exclude it immediately.\n4. **Frontend only.** Never claim or attempt to replicate backend business logic, database schemas, or server-side behavior.\n5. Folders represent navigation relationships. If page A can navigate to page B, then page B should be created as a subfolder inside page A’s folder.\n6. If multiple pages can navigate to the same target page, you may skip redundant exploration of that page and create its folder only once under the most natural parent. However, all navigation sources must still be recorded in `_sitemap.md`, `_navigation_graph.md`, and the related pages’ `_page.md` files.\n7. Every folder must contain:\n   - `_page.md` — page blueprint (sections, components, outbound navigation)\n   - `_full.png` — full-page screenshot\n   - `_interactions.md` — interaction behavior record\n   - `_interactions\u002F` — directory for interaction state screenshots\n   - `_assets\u002F` — page-specific assets\n   - scrolling screenshot sequence `_scroll_00.png` ~ `_scroll_N.png`\n8. Screenshots must be captured from the real site. Do not describe visual information from memory; all visual details must be based on actual screenshots.\n9. Interactions must be genuinely triggered and recorded one by one, including hover, click, focus, and so on.\n10. Assets should be downloaded whenever possible. Use `curl` to download images, and use `agent-browser eval` or Playwright MCP to extract SVG source code and save it. All failed downloads must be recorded together with the reasons for failure.\n11. Record only; do not evaluate. Accurately document observed results without making quality judgments.\n12. Keep files updated in real time. After finishing exploration of each page window, update the sitemap and all related blueprint files such as `_page.md` and `_interactions.md` so the output always remains synchronized with the current exploration state.\n13. Ensure elements are visible. Before interacting with any page element, make sure the target element is within the visible viewport. Scroll the page or adjust the viewport position if necessary.\n14. Each call to `agent-browser` may execute only one command, such as taking a screenshot, getting the element list, or performing one interaction. Do not combine multiple commands in a single call. The consecutive commands in the example are only for illustrating the workflow; in actual execution they must be split into separate calls.\n15. If interaction with a webpage element triggers navigation to an external domain, there is no need to deeply explore or continue scraping that external page. However, you must record the key information of that external link, including the external URL, the page element that triggered the link (text\u002Fbutton name\u002Fselector or ref), and the trigger method (such as click). In the replicated website, the corresponding page element should preserve the same trigger method and external destination.\n16. `_full.png` is used to record the overall visual overview of the page, while the scrolling screenshot sequence (`_scroll_00.png` ~ `_scroll_N.png`) can record details of each segment. During website replication, both the overall information from the full-page screenshot and the detailed information from the scrolling screenshot sequence should be referenced together to ensure accurate visual reproduction and complete detail restoration.","# Website Frontend Visual Replication\n\n## Prerequisites\nThis workflow depends on either Playwright MCP or the agent-browser skill. As long as at least one of them is installed and available, the workflow can run normally. If neither is available in your environment, remind the user to install one.\n\n## Authorization Gate (MUST execute first)\n\nBefore proceeding, the agent **MUST** ask the user:\n\n> “Do you own this website, or do you have explicit written permission from the owner to replicate it? Unauthorized replication may violate copyright, terms of service, or applicable law.”\n\n- If the user confirms authorization → proceed.\n- If the user cannot confirm → **STOP**. Do not proceed with replication. Suggest alternatives (e.g., building an original design inspired by general layout patterns).\n\n## Scope & Limitations\n\n**This skill replicates FRONTEND VISUAL PRESENTATION only.** Specifically:\n\n| Included | NOT Included |\n|----------|-------------|\n| Page layout & visual styling | Backend \u002F server-side logic |\n| Navigation structure | Databases & data stores |\n| Publicly visible text & images | Authentication systems \u002F sessions |\n| CSS\u002Fdesign tokens | API business logic |\n| Client-side interaction patterns | Non-public or behind-login content |\n| Static asset files (images, fonts) | Credentials, secrets, or API keys |\n\n**Data handling rules:**\n1. **Never scrape behind a login wall.** Only capture publicly accessible pages.\n2. **Never collect or store credentials**, API keys, session tokens, or personal data (PII).\n3. **Never reproduce copyrighted content verbatim** (articles, copy text) unless the user holds rights.\n4. **Respect robots.txt and rate limits.** If the site signals crawl restrictions, honor them.\n5. **Output is for reference & mockup purposes** unless the user has confirmed full rights.\n\n## Core Idea\n1. Recursively explore every **public** page of the target website, systematically record its visual content, client-side interaction logic, and publicly available asset files, and organize everything into a structured “website replication blueprint.” This blueprint should comprehensively include detailed information for each page, and naturally map the site’s navigation relationships through folder hierarchy. Specifically, during exploration, use nested folders to organize and record the collected page information: represent the current page as a folder, and represent all pages reachable from it as child folders. At the same time, save that page’s screenshots, component interaction records, and related asset files inside the page folder. With this structure, the final blueprint will clearly present both the content and interaction details of each page, while also implicitly reflecting the website’s overall information architecture and navigation paths.\n\nAn example blueprint folder structure:\n```text\nblueprint\u002F\n├── _meta.md                      # Site-wide metadata\n├── _sitemap.md                   # Sitemap\n├── _assets\u002F                      # Global assets (fonts, favicon, etc.)\n├── home\u002F                         # Homepage\n│   ├── _page.md                  # Page blueprint (sections, components, interaction summary)\n│   ├── _full.png                 # Full-page screenshot\n│   ├── _scroll_00.png ~ N.png    # Scrolling screenshot sequence\n│   ├── _interactions.md          # Record of all interactions\n│   ├── _interactions\u002F            # Interaction state screenshots (organized by interaction type)\n│   ├── _assets\u002F                  # Assets for this page (images, videos, etc.)\n│   ├── products\u002F                 # \"Product list\" reachable from homepage\n│   │   ├── _page.md\n│   │   ├── _full.png\n│   │   ├── _scroll_00.png ~ N.png \n│   │   ├── _interactions.md\n│   │   ├── _interactions\u002F\n│   │   ├── _assets\u002F\n│   │   ├── product-detail\u002F       # \"Product detail\" reachable from product list\n│   │   │   ├── _page.md\n│   │   │   └── ...\n│   │   └── category\u002F             # \"Category filter\" reachable from product list\n│   │       └── ...\n│   ├── about\u002F                    # \"About us\" reachable from homepage\n│   │   └── ...\n│   ├── blog\u002F                     # \"Blog\" reachable from homepage\n│   │   └── ...\n│   └── login\u002F                    # \"Login\" reachable from homepage\n│       └── ...\n└── _navigation_graph.md          # Site-wide navigation graph (Mermaid)\n```\n\n2. After completing the blueprint construction above, build a **frontend visual replica** of the target website based on that blueprint, approximating the original's page-to-page navigation, visual layout, and client-side interaction patterns. This is a frontend-only reproduction and does not include backend behavior replication.\n\n## Replication Workflow\nThe whole process is divided into five phases: initialization → recursively collect pages and build the sitemap → generate summary outputs → frontend visual replication → visual comparison and revision.\n\nThe first three phases focus on exploration and documentation, while the final two phases focus on implementing the frontend replica based on the collected blueprint and visually verifying it. Below, the agent-browser workflow is used as an example; if using Playwright MCP, the overall process and usage are essentially the same and can be followed with the same approach.\n\n### Step 1: Initialize the project\n```bash\n# Create the blueprint root directory\nmkdir -p blueprint\u002F_assets\n# Open the browser and visit the target site\nagent-browser open \u003Ctarget URL>\nagent-browser set viewport 1920 1080\nagent-browser wait --load networkidle\n```\n\nWrite the following content into `blueprint\u002F_meta.md`:\n```markdown\n# Website Replication Blueprint\n- Target website: \u003CURL>\n- Exploration date: \u003Cdate>\n- Viewport size: 1920×1080\n```\n\n### Step 2: Recursively collect pages and build the sitemap\nFor every recursively discovered page, execute the following standard procedure:\n\nFirst capture a full-page screenshot → download assets → traverse interaction states → scroll down → download assets again → traverse interaction states again → scroll down again → ... → continue until reaching the bottom of the page.\n\n#### 2.1: Asset download\nAfter opening the page and waiting for it to fully load, collect all asset links on the page (images, videos, fonts, etc.) and download them into that page’s `_assets\u002F` directory whenever possible. Record all failed downloads and the reasons for failure.\n\n#### 2.2: Traverse interaction states\nObtain the list of interactive elements on the page, interact with all of them, capture UI changes, and record all newly discovered pages.\n\n```bash\n# === Example using a product list page before any downward scrolling ===\nagent-browser open \u003CProduct List URL>\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002F_scroll_00.png\nagent-browser wait --load networkidle\nagent-browser snapshot -i \n# Suppose the output is:\n# button \"All\" [ref=e1]                ← filter tab\n# button \"Electronics\" [ref=e2]\n# card \"Product A\" [ref=e3]            ← product card\n# select \"Sort\" [ref=e4]               ← sort dropdown\n# link \"Home\" [ref=e5]                 ← breadcrumb link\n# button \"Learn More\" [ref=e6]         ← button inside product card\n# --- Interaction 1: hover over product card ---\nagent-browser hover @e3\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002F_interactions\u002Fcard_hover.png\n# --- Interaction 2: click filter tab ---\nagent-browser click @e2\nagent-browser wait --load networkidle\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002F_interactions\u002Ffilter_electronics.png\n# --- Interaction 3: change sorting ---\nagent-browser select @e4 \"Price: Low to High\"\nagent-browser wait --load networkidle\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002F_interactions\u002Fsort_price_asc.png\n# --- Interaction 4: click product card (triggers navigation) ---\nagent-browser click @e3\nagent-browser wait --load networkidle\nagent-browser get url    # → \u002Fproducts\u002F123\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002Fproduct-detail\u002F_full.png --full\nagent-browser back\n# --- Interaction 5: click breadcrumb \"Home\" ---\nagent-browser click @e5\nagent-browser wait --load networkidle\nagent-browser get url    # → \u002F\nagent-browser screenshot blueprint\u002Fhome\u002F_full.png --full\nagent-browser back\n# --- Interaction 6: click \"Learn More\" button (external navigation) ---\nagent-browser click @e6\nagent-browser wait --load networkidle\nagent-browser get url    # → https:\u002F\u002Fwww.angelokeirsebilck.be\u002F\nagent-browser screenshot blueprint\u002Fhome\u002Fproducts\u002F_interactions\u002Flearn_more_external.png --full\nagent-browser back\n```\n\nWrite the updated sitemap into `blueprint\u002F_sitemap.md`.\n\nWrite the updated page collection results into `blueprint\u002Fhome\u002Fproducts\u002F_page.md`:\n```markdown\n# Product List Page\n- URL: \u002Fproducts\n- Source: Homepage main navigation \"Products\" link\n\n## Section Structure\n| No. | Section Name | Layout Pattern | Content Type |\n|------|--------------|----------------|--------------|\n| 1 | Page header | Full-width single column | H1 heading + descriptive text |\n| 2 | Filter bar | Horizontal layout | Category tabs + sorting dropdown |\n| 3 | Product grid | 3-column grid | Product cards × N |\n| 4 | Pagination | Centered single column | Pagination button group |\n\n## Screenshots\n- Full page: ![Full page screenshot](.\u002F_full.png)\n- Scroll sequence: ![Screen 1](.\u002F_scroll_00.png) ![Screen 2](.\u002F_scroll_01.png)\n\n## Outbound Navigation\n| Trigger Element | Trigger Method | Target | Child Folder |\n|----------------|----------------|--------|--------------|\n| Product card | Click | \u002Fproducts\u002F:id | .\u002Fproduct-detail\u002F |\n| Category tab | Click | \u002Fproducts\u002Fcategory\u002F:slug | .\u002Fcategory\u002F |\n| Breadcrumb \"Home\" | Click | \u002F | (return to parent) |\n| Learn More button | Click | https:\u002F\u002Fwww.angelokeirsebilck.be\u002F | None |\n\n## Page Assets\n| File | Purpose |\n|------|---------|\n| _assets\u002Fproduct-01.jpg | Product card thumbnail |\n| _assets\u002Fproduct-02.jpg | Product card thumbnail |\n```\n\nWrite all updated interactions into `blueprint\u002Fhome\u002Fproducts\u002F_interactions.md`:\n```markdown\n# Product List Page - Interaction Behavior\n\n## Interaction List\n| Element | Trigger Method | Behavior | Navigation | Screenshot |\n|---------|----------------|----------|------------|------------|\n| Product card | hover | Card rises + shadow deepens | No | ![](.\u002F_interactions\u002Fcard_hover.png) |\n| Product card | click | Navigates to product detail | Yes → .\u002Fproduct-detail\u002F | — |\n| Filter tab \"Electronics\" | click | List refreshes to electronics category | No (AJAX) | ![](.\u002F_interactions\u002Ffilter_electronics.png) |\n| Sort dropdown | select | Product list reorders | No (AJAX) | ![](.\u002F_interactions\u002Fsort_price_asc.png) |\n| Breadcrumb \"Home\" | click | Navigates to homepage | Yes → ..\u002F | — |\n| Learn More button | click | Opens external link | Yes → https:\u002F\u002Fwww.angelokeirsebilck.be\u002F | — |\n\n## State Transitions\nDefault list --[click filter tab]--> Filtered list\nDefault list --[change sorting]--> Sorted list\nProduct card (default) --[hover]--> Product card (hover state)\nProduct card --[click]--> \u002Fproducts\u002F:id (navigation)\nLearn More button --[click]--> External link (navigation to https:\u002F\u002Fwww.angelokeirsebilck.be\u002F)\n```\n\n### Step 3: Generate summary outputs\nAfter all page collection is complete, generate the global summary files.\n\n#### `blueprint\u002F_sitemap.md`\n```markdown\n# Sitemap\nhome\u002F                          # \u002F (homepage)\n├── products\u002F                  # \u002Fproducts (product list)\n│   ├── product-detail\u002F        # \u002Fproducts\u002F:id (product detail)\n│   └── category\u002F              # \u002Fproducts\u002Fcategory\u002F:slug (category)\n├── about\u002F                     # \u002Fabout (about us)\n├── blog\u002F                      # \u002Fblog (blog list)\n│   └── blog-post\u002F             # \u002Fblog\u002F:slug (blog post)\n├── contact\u002F                   # \u002Fcontact (contact us)\n└── login\u002F                     # \u002Fauth\u002Flogin (login)\n    └── register\u002F              # \u002Fauth\u002Fregister (register)\n```\n\n#### `blueprint\u002F_navigation_graph.md`\n```markdown\n# Site-wide Navigation Graph\ngraph LR\n    Home[\"home \u002F\"] -->|Nav - Products| Products[\"products \u002Fproducts\"]\n    Home -->|Nav - About| About[\"about \u002Fabout\"]\n    Home -->|Nav - Blog| Blog[\"blog \u002Fblog\"]\n    Home -->|Header - Login| Login[\"login \u002Fauth\u002Flogin\"]\n    Products -->|Card click| Detail[\"product-detail \u002Fproducts\u002F:id\"]\n    Products -->|Filter tab| Category[\"category \u002Fproducts\u002Fcategory\u002F:slug\"]\n    Blog -->|Post card| Post[\"blog-post \u002Fblog\u002F:slug\"]\n    Login -->|Register link| Register[\"register \u002Fauth\u002Fregister\"]\n\n## Navigation Details\n| ID | Source Folder | Trigger Element | Target Folder | Navigation Type |\n|----|---------------|----------------|---------------|-----------------|\n| N001 | home\u002F | Main nav \"Products\" | home\u002Fproducts\u002F | Internal |\n| N002 | home\u002F | Hero CTA button | home\u002Fproducts\u002F | Internal |\n| N003 | home\u002Fproducts\u002F | Product card | home\u002Fproducts\u002Fproduct-detail\u002F | Internal |\n| N004 | home\u002Fproducts\u002F | Category tab \"Electronics\" | home\u002Fproducts\u002Fcategory\u002F | Internal |\n| N005 | home\u002Fproducts\u002F | Breadcrumb \"Home\" | home\u002F | Internal |\n| N006 | home\u002Fproducts\u002F | Learn More button | External link https:\u002F\u002Fwww.angelokeirsebilck.be\u002F | External |\n| ... | ... | ... | ... | ... |\n```\n\n#### Close the browser\n```bash\nagent-browser close\n```\n\n### Step 4: Frontend Visual Replication\nAfter completing website exploration and blueprint generation, build a **frontend visual replica** based on the collected blueprint. During replication, refer to the blueprint’s page structures, visual styles, and publicly available assets, and use your preferred frontend tools and frameworks to rebuild the website’s client-side presentation. The goal is to approximate the original’s visual design and navigation — not to reproduce backend behavior or non-public functionality.\n\n### Step 5: Visual Comparison & Revision\nAfter finishing the frontend replication, use Playwright MCP or the agent-browser skill to render both the original website and the replicated version, systematically compare them for visual consistency in layout, colors, typography, and navigation structure, verify the degree of visual approximation page by page, and make adjustments based on the comparison results.\n\n## Key Rules\n1. **Authorization first.** Never begin replication without user confirmation of legal right to replicate.\n2. **Public pages only.** Only explore and capture publicly accessible pages. Do not attempt to access login-protected areas, admin panels, or authenticated endpoints.\n3. **No credential\u002FPII handling.** If any captured content contains credentials, tokens, or personal data, redact or exclude it immediately.\n4. **Frontend only.** Never claim or attempt to replicate backend business logic, database schemas, or server-side behavior.\n5. Folders represent navigation relationships. If page A can navigate to page B, then page B should be created as a subfolder inside page A’s folder.\n6. If multiple pages can navigate to the same target page, you may skip redundant exploration of that page and create its folder only once under the most natural parent. However, all navigation sources must still be recorded in `_sitemap.md`, `_navigation_graph.md`, and the related pages’ `_page.md` files.\n7. Every folder must contain:\n   - `_page.md` — page blueprint (sections, components, outbound navigation)\n   - `_full.png` — full-page screenshot\n   - `_interactions.md` — interaction behavior record\n   - `_interactions\u002F` — directory for interaction state screenshots\n   - `_assets\u002F` — page-specific assets\n   - scrolling screenshot sequence `_scroll_00.png` ~ `_scroll_N.png`\n8. Screenshots must be captured from the real site. Do not describe visual information from memory; all visual details must be based on actual screenshots.\n9. Interactions must be genuinely triggered and recorded one by one, including hover, click, focus, and so on.\n10. Assets should be downloaded whenever possible. Use `curl` to download images, and use `agent-browser eval` or Playwright MCP to extract SVG source code and save it. All failed downloads must be recorded together with the reasons for failure.\n11. Record only; do not evaluate. Accurately document observed results without making quality judgments.\n12. Keep files updated in real time. After finishing exploration of each page window, update the sitemap and all related blueprint files such as `_page.md` and `_interactions.md` so the output always remains synchronized with the current exploration state.\n13. Ensure elements are visible. Before interacting with any page element, make sure the target element is within the visible viewport. Scroll the page or adjust the viewport position if necessary.\n14. Each call to `agent-browser` may execute only one command, such as taking a screenshot, getting the element list, or performing one interaction. Do not combine multiple commands in a single call. The consecutive commands in the example are only for illustrating the workflow; in actual execution they must be split into separate calls.\n15. If interaction with a webpage element triggers navigation to an external domain, there is no need to deeply explore or continue scraping that external page. However, you must record the key information of that external link, including the external URL, the page element that triggered the link (text\u002Fbutton name\u002Fselector or ref), and the trigger method (such as click). In the replicated website, the corresponding page element should preserve the same trigger method and external destination.\n16. `_full.png` is used to record the overall visual overview of the page, while the scrolling screenshot sequence (`_scroll_00.png` ~ `_scroll_N.png`) can record details of each segment. During website replication, both the overall information from the full-page screenshot and the detailed information from the scrolling screenshot sequence should be referenced together to ensure accurate visual reproduction and complete detail restoration.",{"name":5,"read_when":24,"description":28,"allowed-tools":29},[25,26,27],"When the user wants to create a frontend visual replica of a website they own or have explicit permission to replicate","When the user needs a static\u002FHTML approximation of a website’s visual design and layout","When the user wants to study and reproduce a website’s frontend page structure and styling","Frontend visual replication skill. Explores a target website’s publicly visible pages via Playwright MCP or agent-browser, captures screenshots and layout information, then generates a static or client-side frontend replica that approximates the original’s visual appearance and page structure. This skill replicates FRONTEND PRESENTATION ONLY — it does not reproduce backend logic, server-side behavior, databases, or any non-public content. The user is responsible for ensuring they have proper authorization (ownership, license, or explicit permission) before replicating any website.\n⚠️ Authorization gate: Before starting, the agent MUST confirm with the user that they have the legal right to replicate the target site. If the user cannot confirm, the skill MUST refuse to proceed.\n","Bash(glmv-web-replication:*)","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-GLM-skills\u002Fskills\u002Fglmv-web-replication",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill glmv-web-replication",{"tool":45,"command":46},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill glmv-web-replication",{"tool":48,"command":49},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill glmv-web-replication","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-GLM-skills\u002Fskills\u002Fglmv-web-replication\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]