[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MT281AXSAAQTDPE9YSX67":3,"skill-same:01M71MT281AXSAAQTDPE9YSX67":72},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M71MT281AXSAAQTDPE9YSX67","chrome-devtools",null,"Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_github_chrome_devtools\u002Fskill.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"devtools","chrome","chrome devtools","analyzing","performance analysis","profiling","web","with","browser","analysis","automation","debugging","use","traffic","MCP","pages","browser automation","performance","expert","for","2026-11-10 10:56:23",false,"---\nname: chrome-devtools\ndescription: 'Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.'\nlicense: MIT\n---\n\n# Chrome DevTools Agent\n\n## Overview\n\nA specialized skill for controlling and inspecting a live Chrome browser. This skill leverages the `chrome-devtools` MCP server to perform a wide range of browser-related tasks, from simple navigation to complex performance profiling.\n\n## When to Use\n\nUse this skill when:\n\n- **Browser Automation**: Navigating pages, clicking elements, filling forms, and handling dialogs.\n- **Visual Inspection**: Taking screenshots or text snapshots of web pages.\n- **Debugging**: Inspecting console messages, evaluating JavaScript in the page context, and analyzing network requests.\n- **Performance Analysis**: Recording and analyzing performance traces to identify bottlenecks and Core Web Vital issues.\n- **Emulation**: Resizing the viewport or emulating network\u002FCPU conditions.\n\n## Tool Categories\n\n### 1. Navigation & Page Management\n\n- `new_page`: Open a new tab\u002Fpage.\n- `navigate_page`: Go to a specific URL, reload, or navigate history.\n- `select_page`: Switch context between open pages.\n- `list_pages`: See all open pages and their IDs.\n- `close_page`: Close a specific page.\n- `wait_for`: Wait for specific text to appear on the page.\n\n### 2. Input & Interaction\n\n- `click`: Click on an element (use `uid` from snapshot).\n- `fill` \u002F `fill_form`: Type text into inputs or fill multiple fields at once.\n- `hover`: Move the mouse over an element.\n- `press_key`: Send keyboard shortcuts or special keys (e.g., \"Enter\", \"Control+C\").\n- `drag`: Drag and drop elements.\n- `handle_dialog`: Accept or dismiss browser alerts\u002Fprompts.\n- `upload_file`: Upload a file through a file input.\n\n### 3. Debugging & Inspection\n\n- `take_snapshot`: Get a text-based accessibility tree (best for identifying elements).\n- `take_screenshot`: Capture a visual representation of the page or a specific element.\n- `list_console_messages` \u002F `get_console_message`: Inspect the page's console output.\n- `evaluate_script`: Run custom JavaScript in the page context.\n- `list_network_requests` \u002F `get_network_request`: Analyze network traffic and request details.\n\n### 4. Emulation & Performance\n\n- `resize_page`: Change the viewport dimensions.\n- `emulate`: Throttling CPU\u002FNetwork or emulating geolocation.\n- `performance_start_trace`: Start recording a performance profile.\n- `performance_stop_trace`: Stop recording and save the trace.\n- `performance_analyze_insight`: Get detailed analysis from recorded performance data.\n\n## Workflow Patterns\n\n### Pattern A: Identifying Elements (Snapshot-First)\n\nAlways prefer `take_snapshot` over `take_screenshot` for finding elements. The snapshot provides `uid` values which are required by interaction tools.\n\n```markdown\n1. `take_snapshot` to get the current page structure.\n2. Find the `uid` of the target element.\n3. Use `click(uid=...)` or `fill(uid=..., value=...)`.\n```\n\n### Pattern B: Troubleshooting Errors\n\nWhen a page is failing, check both console logs and network requests.\n\n```markdown\n1. `list_console_messages` to check for JavaScript errors.\n2. `list_network_requests` to identify failed (4xx\u002F5xx) resources.\n3. `evaluate_script` to check the value of specific DOM elements or global variables.\n```\n\n### Pattern C: Performance Profiling\n\nIdentify why a page is slow.\n\n```markdown\n1. `performance_start_trace(reload=true, autoStop=true)`\n2. Wait for the page to load\u002Ftrace to finish.\n3. `performance_analyze_insight` to find LCP issues or layout shifts.\n```\n\n## Best Practices\n\n- **Context Awareness**: Always run `list_pages` and `select_page` if you are unsure which tab is currently active.\n- **Snapshots**: Take a new snapshot after any major navigation or DOM change, as `uid` values may change.\n- **Timeouts**: Use reasonable timeouts for `wait_for` to avoid hanging on slow-loading elements.\n- **Screenshots**: Use `take_screenshot` sparingly for visual verification, but rely on `take_snapshot` for logic.\n","# Chrome DevTools Agent\n\n## Overview\n\nA specialized skill for controlling and inspecting a live Chrome browser. This skill leverages the `chrome-devtools` MCP server to perform a wide range of browser-related tasks, from simple navigation to complex performance profiling.\n\n## When to Use\n\nUse this skill when:\n\n- **Browser Automation**: Navigating pages, clicking elements, filling forms, and handling dialogs.\n- **Visual Inspection**: Taking screenshots or text snapshots of web pages.\n- **Debugging**: Inspecting console messages, evaluating JavaScript in the page context, and analyzing network requests.\n- **Performance Analysis**: Recording and analyzing performance traces to identify bottlenecks and Core Web Vital issues.\n- **Emulation**: Resizing the viewport or emulating network\u002FCPU conditions.\n\n## Tool Categories\n\n### 1. Navigation & Page Management\n\n- `new_page`: Open a new tab\u002Fpage.\n- `navigate_page`: Go to a specific URL, reload, or navigate history.\n- `select_page`: Switch context between open pages.\n- `list_pages`: See all open pages and their IDs.\n- `close_page`: Close a specific page.\n- `wait_for`: Wait for specific text to appear on the page.\n\n### 2. Input & Interaction\n\n- `click`: Click on an element (use `uid` from snapshot).\n- `fill` \u002F `fill_form`: Type text into inputs or fill multiple fields at once.\n- `hover`: Move the mouse over an element.\n- `press_key`: Send keyboard shortcuts or special keys (e.g., \"Enter\", \"Control+C\").\n- `drag`: Drag and drop elements.\n- `handle_dialog`: Accept or dismiss browser alerts\u002Fprompts.\n- `upload_file`: Upload a file through a file input.\n\n### 3. Debugging & Inspection\n\n- `take_snapshot`: Get a text-based accessibility tree (best for identifying elements).\n- `take_screenshot`: Capture a visual representation of the page or a specific element.\n- `list_console_messages` \u002F `get_console_message`: Inspect the page's console output.\n- `evaluate_script`: Run custom JavaScript in the page context.\n- `list_network_requests` \u002F `get_network_request`: Analyze network traffic and request details.\n\n### 4. Emulation & Performance\n\n- `resize_page`: Change the viewport dimensions.\n- `emulate`: Throttling CPU\u002FNetwork or emulating geolocation.\n- `performance_start_trace`: Start recording a performance profile.\n- `performance_stop_trace`: Stop recording and save the trace.\n- `performance_analyze_insight`: Get detailed analysis from recorded performance data.\n\n## Workflow Patterns\n\n### Pattern A: Identifying Elements (Snapshot-First)\n\nAlways prefer `take_snapshot` over `take_screenshot` for finding elements. The snapshot provides `uid` values which are required by interaction tools.\n\n```markdown\n1. `take_snapshot` to get the current page structure.\n2. Find the `uid` of the target element.\n3. Use `click(uid=...)` or `fill(uid=..., value=...)`.\n```\n\n### Pattern B: Troubleshooting Errors\n\nWhen a page is failing, check both console logs and network requests.\n\n```markdown\n1. `list_console_messages` to check for JavaScript errors.\n2. `list_network_requests` to identify failed (4xx\u002F5xx) resources.\n3. `evaluate_script` to check the value of specific DOM elements or global variables.\n```\n\n### Pattern C: Performance Profiling\n\nIdentify why a page is slow.\n\n```markdown\n1. `performance_start_trace(reload=true, autoStop=true)`\n2. Wait for the page to load\u002Ftrace to finish.\n3. `performance_analyze_insight` to find LCP issues or layout shifts.\n```\n\n## Best Practices\n\n- **Context Awareness**: Always run `list_pages` and `select_page` if you are unsure which tab is currently active.\n- **Snapshots**: Take a new snapshot after any major navigation or DOM change, as `uid` values may change.\n- **Timeouts**: Use reasonable timeouts for `wait_for` to avoid hanging on slow-loading elements.\n- **Screenshots**: Use `take_screenshot` sparingly for visual verification, but rely on `take_snapshot` for logic.\n",{"name":5,"license":15,"description":7},"master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fofficial_github_chrome_devtools",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill chrome-devtools",{"tool":64,"command":65},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill chrome-devtools",{"tool":67,"command":68},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill chrome-devtools","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_github_chrome_devtools\u002Fskill.md",true,[],[73,104,125,147,166,189],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":82,"publishedAt":103},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","when","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":103},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[110],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},[83,112,113,87,114,115,116,41,96,117,97,118,98,119,120,121,122,123,124,43],"react native","native","vercel react native skills","react native skills","modules","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":103},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[131],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},[83,133,134,87,135,41,136,97,137,118,98,138,139,140,141,142,143,144,145,146],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"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":154,"publishedAt":103},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[153],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},[155,87,156,143,157,158,159,160,146,161,162,36,97,163,118,98,164,165,99,83],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":103},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[172],{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[176,177,178,179,135,180,181,182,43,144,41,183,184,136,185,36,186,187,188,97],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":44},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[195],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},[197,198,199,200,201,93,202,160,203,96,204,205,97,83,206,207,208,209,210,211],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue"]