[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71FT040Y4NBAZ2CFA1JE7TE":3,"skill-same:01M71FT040Y4NBAZ2CFA1JE7TE":70},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M71FT040Y4NBAZ2CFA1JE7TE","appinsights-instrumentation",null,"Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. WHEN: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices.","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\u002F.ai\u002Fskills\u002Fofficial_microsoft_appinsights_instrumentation\u002Fskill.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"instrumentation","appinsights instrumentation","configuration","patterns","instrument","guidance","microsoft","sdk","how","references","with","examples","best practices","when","telemetry","how to","insights","azure","for","app","2026-11-10 10:12:30",false,"---\nname: appinsights-instrumentation\ndescription: \"Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. WHEN: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices.\"\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.2\"\n---\n\n# AppInsights Instrumentation Guide\n\nThis skill provides **guidance and reference material** for instrumenting webapps with Azure Application Insights.\n\n> **⛔ ADDING COMPONENTS?**\n>\n> If the user wants to **add App Insights to their app**, invoke **azure-prepare** instead.\n> This skill provides reference material—azure-prepare orchestrates the actual changes.\n\n## When to Use This Skill\n\n- User asks **how** to instrument (guidance, patterns, examples)\n- User needs SDK setup instructions\n- azure-prepare invokes this skill during research phase\n- User wants to understand App Insights concepts\n\n## When to Use azure-prepare Instead\n\n- User says \"add telemetry to my app\"\n- User says \"add App Insights\" \n- User wants to modify their project\n- Any request to change\u002Fadd components\n\n## Prerequisites\n\nThe app in the workspace must be one of these kinds\n\n- An ASP.NET Core app hosted in Azure\n- A Node.js app hosted in Azure\n\n## Guidelines\n\n### Collect context information\n\nFind out the (programming language, application framework, hosting) tuple of the application the user is trying to add telemetry support in. This determines how the application can be instrumented. Read the source code to make an educated guess. Confirm with the user on anything you don't know. You must always ask the user where the application is hosted (e.g. on a personal computer, in an Azure App Service as code, in an Azure App Service as container, in an Azure Container App, etc.). \n\n### Prefer auto-instrument if possible\n\nIf the app is a C# ASP.NET Core app hosted in Azure App Service, use AUTO guide (`references\u002Fauto.md`) to help user auto-instrument the app.\n\n### Manually instrument\n\nManually instrument the app by creating the AppInsights resource and update the app's code. \n\n#### Create AppInsights resource\n\nUse one of the following options that fits the environment.\n\n- Add AppInsights to existing Bicep template. See examples\u002Fappinsights.bicep (`examples\u002Fappinsights.bicep`) for what to add. This is the best option if there are existing Bicep template files in the workspace.\n- Use Azure CLI. See scripts\u002Fappinsights.ps1 (`scripts\u002Fappinsights.ps1`) for what Azure CLI command to execute to create the App Insights resource.\n\nNo matter which option you choose, recommend the user to create the App Insights resource in a meaningful resource group that makes managing resources easier. A good candidate will be the same resource group that contains the resources for the hosted app in Azure.\n\n#### Modify application code\n\n- If the app is an ASP.NET Core app, see ASPNETCORE guide (`references\u002Faspnetcore.md`) for how to modify the C# code.\n- If the app is a Node.js app, see NODEJS guide (`references\u002Fnodejs.md`) for how to modify the JavaScript\u002FTypeScript code.\n- If the app is a Python app, see PYTHON guide (`references\u002Fpython.md`) for how to modify the Python code.\n\n## SDK Quick References\n\n- **OpenTelemetry Distro**: Python (`references\u002Fsdk\u002Fazure_monitor_opentelemetry_py.md`) | TypeScript (`references\u002Fsdk\u002Fazure_monitor_opentelemetry_ts.md`)\n- **OpenTelemetry Exporter**: Python (`references\u002Fsdk\u002Fazure_monitor_opentelemetry_exporter_py.md`) | Java (`references\u002Fsdk\u002Fazure_monitor_opentelemetry_exporter_java.md`)\n","# AppInsights Instrumentation Guide\n\nThis skill provides **guidance and reference material** for instrumenting webapps with Azure Application Insights.\n\n> **⛔ ADDING COMPONENTS?**\n>\n> If the user wants to **add App Insights to their app**, invoke **azure-prepare** instead.\n> This skill provides reference material—azure-prepare orchestrates the actual changes.\n\n## When to Use This Skill\n\n- User asks **how** to instrument (guidance, patterns, examples)\n- User needs SDK setup instructions\n- azure-prepare invokes this skill during research phase\n- User wants to understand App Insights concepts\n\n## When to Use azure-prepare Instead\n\n- User says \"add telemetry to my app\"\n- User says \"add App Insights\" \n- User wants to modify their project\n- Any request to change\u002Fadd components\n\n## Prerequisites\n\nThe app in the workspace must be one of these kinds\n\n- An ASP.NET Core app hosted in Azure\n- A Node.js app hosted in Azure\n\n## Guidelines\n\n### Collect context information\n\nFind out the (programming language, application framework, hosting) tuple of the application the user is trying to add telemetry support in. This determines how the application can be instrumented. Read the source code to make an educated guess. Confirm with the user on anything you don't know. You must always ask the user where the application is hosted (e.g. on a personal computer, in an Azure App Service as code, in an Azure App Service as container, in an Azure Container App, etc.). \n\n### Prefer auto-instrument if possible\n\nIf the app is a C# ASP.NET Core app hosted in Azure App Service, use AUTO guide (`references\u002Fauto.md`) to help user auto-instrument the app.\n\n### Manually instrument\n\nManually instrument the app by creating the AppInsights resource and update the app's code. \n\n#### Create AppInsights resource\n\nUse one of the following options that fits the environment.\n\n- Add AppInsights to existing Bicep template. See examples\u002Fappinsights.bicep (`examples\u002Fappinsights.bicep`) for what to add. This is the best option if there are existing Bicep template files in the workspace.\n- Use Azure CLI. See scripts\u002Fappinsights.ps1 (`scripts\u002Fappinsights.ps1`) for what Azure CLI command to execute to create the App Insights resource.\n\nNo matter which option you choose, recommend the user to create the App Insights resource in a meaningful resource group that makes managing resources easier. A good candidate will be the same resource group that contains the resources for the hosted app in Azure.\n\n#### Modify application code\n\n- If the app is an ASP.NET Core app, see ASPNETCORE guide (`references\u002Faspnetcore.md`) for how to modify the C# code.\n- If the app is a Node.js app, see NODEJS guide (`references\u002Fnodejs.md`) for how to modify the JavaScript\u002FTypeScript code.\n- If the app is a Python app, see PYTHON guide (`references\u002Fpython.md`) for how to modify the Python code.\n\n## SDK Quick References\n\n- **OpenTelemetry Distro**: Python (`references\u002Fsdk\u002Fazure_monitor_opentelemetry_py.md`) | TypeScript (`references\u002Fsdk\u002Fazure_monitor_opentelemetry_ts.md`)\n- **OpenTelemetry Exporter**: Python (`references\u002Fsdk\u002Fazure_monitor_opentelemetry_exporter_py.md`) | Java (`references\u002Fsdk\u002Fazure_monitor_opentelemetry_exporter_java.md`)\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":45,"version":46},"Microsoft","1.0.2","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_microsoft_appinsights_instrumentation",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill appinsights-instrumentation",{"tool":62,"command":63},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill appinsights-instrumentation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill appinsights-instrumentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_microsoft_appinsights_instrumentation\u002Fskill.md",true,[],[71,103,125,145,165,188],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":102},"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",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[83,84,85,86,87,88,89,90,91,92,93,94,95,96,32,97,98,99,100,101],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":110,"publishedAt":102},"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",[109],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[83,111,112,87,113,114,115,116,96,117,32,118,97,119,120,121,122,123,124,37],"react native","native","vercel react native skills","react native skills","modules","performance","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":102},"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":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[83,133,134,87,31,116,135,32,136,118,97,137,138,139,140,141,22,142,143,144],"react best practices","vercel react best practices","writing","code","data fetching","react components","next","refactoring","data","Optimization","guidelines","triggers",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":102},"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",[151],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[153,87,154,22,155,156,157,158,144,159,160,161,32,162,118,97,163,164,98,83],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":102},"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",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000010","后端与接口",[175,176,177,178,31,179,180,181,37,142,116,182,183,135,184,161,185,186,187,32],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":211},"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",[194],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[196,197,198,199,200,93,201,158,202,96,203,204,32,83,205,206,207,208,209,210],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]