[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NX608182WH5N33Z2MHEBB":3,"skill-same:01M71NX608182WH5N33Z2MHEBB":75},{"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":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M71NX608182WH5N33Z2MHEBB","azure-cost",null,"Unified Azure cost management: query historical costs, forecast future spending, and optimize to reduce waste. WHEN: \"Azure costs\", \"Azure spending\", \"Azure bill\", \"cost breakdown\", \"cost by service\", \"cost by resource\", \"how much am I spending\", \"show my bill\", \"monthly cost summary\", \"cost trends\", \"top cost drivers\", \"actual cost\", \"amortized cost\", \"forecast spending\", \"projected costs\", \"estimate bill\", \"future costs\", \"budget forecast\", \"end of month costs\", \"how much will I spend\", \"optimize costs\", \"reduce spending\", \"find cost savings\", \"orphaned resources\", \"rightsize VMs\", \"cost analysis\", \"reduce waste\", \"unused resources\", \"optimize Redis costs\", \"cost by tag\", \"cost by resource group\", \"AKS cost analysis add-on\", \"namespace cost\", \"cost spike\", \"anomaly\", \"budget alert\", \"AKS cost visibility\". DO NOT USE FOR: deploying resources, provisioning infrastructure, diagnostics, security audits, or estimating costs for new resources not yet deployed.","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_cost\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],"cost","azure cost","azure","Budget","aks","how","top","cost summary","optimize","analysis","query","reduce","when","group","unused","new","provisioning infrastructure","end","resources","show","2026-11-10 10:56:23",false,"---\nname: azure-cost\ndescription: \"Unified Azure cost management: query historical costs, forecast future spending, and optimize to reduce waste. WHEN: \\\"Azure costs\\\", \\\"Azure spending\\\", \\\"Azure bill\\\", \\\"cost breakdown\\\", \\\"cost by service\\\", \\\"cost by resource\\\", \\\"how much am I spending\\\", \\\"show my bill\\\", \\\"monthly cost summary\\\", \\\"cost trends\\\", \\\"top cost drivers\\\", \\\"actual cost\\\", \\\"amortized cost\\\", \\\"forecast spending\\\", \\\"projected costs\\\", \\\"estimate bill\\\", \\\"future costs\\\", \\\"budget forecast\\\", \\\"end of month costs\\\", \\\"how much will I spend\\\", \\\"optimize costs\\\", \\\"reduce spending\\\", \\\"find cost savings\\\", \\\"orphaned resources\\\", \\\"rightsize VMs\\\", \\\"cost analysis\\\", \\\"reduce waste\\\", \\\"unused resources\\\", \\\"optimize Redis costs\\\", \\\"cost by tag\\\", \\\"cost by resource group\\\", \\\"AKS cost analysis add-on\\\", \\\"namespace cost\\\", \\\"cost spike\\\", \\\"anomaly\\\", \\\"budget alert\\\", \\\"AKS cost visibility\\\". DO NOT USE FOR: deploying resources, provisioning infrastructure, diagnostics, security audits, or estimating costs for new resources not yet deployed.\"\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.1.0\"\n---\n\n# Azure Cost Management Skill\n\nUnified skill for all Azure cost management tasks: querying historical costs, forecasting future spending, and optimizing to reduce waste.\n\n## When to Use This Skill\n\nActivate this skill when user wants to:\n- Query or analyze Azure costs (how much am I spending, show my bill, cost breakdown)\n- Break down costs by service, resource, location, or tag\n- Analyze cost trends over time\n- Forecast future Azure spending or project end-of-month costs\n- Optimize Azure costs, reduce spending, or find savings\n- Find orphaned or unused resources\n- Rightsize Azure VMs, containers, or services\n- Generate cost optimization reports\n\n## Quick Reference\n\n| Property | Value |\n|----------|-------|\n| **Query API Endpoint** | `POST {scope}\u002Fproviders\u002FMicrosoft.CostManagement\u002Fquery?api-version=2023-11-01` |\n| **Forecast API Endpoint** | `POST {scope}\u002Fproviders\u002FMicrosoft.CostManagement\u002Fforecast?api-version=2023-11-01` |\n| **MCP Tools** | `azure__documentation`, `azure__extension_cli_generate`, `azure__get_azure_bestpractices` |\n| **CLI** | `az rest`, `az monitor metrics list`, `az resource list` |\n| **Required Role** | Cost Management Reader + Monitoring Reader + Reader on scope |\n\n## MCP Tools\n\n| Tool | Description | Parameters | When to Use |\n|------|-------------|------------|-------------|\n| `azure__documentation` | Search Azure documentation | `query` (Required): search terms | Research Cost Management API parameters and options |\n| `azure__extension_cli_generate` | Generate Azure CLI commands | `intent` (Required): task description, `cli-type` (Required): `\"az\"` | Construct `az rest` commands for cost queries |\n| `azure__get_azure_bestpractices` | Get Azure best practices | `intent` (Required): optimization context | Inform query design with cost management best practices |\n| `azure__extension_azqr` | Run Azure Quick Review compliance scan | `subscription` (Required): subscription ID, `resource-group` (Optional): resource group name | Find orphaned resources and cost optimization opportunities |\n| `azure__aks` | Azure Kubernetes Service operations | varies by sub-command | AKS cost analysis: list clusters, get node pools, inspect configuration |\n\n> 💡 **Tip:** Prefer MCP tools over direct CLI commands. Use `az rest` only when MCP tools don't cover the specific operation.\n\n---\n\n## Routing\n\nRead the user's request and follow the appropriate workflow below.\n\n| User Intent | Workflow | Example Prompts |\n|-------------|----------|-----------------|\n| Understand current costs | Cost Query Workflow (`cost-query\u002Fworkflow.md`) | \"how much am I spending\", \"cost by service\", \"show my bill\" |\n| Reduce costs \u002F find waste | Cost Optimization Workflow (`cost-optimization\u002Fworkflow.md`) | \"optimize costs\", \"find orphaned resources\", \"reduce spending\" |\n| Project future costs | Cost Forecast Workflow (`cost-forecast\u002Fworkflow.md`) | \"forecast costs\", \"end of month estimate\", \"how much will I spend\" |\n| Full cost picture | All three workflows combined | \"give me the full picture of my Azure costs\" |\n\n> **Important:** When optimizing costs, always present the total bill and cost breakdown alongside optimization recommendations.\n\n---\n\n## Scope Reference (Shared Across All Workflows)\n\n| Scope | URL Pattern |\n|-------|-------------|\n| Subscription | `\u002Fsubscriptions\u002F\u003Csubscription-id>` |\n| Resource Group | `\u002Fsubscriptions\u002F\u003Csubscription-id>\u002FresourceGroups\u002F\u003Cresource-group-name>` |\n| Management Group | `\u002Fproviders\u002FMicrosoft.Management\u002FmanagementGroups\u002F\u003Cmanagement-group-id>` |\n| Billing Account | `\u002Fproviders\u002FMicrosoft.Billing\u002FbillingAccounts\u002F\u003Cbilling-account-id>` |\n| Billing Profile | `\u002Fproviders\u002FMicrosoft.Billing\u002FbillingAccounts\u002F\u003Cbilling-account-id>\u002FbillingProfiles\u002F\u003Cbilling-profile-id>` |\n\n> 💡 **Tip:** These are scope paths only — not complete URLs. Combine with the API endpoint and version.\n\n---\n\n## Part 1: Cost Query Workflow\n\nFor the full cost query workflow (scope selection, report types, timeframes, dataset configuration, API calls, pagination, guardrails, examples, and error handling), see:\n\n📄 **Cost Query Workflow (`cost-query\u002Fworkflow.md`)**\n\n---\n\n## Part 2: Cost Optimization Workflow\n\nFor the full cost optimization workflow (prerequisites, best practices, Redis\u002FAKS-specific analysis, Azure Quick Review, resource discovery, cost queries, pricing validation, utilization metrics, and report generation), see:\n\n📄 **Cost Optimization Workflow (`cost-optimization\u002Fworkflow.md`)**\n\n---\n\n## Part 3: Cost Forecast Workflow\n\nFor the full cost forecast workflow (scope selection, time period rules, dataset configuration, forecast-specific options, API calls, response interpretation, guardrails, and error handling), see:\n\n📄 **Cost Forecast Workflow (`cost-forecast\u002Fworkflow.md`)**\n\n---\n\n## Data Classification\n\n- **ACTUAL DATA** = Retrieved from Azure Cost Management API\n- **ACTUAL METRICS** = Retrieved from Azure Monitor\n- **VALIDATED PRICING** = Retrieved from official Azure pricing pages\n- **ESTIMATED SAVINGS** = Calculated based on actual data and validated pricing\n\n## Best Practices\n\n- Always query actual costs first — never estimate or assume\n- Always present the total bill alongside optimization recommendations\n- Validate pricing from official sources — account for free tiers\n- Use REST API for cost queries (more reliable than `az costmanagement query`)\n- Always include the `ClientType: GitHubCopilotForAzure` header on all Cost Management API requests (`--headers \"ClientType=GitHubCopilotForAzure\"` in `az rest`)\n- Save audit trail — include all queries and responses\n- Include Azure Portal links for all resources\n- For costs \u003C $10\u002Fmonth, emphasize operational improvements over financial savings\n- Never execute destructive operations without explicit approval\n- On 429 responses, check all `x-ms-ratelimit-microsoft.costmanagement-*-retry-after` headers (`qpu-retry-after`, `entity-retry-after`, `tenant-retry-after`), wait for the longest value, and do not retry until that duration has elapsed. The per-scope limit (4 requests\u002Fminute) is the most restrictive.\n\n## Common Pitfalls\n\n- **Assuming costs**: Always query actual data from Cost Management API\n- **Ignoring free tiers**: Many services have generous allowances\n- **Using wrong date ranges**: 30 days for costs, 14 days for utilization\n- **Not showing the bill**: Always present cost breakdown alongside optimization recommendations\n- **Cost query failures**: Use `az rest` with JSON body, not `az costmanagement query`\n\n## Safety Requirements\n\n- Get approval before deleting resources\n- Test changes in non-production first\n- Provide dry-run commands for validation\n- Include rollback procedures\n\n## SDK Quick References\n\n- **Redis Management**: .NET (`cost-optimization\u002Fsdk\u002Fazure_resource_manager_redis_dotnet.md`)\n","# Azure Cost Management Skill\n\nUnified skill for all Azure cost management tasks: querying historical costs, forecasting future spending, and optimizing to reduce waste.\n\n## When to Use This Skill\n\nActivate this skill when user wants to:\n- Query or analyze Azure costs (how much am I spending, show my bill, cost breakdown)\n- Break down costs by service, resource, location, or tag\n- Analyze cost trends over time\n- Forecast future Azure spending or project end-of-month costs\n- Optimize Azure costs, reduce spending, or find savings\n- Find orphaned or unused resources\n- Rightsize Azure VMs, containers, or services\n- Generate cost optimization reports\n\n## Quick Reference\n\n| Property | Value |\n|----------|-------|\n| **Query API Endpoint** | `POST {scope}\u002Fproviders\u002FMicrosoft.CostManagement\u002Fquery?api-version=2023-11-01` |\n| **Forecast API Endpoint** | `POST {scope}\u002Fproviders\u002FMicrosoft.CostManagement\u002Fforecast?api-version=2023-11-01` |\n| **MCP Tools** | `azure__documentation`, `azure__extension_cli_generate`, `azure__get_azure_bestpractices` |\n| **CLI** | `az rest`, `az monitor metrics list`, `az resource list` |\n| **Required Role** | Cost Management Reader + Monitoring Reader + Reader on scope |\n\n## MCP Tools\n\n| Tool | Description | Parameters | When to Use |\n|------|-------------|------------|-------------|\n| `azure__documentation` | Search Azure documentation | `query` (Required): search terms | Research Cost Management API parameters and options |\n| `azure__extension_cli_generate` | Generate Azure CLI commands | `intent` (Required): task description, `cli-type` (Required): `\"az\"` | Construct `az rest` commands for cost queries |\n| `azure__get_azure_bestpractices` | Get Azure best practices | `intent` (Required): optimization context | Inform query design with cost management best practices |\n| `azure__extension_azqr` | Run Azure Quick Review compliance scan | `subscription` (Required): subscription ID, `resource-group` (Optional): resource group name | Find orphaned resources and cost optimization opportunities |\n| `azure__aks` | Azure Kubernetes Service operations | varies by sub-command | AKS cost analysis: list clusters, get node pools, inspect configuration |\n\n> 💡 **Tip:** Prefer MCP tools over direct CLI commands. Use `az rest` only when MCP tools don't cover the specific operation.\n\n---\n\n## Routing\n\nRead the user's request and follow the appropriate workflow below.\n\n| User Intent | Workflow | Example Prompts |\n|-------------|----------|-----------------|\n| Understand current costs | Cost Query Workflow (`cost-query\u002Fworkflow.md`) | \"how much am I spending\", \"cost by service\", \"show my bill\" |\n| Reduce costs \u002F find waste | Cost Optimization Workflow (`cost-optimization\u002Fworkflow.md`) | \"optimize costs\", \"find orphaned resources\", \"reduce spending\" |\n| Project future costs | Cost Forecast Workflow (`cost-forecast\u002Fworkflow.md`) | \"forecast costs\", \"end of month estimate\", \"how much will I spend\" |\n| Full cost picture | All three workflows combined | \"give me the full picture of my Azure costs\" |\n\n> **Important:** When optimizing costs, always present the total bill and cost breakdown alongside optimization recommendations.\n\n---\n\n## Scope Reference (Shared Across All Workflows)\n\n| Scope | URL Pattern |\n|-------|-------------|\n| Subscription | `\u002Fsubscriptions\u002F\u003Csubscription-id>` |\n| Resource Group | `\u002Fsubscriptions\u002F\u003Csubscription-id>\u002FresourceGroups\u002F\u003Cresource-group-name>` |\n| Management Group | `\u002Fproviders\u002FMicrosoft.Management\u002FmanagementGroups\u002F\u003Cmanagement-group-id>` |\n| Billing Account | `\u002Fproviders\u002FMicrosoft.Billing\u002FbillingAccounts\u002F\u003Cbilling-account-id>` |\n| Billing Profile | `\u002Fproviders\u002FMicrosoft.Billing\u002FbillingAccounts\u002F\u003Cbilling-account-id>\u002FbillingProfiles\u002F\u003Cbilling-profile-id>` |\n\n> 💡 **Tip:** These are scope paths only — not complete URLs. Combine with the API endpoint and version.\n\n---\n\n## Part 1: Cost Query Workflow\n\nFor the full cost query workflow (scope selection, report types, timeframes, dataset configuration, API calls, pagination, guardrails, examples, and error handling), see:\n\n📄 **Cost Query Workflow (`cost-query\u002Fworkflow.md`)**\n\n---\n\n## Part 2: Cost Optimization Workflow\n\nFor the full cost optimization workflow (prerequisites, best practices, Redis\u002FAKS-specific analysis, Azure Quick Review, resource discovery, cost queries, pricing validation, utilization metrics, and report generation), see:\n\n📄 **Cost Optimization Workflow (`cost-optimization\u002Fworkflow.md`)**\n\n---\n\n## Part 3: Cost Forecast Workflow\n\nFor the full cost forecast workflow (scope selection, time period rules, dataset configuration, forecast-specific options, API calls, response interpretation, guardrails, and error handling), see:\n\n📄 **Cost Forecast Workflow (`cost-forecast\u002Fworkflow.md`)**\n\n---\n\n## Data Classification\n\n- **ACTUAL DATA** = Retrieved from Azure Cost Management API\n- **ACTUAL METRICS** = Retrieved from Azure Monitor\n- **VALIDATED PRICING** = Retrieved from official Azure pricing pages\n- **ESTIMATED SAVINGS** = Calculated based on actual data and validated pricing\n\n## Best Practices\n\n- Always query actual costs first — never estimate or assume\n- Always present the total bill alongside optimization recommendations\n- Validate pricing from official sources — account for free tiers\n- Use REST API for cost queries (more reliable than `az costmanagement query`)\n- Always include the `ClientType: GitHubCopilotForAzure` header on all Cost Management API requests (`--headers \"ClientType=GitHubCopilotForAzure\"` in `az rest`)\n- Save audit trail — include all queries and responses\n- Include Azure Portal links for all resources\n- For costs \u003C $10\u002Fmonth, emphasize operational improvements over financial savings\n- Never execute destructive operations without explicit approval\n- On 429 responses, check all `x-ms-ratelimit-microsoft.costmanagement-*-retry-after` headers (`qpu-retry-after`, `entity-retry-after`, `tenant-retry-after`), wait for the longest value, and do not retry until that duration has elapsed. The per-scope limit (4 requests\u002Fminute) is the most restrictive.\n\n## Common Pitfalls\n\n- **Assuming costs**: Always query actual data from Cost Management API\n- **Ignoring free tiers**: Many services have generous allowances\n- **Using wrong date ranges**: 30 days for costs, 14 days for utilization\n- **Not showing the bill**: Always present cost breakdown alongside optimization recommendations\n- **Cost query failures**: Use `az rest` with JSON body, not `az costmanagement query`\n\n## Safety Requirements\n\n- Get approval before deleting resources\n- Test changes in non-production first\n- Provide dry-run commands for validation\n- Include rollback procedures\n\n## SDK Quick References\n\n- **Redis Management**: .NET (`cost-optimization\u002Fsdk\u002Fazure_resource_manager_redis_dotnet.md`)\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"version":51},"Microsoft","1.1.0","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fofficial_microsoft_azure_cost",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill azure-cost",{"tool":67,"command":68},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill azure-cost",{"tool":70,"command":71},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill azure-cost","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_microsoft_azure_cost\u002Fskill.md",true,[],[76,106,129,151,171,194],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":85,"publishedAt":105},"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",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[86,87,88,89,90,91,92,93,94,95,96,97,98,99,36,100,101,102,103,104],"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":105},"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",[112],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[86,114,115,90,116,117,118,119,99,120,36,121,100,122,123,124,125,126,127,128],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":105},"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",[135],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[86,137,138,90,139,119,140,36,141,121,100,142,143,144,145,146,147,148,149,150],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":105},"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",[157],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[159,90,160,147,161,162,163,164,150,165,166,167,36,168,121,100,169,170,101,86],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":180,"publishedAt":105},"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",[177],{"categoryNo":178,"categoryName":179,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[181,182,183,184,139,185,186,187,128,148,119,188,189,140,190,167,191,192,193,36],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"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",[200],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[202,203,204,205,206,96,207,164,208,99,209,210,36,86,211,212,213,214,215,216],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue"]