[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NXRF795JSXWP9V304KBQX":3,"skill-same:01M71NXRF795JSXWP9V304KBQX":78},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M71NXRF795JSXWP9V304KBQX","azure-kubernetes",null,"Plan, create, and configure production-ready Azure Kubernetes Service (AKS) clusters. Covers Day-0 checklist, SKU selection (Automatic vs Standard), networking options (private API server, Azure CNI Overlay, egress configuration), security, and operations (autoscaling, upgrade strategy, cost analysis). WHEN: create AKS environment, provision AKS environment, enable AKS observability, design AKS networking, choose AKS SKU, secure AKS, optimize AKS, rightsize AKS pod, AKS spot nodes, AKS cluster-autoscaler.","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_microsoft_azure_kubernetes\u002Fskill.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"kubernetes","azure kubernetes","azure","when","design","overlay","production-ready","autoscaling","upgrade","options","optimize","selection","ready","choose","configure","plan","api","analysis","server","create","2026-11-10 10:56:23",false,"---\nname: azure-kubernetes\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.4\"\ndescription: \"Plan, create, and configure production-ready Azure Kubernetes Service (AKS) clusters. Covers Day-0 checklist, SKU selection (Automatic vs Standard), networking options (private API server, Azure CNI Overlay, egress configuration), security, and operations (autoscaling, upgrade strategy, cost analysis). WHEN: create AKS environment, provision AKS environment, enable AKS observability, design AKS networking, choose AKS SKU, secure AKS, optimize AKS, rightsize AKS pod, AKS spot nodes, AKS cluster-autoscaler.\"\n---\n\n# Azure Kubernetes Service\n\n> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**\n>\n> This skill produces a **recommended AKS cluster configuration** based on user requirements, distinguishing **Day-0 decisions** (networking, API server — hard to change later) from **Day-1 features** (can enable post-creation). See CLI reference (`.\u002Freferences\u002Fcli_reference.md`) for commands.\n\n## Quick Reference\n| Property | Value |\n|----------|-------|\n| Best for | AKS cluster planning and Day-0 decisions |\n| MCP Tools | `mcp_azure_mcp_aks` |\n| CLI | `az aks create`, `az aks show`, `kubectl get`, `kubectl describe` |\n| Related skills | azure-diagnostics (troubleshooting AKS), azure-validate (readiness checks) |\n\n## When to Use This Skill\nActivate this skill when user wants to:\n- Create a new AKS cluster\n- Plan AKS cluster configuration for production workloads\n- Design AKS networking (API server access, pod IP model, egress)\n- Set up AKS identity and secrets management\n- Configure AKS governance (Azure Policy, Deployment Safeguards)\n- Enable AKS observability (Container Insights, Managed Prometheus, Grafana)\n- Define AKS upgrade and patching strategy\n- Understand AKS Automatic vs Standard SKU differences\n- Get a Day-0 checklist for AKS cluster setup and configuration\n\n## Rules\n1. Start with the user's requirements for provisioning compute, networking, security, and other settings.\n2. Use the `azure` MCP server and select `mcp_azure_mcp_aks` first to discover the exact AKS-specific MCP tools surfaced by the client. Choose the smallest discovered AKS tool that fits the task, and fall back to Azure CLI (`az aks`) only when the needed functionality is not exposed through the AKS MCP surface.\n3. Determine if AKS Automatic or Standard SKU is more appropriate based on the user's need for control vs convenience. Default to AKS Automatic unless specific customizations are required.\n4. Document decisions and rationale for cluster configuration choices, especially for Day-0 decisions that are hard to change later (networking, API server access).\n\n\n## Required Inputs (Ask only what’s needed)\nIf the user is unsure, use safe defaults.\n- AKS environment type: dev\u002Ftest or production\n- Region(s), availability zones, preferred node VM sizes\n- Expected scale (node\u002Fcluster count, workload size)\n- Networking requirements (API server access, pod IP model, ingress\u002Fegress control)\n- Security and identity requirements, including image registry\n- Upgrade and observability preferences\n- Cost constraints\n\n## Workflow\n\n### 1. Cluster Type\n- **AKS Automatic** (default): Best for most production workloads, provides a curated experience with pre-configured best practices for security, reliability, and performance. Use unless you have specific custom requirements for networking, autoscaling, or node pool configurations not supported by Node Auto-Provisioning (NAP).\n- **AKS Standard**: Use if you need full control over environment configuration, which requires additional overhead to set up and manage.\n\n### 2. Networking (Pod IP, Egress, Ingress, Dataplane)\n\n**Pod IP Model** (Key Day-0 decision):\n- **Azure CNI Overlay** (recommended): pod IPs from private overlay range, not VNet-routable, scales to large environments and good for most workloads\n- **Azure CNI (VNet-routable)**: pod IPs directly from VNet (pod subnet or node subnet), use when pods must be directly addressable from VNet or on-prem\n  - Docs: https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Faks\u002Fazure-cni-overlay\n\n**Dataplane & Network Policy**:\n- **Azure CNI powered by Cilium** (recommended): eBPF-based for high-performance packet processing, network policies, and observability\n\n**Egress**:\n- **Static Egress Gateway** for stable, predictable outbound IPs\n- For restricted egress: UDR + Azure Firewall or NVA\n\n**Ingress**:\n- **App Routing addon with Gateway API** — recommended default for HTTP\u002FHTTPS workloads\n- **Istio service mesh with Gateway API** - for advanced traffic management, mTLS, canary releases\n- **Application Gateway for Containers** — for L7 load balancing with WAF integration\n\n**DNS**:\n- Enable **LocalDNS** on all node pools for reliable, performant DNS resolution\n\n### 3. Security\n- Use **Microsoft Entra ID** everywhere (control plane, Workload Identity for pods, node access). Avoid static credentials.\n- Azure Key Vault via **Secrets Store CSI Driver** for secrets\n- Enable **Azure Policy** + **Deployment Safeguards**\n- Enable **Encryption at rest** for etcd\u002FAPI server; **in-transit** for node-to-node\n- Allow only signed, policy-approved images (Azure Policy + Ratify), prefer **Azure Container Registry**\n- **Isolation**: Use namespaces, network policies, scoped logging\n\n### 4. Observability\n- Use Managed Prometheus and Container Insights with Grafana for AKS observability (logs + metrics).\n- Enable Diagnostic Settings to collect control plane logs and audit logs in a Log Analytics workspace for security monitoring and troubleshooting.\n- For other monitoring and troubleshooting tools, use features like the Agentic CLI for AKS, Application Insights, Resource Health Center, AppLens detectors, and Azure Advisors.\n\n### 5. Upgrades & Patching\n- Configure **Maintenance Windows** for controlled upgrade timing\n- Enable **auto-upgrades** for control plane and node OS to stay up-to-date with security patches and Kubernetes versions\n- Consider **LTS versions** for enterprise stability (2-year support) by upgrading your AKS environment to the Premium tier\n- **Fleet upgrades**: Use **AKS Fleet Manager** for staged rollout across test to production environments\n\n### 6. Performance\n- Use **Ephemeral OS disks** (`--node-osdisk-type Ephemeral`) for faster node startup\n- Select **Azure Linux** as node OS (smaller footprint, faster boot)\n- Enable **KEDA** for event-driven autoscaling beyond HPA\n\n### 7. Node Pools & Compute\n- **Dedicated system node pool**: At least 2 nodes, tainted for system workloads only (`CriticalAddonsOnly`)\n- Enable **Node Auto Provisioning (NAP)** on all pools for cost savings and responsive scaling\n- Use **latest generation SKUs (v5\u002Fv6)** for host-level optimizations\n- **Avoid B-series VMs** — burstable SKUs cause performance\u002Freliability issues\n- Use SKUs with **at least 4 vCPUs** for production workloads\n- Set **topology spread constraints** to distribute pods across hosts\u002Fzones per SLO\n\n### 8. Reliability\n- Deploy across **3 Availability Zones** (`--zones 1 2 3`)\n- Use **Standard tier** for zone-redundant control plane + 99.95% SLA for API server availability\n- Enable **Microsoft Defender for Containers** for runtime protection\n- Configure **PodDisruptionBudgets** for all production workloads\n- Use **topology spread constraints** to ensure pod distribution across failure domains\n\n### 9. Cost Controls\n- Use **Spot node pools** for batch\u002Finterruptible workloads (up to 90% savings)\n- **Stop\u002FStart** dev\u002Ftest clusters: `az aks stop\u002Fstart`\n- Consider **Reserved Instances** or **Savings Plans** for steady-state workloads\n\n**Deep-dive scenarios** — load only the relevant reference file:\n\n| Scenario | Trigger Keywords | Reference |\n|----------|-----------------|-----------|\n| Pod Rightsizing | over-provisioned pods, CPU requests, memory requests, rightsize workloads | azure_aks_rightsizing.md (`.\u002Freferences\u002Fazure_aks_rightsizing.md`) |\n| VPA Setup | vertical pod autoscaler, VPA recommendations, VPA enable | azure_aks_vpa.md (`.\u002Freferences\u002Fazure_aks_vpa.md`) |\n| Cluster Autoscaler | idle nodes, CAS off, enable autoscaler, scale-down profile, node utilization | azure_aks_autoscaler.md (`.\u002Freferences\u002Fazure_aks_autoscaler.md`) |\n| Spot Node Pools | Spot VMs, Spot nodes, batch workloads, cheaper nodes | azure_aks_spot.md (`.\u002Freferences\u002Fazure_aks_spot.md`) |\n\n> **Disambiguation:** If a prompt matches multiple rows (e.g., \"cheaper nodes\" could suggest both Spot and autoscaler), prefer the most specific match. If ambiguous, ask the user to clarify their intent before loading a reference file.\n\n## Guardrails \u002F Safety\n- Do not request or output secrets (tokens, keys).\n- Do not ask the user to paste subscription IDs. Discover subscription and resource scope via MCP tools (e.g., list subscriptions, list resource groups) or `az account show` \u002F `az account list` so the agent can resolve context without exposing identifiers.\n- If requirements are ambiguous for day-0 critical decisions, ask the user clarifying questions. For day-1 enabled features, propose 2–3 safe options with tradeoffs and choose a conservative default.\n- Do not promise zero downtime; advise workload safeguards (PDBs, probes, replicas) and staged upgrades along with best practices for reliability and performance.\n\n## MCP Tools\n| Tool | Purpose | Key Parameters |\n|------|---------|----------------|\n| `mcp_azure_mcp_aks` | AKS MCP entry point used to discover the exact AKS-specific tools exposed by the client | Discover the callable AKS tool first, then use that tool's parameters |\n\n## Error Handling\n| Error \u002F Symptom | Likely Cause | Remediation |\n|-----------------|--------------|-------------|\n| MCP tool call fails or times out | Invalid credentials, subscription, or AKS context | Verify `az login`, confirm the active subscription context with `az account show`, and check the target resource group without echoing subscription identifiers back to the user |\n| Quota exceeded | Regional vCPU or resource limits | Request quota increase or select different region\u002FVM SKU |\n| Networking conflict (IP exhaustion) | Pod subnet too small for overlay\u002FCNI | Re-plan IP ranges; may require cluster recreation (Day-0) |\n| Workload Identity not working | Missing OIDC issuer or federated credential | Enable `--enable-oidc-issuer --enable-workload-identity`, configure federated identity |\n","# Azure Kubernetes Service\n\n> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**\n>\n> This skill produces a **recommended AKS cluster configuration** based on user requirements, distinguishing **Day-0 decisions** (networking, API server — hard to change later) from **Day-1 features** (can enable post-creation). See CLI reference (`.\u002Freferences\u002Fcli_reference.md`) for commands.\n\n## Quick Reference\n| Property | Value |\n|----------|-------|\n| Best for | AKS cluster planning and Day-0 decisions |\n| MCP Tools | `mcp_azure_mcp_aks` |\n| CLI | `az aks create`, `az aks show`, `kubectl get`, `kubectl describe` |\n| Related skills | azure-diagnostics (troubleshooting AKS), azure-validate (readiness checks) |\n\n## When to Use This Skill\nActivate this skill when user wants to:\n- Create a new AKS cluster\n- Plan AKS cluster configuration for production workloads\n- Design AKS networking (API server access, pod IP model, egress)\n- Set up AKS identity and secrets management\n- Configure AKS governance (Azure Policy, Deployment Safeguards)\n- Enable AKS observability (Container Insights, Managed Prometheus, Grafana)\n- Define AKS upgrade and patching strategy\n- Understand AKS Automatic vs Standard SKU differences\n- Get a Day-0 checklist for AKS cluster setup and configuration\n\n## Rules\n1. Start with the user's requirements for provisioning compute, networking, security, and other settings.\n2. Use the `azure` MCP server and select `mcp_azure_mcp_aks` first to discover the exact AKS-specific MCP tools surfaced by the client. Choose the smallest discovered AKS tool that fits the task, and fall back to Azure CLI (`az aks`) only when the needed functionality is not exposed through the AKS MCP surface.\n3. Determine if AKS Automatic or Standard SKU is more appropriate based on the user's need for control vs convenience. Default to AKS Automatic unless specific customizations are required.\n4. Document decisions and rationale for cluster configuration choices, especially for Day-0 decisions that are hard to change later (networking, API server access).\n\n\n## Required Inputs (Ask only what’s needed)\nIf the user is unsure, use safe defaults.\n- AKS environment type: dev\u002Ftest or production\n- Region(s), availability zones, preferred node VM sizes\n- Expected scale (node\u002Fcluster count, workload size)\n- Networking requirements (API server access, pod IP model, ingress\u002Fegress control)\n- Security and identity requirements, including image registry\n- Upgrade and observability preferences\n- Cost constraints\n\n## Workflow\n\n### 1. Cluster Type\n- **AKS Automatic** (default): Best for most production workloads, provides a curated experience with pre-configured best practices for security, reliability, and performance. Use unless you have specific custom requirements for networking, autoscaling, or node pool configurations not supported by Node Auto-Provisioning (NAP).\n- **AKS Standard**: Use if you need full control over environment configuration, which requires additional overhead to set up and manage.\n\n### 2. Networking (Pod IP, Egress, Ingress, Dataplane)\n\n**Pod IP Model** (Key Day-0 decision):\n- **Azure CNI Overlay** (recommended): pod IPs from private overlay range, not VNet-routable, scales to large environments and good for most workloads\n- **Azure CNI (VNet-routable)**: pod IPs directly from VNet (pod subnet or node subnet), use when pods must be directly addressable from VNet or on-prem\n  - Docs: https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Faks\u002Fazure-cni-overlay\n\n**Dataplane & Network Policy**:\n- **Azure CNI powered by Cilium** (recommended): eBPF-based for high-performance packet processing, network policies, and observability\n\n**Egress**:\n- **Static Egress Gateway** for stable, predictable outbound IPs\n- For restricted egress: UDR + Azure Firewall or NVA\n\n**Ingress**:\n- **App Routing addon with Gateway API** — recommended default for HTTP\u002FHTTPS workloads\n- **Istio service mesh with Gateway API** - for advanced traffic management, mTLS, canary releases\n- **Application Gateway for Containers** — for L7 load balancing with WAF integration\n\n**DNS**:\n- Enable **LocalDNS** on all node pools for reliable, performant DNS resolution\n\n### 3. Security\n- Use **Microsoft Entra ID** everywhere (control plane, Workload Identity for pods, node access). Avoid static credentials.\n- Azure Key Vault via **Secrets Store CSI Driver** for secrets\n- Enable **Azure Policy** + **Deployment Safeguards**\n- Enable **Encryption at rest** for etcd\u002FAPI server; **in-transit** for node-to-node\n- Allow only signed, policy-approved images (Azure Policy + Ratify), prefer **Azure Container Registry**\n- **Isolation**: Use namespaces, network policies, scoped logging\n\n### 4. Observability\n- Use Managed Prometheus and Container Insights with Grafana for AKS observability (logs + metrics).\n- Enable Diagnostic Settings to collect control plane logs and audit logs in a Log Analytics workspace for security monitoring and troubleshooting.\n- For other monitoring and troubleshooting tools, use features like the Agentic CLI for AKS, Application Insights, Resource Health Center, AppLens detectors, and Azure Advisors.\n\n### 5. Upgrades & Patching\n- Configure **Maintenance Windows** for controlled upgrade timing\n- Enable **auto-upgrades** for control plane and node OS to stay up-to-date with security patches and Kubernetes versions\n- Consider **LTS versions** for enterprise stability (2-year support) by upgrading your AKS environment to the Premium tier\n- **Fleet upgrades**: Use **AKS Fleet Manager** for staged rollout across test to production environments\n\n### 6. Performance\n- Use **Ephemeral OS disks** (`--node-osdisk-type Ephemeral`) for faster node startup\n- Select **Azure Linux** as node OS (smaller footprint, faster boot)\n- Enable **KEDA** for event-driven autoscaling beyond HPA\n\n### 7. Node Pools & Compute\n- **Dedicated system node pool**: At least 2 nodes, tainted for system workloads only (`CriticalAddonsOnly`)\n- Enable **Node Auto Provisioning (NAP)** on all pools for cost savings and responsive scaling\n- Use **latest generation SKUs (v5\u002Fv6)** for host-level optimizations\n- **Avoid B-series VMs** — burstable SKUs cause performance\u002Freliability issues\n- Use SKUs with **at least 4 vCPUs** for production workloads\n- Set **topology spread constraints** to distribute pods across hosts\u002Fzones per SLO\n\n### 8. Reliability\n- Deploy across **3 Availability Zones** (`--zones 1 2 3`)\n- Use **Standard tier** for zone-redundant control plane + 99.95% SLA for API server availability\n- Enable **Microsoft Defender for Containers** for runtime protection\n- Configure **PodDisruptionBudgets** for all production workloads\n- Use **topology spread constraints** to ensure pod distribution across failure domains\n\n### 9. Cost Controls\n- Use **Spot node pools** for batch\u002Finterruptible workloads (up to 90% savings)\n- **Stop\u002FStart** dev\u002Ftest clusters: `az aks stop\u002Fstart`\n- Consider **Reserved Instances** or **Savings Plans** for steady-state workloads\n\n**Deep-dive scenarios** — load only the relevant reference file:\n\n| Scenario | Trigger Keywords | Reference |\n|----------|-----------------|-----------|\n| Pod Rightsizing | over-provisioned pods, CPU requests, memory requests, rightsize workloads | azure_aks_rightsizing.md (`.\u002Freferences\u002Fazure_aks_rightsizing.md`) |\n| VPA Setup | vertical pod autoscaler, VPA recommendations, VPA enable | azure_aks_vpa.md (`.\u002Freferences\u002Fazure_aks_vpa.md`) |\n| Cluster Autoscaler | idle nodes, CAS off, enable autoscaler, scale-down profile, node utilization | azure_aks_autoscaler.md (`.\u002Freferences\u002Fazure_aks_autoscaler.md`) |\n| Spot Node Pools | Spot VMs, Spot nodes, batch workloads, cheaper nodes | azure_aks_spot.md (`.\u002Freferences\u002Fazure_aks_spot.md`) |\n\n> **Disambiguation:** If a prompt matches multiple rows (e.g., \"cheaper nodes\" could suggest both Spot and autoscaler), prefer the most specific match. If ambiguous, ask the user to clarify their intent before loading a reference file.\n\n## Guardrails \u002F Safety\n- Do not request or output secrets (tokens, keys).\n- Do not ask the user to paste subscription IDs. Discover subscription and resource scope via MCP tools (e.g., list subscriptions, list resource groups) or `az account show` \u002F `az account list` so the agent can resolve context without exposing identifiers.\n- If requirements are ambiguous for day-0 critical decisions, ask the user clarifying questions. For day-1 enabled features, propose 2–3 safe options with tradeoffs and choose a conservative default.\n- Do not promise zero downtime; advise workload safeguards (PDBs, probes, replicas) and staged upgrades along with best practices for reliability and performance.\n\n## MCP Tools\n| Tool | Purpose | Key Parameters |\n|------|---------|----------------|\n| `mcp_azure_mcp_aks` | AKS MCP entry point used to discover the exact AKS-specific tools exposed by the client | Discover the callable AKS tool first, then use that tool's parameters |\n\n## Error Handling\n| Error \u002F Symptom | Likely Cause | Remediation |\n|-----------------|--------------|-------------|\n| MCP tool call fails or times out | Invalid credentials, subscription, or AKS context | Verify `az login`, confirm the active subscription context with `az account show`, and check the target resource group without echoing subscription identifiers back to the user |\n| Quota exceeded | Regional vCPU or resource limits | Request quota increase or select different region\u002FVM SKU |\n| Networking conflict (IP exhaustion) | Pod subnet too small for overlay\u002FCNI | Re-plan IP ranges; may require cluster recreation (Day-0) |\n| Workload Identity not working | Missing OIDC issuer or federated credential | Enable `--enable-oidc-issuer --enable-workload-identity`, configure federated identity |\n",{"name":5,"license":15,"metadata":52,"description":7},{"author":53,"version":54},"Microsoft","1.0.4","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fofficial_microsoft_azure_kubernetes",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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill azure-kubernetes",{"tool":70,"command":71},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill azure-kubernetes",{"tool":73,"command":74},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill azure-kubernetes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_microsoft_azure_kubernetes\u002Fskill.md",true,[],[79,107,130,152,172,195],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":88,"publishedAt":106},"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",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[89,90,91,92,93,94,95,96,97,98,99,100,101,102,30,103,43,104,46,105],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","route","libraries","2026-11-10 13:02:02",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":114,"publishedAt":106},"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",[113],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[89,115,116,93,117,118,119,120,102,121,30,122,103,123,124,125,126,127,128,129],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":137,"publishedAt":106},"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",[136],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[89,138,139,93,140,120,141,30,142,122,103,143,144,145,146,147,148,149,150,151],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":106},"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",[158],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[160,93,161,148,162,163,164,165,151,166,167,168,30,169,122,103,170,171,43,89],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":181,"publishedAt":106},"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",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[182,183,184,185,140,186,187,188,129,149,120,189,190,141,191,168,192,193,194,30],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":47},"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",[201],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[203,204,205,206,207,99,208,165,209,102,210,211,30,89,212,213,45,214,215,216],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","markdown","rendering","vue"]