[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78A46TYGST3N2BEKBY9CMWP":3,"skill-same:01M78A46TYGST3N2BEKBY9CMWP":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M78A46TYGST3N2BEKBY9CMWP","od-web-effect-extractor",null,"Extract visual effects, animation systems, Canvas\u002FWebGL\u002FShader behavior, and interaction details from a reference website, then rebuild them as an editable Open Design web artifact.","bluesman1971\u002Fopen-design","bluesman1971","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96430007?v=4","01M788AK0TR13JE8ART2WNQZV6","01M788AK1PVB085AS9SP38WWGK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fscenarios\u002Fod-web-effect-extractor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: od-web-effect-extractor\ndescription: Extract visual effects, animation systems, Canvas\u002FWebGL\u002FShader behavior, and interaction details from a reference website, then rebuild them as an editable Open Design web artifact.\nod:\n  scenario: web-effect-extraction\n  mode: scenario\n---\n\n# Web Effect Extractor\n\nUse this plugin when the user gives a website URL and asks Open Design to recreate, remix, or learn from its visual effects. It is especially useful for hero backgrounds, WebGL scenes, Canvas animations, shader effects, cursor trails, scroll-driven motion, animated typography, and interaction patterns that are hard to understand from screenshots alone.\n\nThis workflow is inspired by the MIT-licensed `web-shader-extractor` skill from `lixiaolin94\u002Fskills`, adapted for Open Design's website recreation and editable artifact workflow.\n\n## Scope\n\nThe goal is to produce a faithful, editable Open Design artifact that preserves the reference site's visual effect and interaction logic while replacing private content, trademarks, tracking code, and nonessential app logic.\n\nExtract only what is needed to understand and recreate the visual behavior:\n\n- Layout structure, viewport behavior, breakpoints, and composition rhythm\n- Color, typography, blend modes, gradients, texture, lighting, and post-processing\n- Motion timing, easing, scroll triggers, pointer response, and idle animation loops\n- Canvas, WebGL, Three.js, shader, particle, and framebuffer pipeline details\n- Public static assets needed for visual parity, with provenance noted\n\nDo not copy private product copy, hidden application state, user data, analytics, auth flows, or unrelated business logic.\n\n## Workflow\n\n### 1. Prepare The Capture\n\nStart from the supplied URL and define the exact effect to recreate. If the user is vague, inspect the first viewport first and infer the likely target effect.\n\nBefore extracting runtime details, prefer a browser context that can evaluate page scripts and inspect canvas\u002FWebGL state. If Chrome DevTools MCP is available, use it for runtime interception. If it is not available, continue with the strongest available browser automation and clearly state that shader\u002Fruntime capture may be incomplete.\n\nRecord:\n\n- URL and capture timestamp\n- Viewport sizes to test, usually desktop and mobile\n- Main effect target and fallback effect targets\n- Framework clues from HTML, network requests, globals, and package signatures\n\n### 2. Runtime Inspection\n\nCapture runtime evidence before simplifying anything.\n\nInspect:\n\n- DOM tree, computed styles, fonts, CSS variables, custom properties, and animation names\n- Canvas elements, WebGL contexts, renderer attributes, supported extensions, and resolution scaling\n- Global framework markers such as `THREE`, `BABYLON`, `__NEXT_DATA__`, `__NUXT__`, `vite`, GSAP, Lenis, Framer Motion, or custom scene globals\n- Networked JS bundles, images, videos, fonts, LUTs, textures, HDRIs, and data files\n\nWhen WebGL is present and tooling allows pre-page-load injection, intercept:\n\n- `gl.shaderSource()` for vertex and fragment source\n- `gl.uniform*()` calls for names and observed values\n- `gl.bindFramebuffer()` to understand multipass render order\n- `gl.drawArrays()` and `gl.drawElements()` to understand draw-call order\n- texture and buffer setup when it affects the final look\n\nWhen 2D Canvas is present, inspect the render loop, draw primitives, image sources, compositing operations, and device-pixel-ratio handling.\n\n### 3. Extract The Visual Model\n\nTurn the raw capture into a compact visual model:\n\n- Scene graph or layer stack\n- Asset list with source, dimensions, and role\n- Shader\u002Fmaterial list with uniforms and dependencies\n- Motion map with trigger, duration, easing, repeat behavior, and responsive differences\n- Interaction map for pointer, keyboard, scroll, resize, and reduced-motion handling\n- Known uncertainties, such as minified bundle branches or runtime values that could not be observed\n\nPrefer evidence over guesses. If an effect cannot be observed directly, mark it as an inference.\n\n### 4. Rebuild In Open Design\n\nCreate a standalone web artifact that can be inspected and edited.\n\nChoose the simplest implementation that preserves the effect:\n\n- Static DOM\u002FCSS for layout-only references\n- CSS animation or WAAPI for simple motion\n- GSAP for sequenced or scroll-linked motion\n- Canvas 2D for 2D procedural effects\n- Native WebGL2 for compact full-screen shader effects\n- Three.js when the reference uses 3D, cameras, materials, textures, post-processing, or GPGPU patterns\n\nKeep the rebuild self-contained unless a dependency materially reduces complexity. If dependencies are used, load them in a transparent, reviewable way.\n\nImportant reconstruction rules:\n\n- Preserve color management and output color space.\n- Preserve the reference time base, such as seconds, elapsed milliseconds, frame count, or scroll progress.\n- Preserve multipass ordering for shader effects.\n- Do not tune random values to hide a root-cause mismatch; fix the model instead.\n- Add `prefers-reduced-motion` fallbacks for intense effects.\n- Replace copyrighted or brand-specific content unless the user explicitly owns it or asks to preserve it.\n\n### 5. Verify Visual Parity\n\nOpen the reference and the rebuilt artifact at the same viewport sizes. Compare:\n\n- First viewport framing\n- Color, brightness, contrast, and blending\n- Motion rhythm and loop continuity\n- Pointer and scroll response\n- Mobile behavior and performance\n- Canvas\u002FWebGL nonblank rendering\n\nFor WebGL and Canvas work, verify that the canvas is not blank and that animation advances over time. If possible, compare screenshots or pixel samples across at least two timestamps.\n\n### 6. Deliver\n\nFinish with:\n\n- The rebuilt artifact path or preview URL\n- A short extraction summary\n- Any visual differences that remain\n- Asset provenance and any replaced assets\n- Notes on what the user can safely edit next\n\nIf the user asks for an extraction report, create `EXTRACTION-REPORT.md` with the source URL, capture method, visual model, implementation choices, validation notes, and remaining gaps.\n\n## Quality Bar\n\n- The artifact must run independently from the source website.\n- The primary visual effect must be recognizable without explanation.\n- The implementation must be understandable enough for a designer or engineer to edit.\n- The workflow must avoid copying unrelated application code.\n- The response must distinguish captured facts from inferred reconstruction choices.\n","# Web Effect Extractor\n\nUse this plugin when the user gives a website URL and asks Open Design to recreate, remix, or learn from its visual effects. It is especially useful for hero backgrounds, WebGL scenes, Canvas animations, shader effects, cursor trails, scroll-driven motion, animated typography, and interaction patterns that are hard to understand from screenshots alone.\n\nThis workflow is inspired by the MIT-licensed `web-shader-extractor` skill from `lixiaolin94\u002Fskills`, adapted for Open Design's website recreation and editable artifact workflow.\n\n## Scope\n\nThe goal is to produce a faithful, editable Open Design artifact that preserves the reference site's visual effect and interaction logic while replacing private content, trademarks, tracking code, and nonessential app logic.\n\nExtract only what is needed to understand and recreate the visual behavior:\n\n- Layout structure, viewport behavior, breakpoints, and composition rhythm\n- Color, typography, blend modes, gradients, texture, lighting, and post-processing\n- Motion timing, easing, scroll triggers, pointer response, and idle animation loops\n- Canvas, WebGL, Three.js, shader, particle, and framebuffer pipeline details\n- Public static assets needed for visual parity, with provenance noted\n\nDo not copy private product copy, hidden application state, user data, analytics, auth flows, or unrelated business logic.\n\n## Workflow\n\n### 1. Prepare The Capture\n\nStart from the supplied URL and define the exact effect to recreate. If the user is vague, inspect the first viewport first and infer the likely target effect.\n\nBefore extracting runtime details, prefer a browser context that can evaluate page scripts and inspect canvas\u002FWebGL state. If Chrome DevTools MCP is available, use it for runtime interception. If it is not available, continue with the strongest available browser automation and clearly state that shader\u002Fruntime capture may be incomplete.\n\nRecord:\n\n- URL and capture timestamp\n- Viewport sizes to test, usually desktop and mobile\n- Main effect target and fallback effect targets\n- Framework clues from HTML, network requests, globals, and package signatures\n\n### 2. Runtime Inspection\n\nCapture runtime evidence before simplifying anything.\n\nInspect:\n\n- DOM tree, computed styles, fonts, CSS variables, custom properties, and animation names\n- Canvas elements, WebGL contexts, renderer attributes, supported extensions, and resolution scaling\n- Global framework markers such as `THREE`, `BABYLON`, `__NEXT_DATA__`, `__NUXT__`, `vite`, GSAP, Lenis, Framer Motion, or custom scene globals\n- Networked JS bundles, images, videos, fonts, LUTs, textures, HDRIs, and data files\n\nWhen WebGL is present and tooling allows pre-page-load injection, intercept:\n\n- `gl.shaderSource()` for vertex and fragment source\n- `gl.uniform*()` calls for names and observed values\n- `gl.bindFramebuffer()` to understand multipass render order\n- `gl.drawArrays()` and `gl.drawElements()` to understand draw-call order\n- texture and buffer setup when it affects the final look\n\nWhen 2D Canvas is present, inspect the render loop, draw primitives, image sources, compositing operations, and device-pixel-ratio handling.\n\n### 3. Extract The Visual Model\n\nTurn the raw capture into a compact visual model:\n\n- Scene graph or layer stack\n- Asset list with source, dimensions, and role\n- Shader\u002Fmaterial list with uniforms and dependencies\n- Motion map with trigger, duration, easing, repeat behavior, and responsive differences\n- Interaction map for pointer, keyboard, scroll, resize, and reduced-motion handling\n- Known uncertainties, such as minified bundle branches or runtime values that could not be observed\n\nPrefer evidence over guesses. If an effect cannot be observed directly, mark it as an inference.\n\n### 4. Rebuild In Open Design\n\nCreate a standalone web artifact that can be inspected and edited.\n\nChoose the simplest implementation that preserves the effect:\n\n- Static DOM\u002FCSS for layout-only references\n- CSS animation or WAAPI for simple motion\n- GSAP for sequenced or scroll-linked motion\n- Canvas 2D for 2D procedural effects\n- Native WebGL2 for compact full-screen shader effects\n- Three.js when the reference uses 3D, cameras, materials, textures, post-processing, or GPGPU patterns\n\nKeep the rebuild self-contained unless a dependency materially reduces complexity. If dependencies are used, load them in a transparent, reviewable way.\n\nImportant reconstruction rules:\n\n- Preserve color management and output color space.\n- Preserve the reference time base, such as seconds, elapsed milliseconds, frame count, or scroll progress.\n- Preserve multipass ordering for shader effects.\n- Do not tune random values to hide a root-cause mismatch; fix the model instead.\n- Add `prefers-reduced-motion` fallbacks for intense effects.\n- Replace copyrighted or brand-specific content unless the user explicitly owns it or asks to preserve it.\n\n### 5. Verify Visual Parity\n\nOpen the reference and the rebuilt artifact at the same viewport sizes. Compare:\n\n- First viewport framing\n- Color, brightness, contrast, and blending\n- Motion rhythm and loop continuity\n- Pointer and scroll response\n- Mobile behavior and performance\n- Canvas\u002FWebGL nonblank rendering\n\nFor WebGL and Canvas work, verify that the canvas is not blank and that animation advances over time. If possible, compare screenshots or pixel samples across at least two timestamps.\n\n### 6. Deliver\n\nFinish with:\n\n- The rebuilt artifact path or preview URL\n- A short extraction summary\n- Any visual differences that remain\n- Asset provenance and any replaced assets\n- Notes on what the user can safely edit next\n\nIf the user asks for an extraction report, create `EXTRACTION-REPORT.md` with the source URL, capture method, visual model, implementation choices, validation notes, and remaining gaps.\n\n## Quality Bar\n\n- The artifact must run independently from the source website.\n- The primary visual effect must be recognizable without explanation.\n- The implementation must be understandable enough for a designer or engineer to edit.\n- The workflow must avoid copying unrelated application code.\n- The response must distinguish captured facts from inferred reconstruction choices.\n",{"od":23,"name":5,"description":7},{"mode":24,"scenario":25},"scenario","web-effect-extraction","main","0467f0e19df12a6994ec7fb20ff6e9e23cd704e7","plugins\u002F_official\u002Fscenarios\u002Fod-web-effect-extractor","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design","https:\u002F\u002Fopen-design.ai","https:\u002F\u002Fgithub.com\u002Fbluesman1971","2026-07-09 04:08:20",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add bluesman1971\u002Fopen-design --skill od-web-effect-extractor",{"tool":39,"command":40},"bunx","bunx skills add bluesman1971\u002Fopen-design --skill od-web-effect-extractor",{"tool":42,"command":43},"pnpm","pnpm dlx skills add bluesman1971\u002Fopen-design --skill od-web-effect-extractor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fscenarios\u002Fod-web-effect-extractor\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"open-design.json","REFERENCE","参考文档",2918,"https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fscenarios\u002Fod-web-effect-extractor\u002Fopen-design.json",[54,63,71,78,85,92],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M78AMRG8NAGKWKNDQE39ZZFQ","web-design-guidelines","Review UI code for Web Interface Guidelines compliance by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.","MIT","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M78AMKHTFS149JGEYNQM5AXR","web-clone","网站复刻 \u002F 克隆方法论。USE WHEN 用户说 复刻网站、克隆网站、clone website、抄个站、仿站、 照着这个站做一个、reproduce site、还原某个网页效果、把这个站搬下来改成我的、 复刻某个交互\u002FWebGL\u002FCanvas\u002FThree.js 效果。提供「先拿真源码 → 判路径 → 逆向拆解 → 搭工程 → 替换内容」的可移植决策树，覆盖静态站 \u002F React-Vue-Next 内容站 \u002F WebGL-Canvas 重前端站三大分支，并强制核对任何 AI 二手分析里的可执行代码。","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-clone\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-clone\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M78AMH25JH2SH3AWTRSDCM9F","venice-video","Video generation and transcription workflows via the Venice.ai API.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fvenice-video\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M78AMF0M4FFKFWXFJ9NHTF5M","venice-image-generate","Image generation endpoints and available styles via the Venice.ai API.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fvenice-image-generate\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M78AMCH68X46SHNZVD284KXS","threejs","Three.js skills for creating 3D elements and interactive experiences in the browser — scenes, materials, controls, and post-processing.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fthreejs\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M78AM7P8WSBZDNZZ42BQHGK7","taste","Brief-time anti-AI-slop taste checklist — read the room and set the\ndesign dials BEFORE generating a landing page, portfolio, or redesign,\nso the first draft doesn't need a post-generation rescue. Use at the\nstart of a visual\u002Fcreative brief, not after the artifact exists.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Ftaste\u002FSKILL.md",[],[]]