[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEAPXRFZNHXXH7Q5F0RHPC":3,"skill-same:01M6AEAPXRFZNHXXH7Q5F0RHPC":60},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6AEAPXRFZNHXXH7Q5F0RHPC","update-specification",null,"Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41046,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fupdate-specification\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"update","update specification","specification","generative ai","code","file","requirements","updates","for","Existing","generative","new","2026-11-10 10:12:30",false,"---\nname: update-specification\ndescription: 'Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.'\n---\n\n# Update Specification\n\nYour goal is to update the existing specification file `${file}` based on new requirements or updates to any existing code.\n\nThe specification file must define the requirements, constraints, and interfaces for the solution components in a manner that is clear, unambiguous, and structured for effective use by Generative AIs. Follow established documentation standards and ensure the content is machine-readable and self-contained.\n\n## Best Practices for AI-Ready Specifications\n\n- Use precise, explicit, and unambiguous language.\n- Clearly distinguish between requirements, constraints, and recommendations.\n- Use structured formatting (headings, lists, tables) for easy parsing.\n- Avoid idioms, metaphors, or context-dependent references.\n- Define all acronyms and domain-specific terms.\n- Include examples and edge cases where applicable.\n- Ensure the document is self-contained and does not rely on external context.\n\nThe specification should be saved in the `\u002Fspec\u002F` directory and named according to the following convention: `[a-z0-9-]+.md`, where the name should be descriptive of the specification's content and starting with the highlevel purpose, which is one of [schema, tool, data, infrastructure, process, architecture, or design].\n\nThe specification file must be formatted in well formed Markdown.\n\nSpecification files must follow the template below, ensuring that all sections are filled out appropriately. The front matter for the markdown should be structured correctly as per the example following:\n\n```md\n---\ntitle: [Concise Title Describing the Specification's Focus]\nversion: [Optional: e.g., 1.0, Date]\ndate_created: [YYYY-MM-DD]\nlast_updated: [Optional: YYYY-MM-DD]\nowner: [Optional: Team\u002FIndividual responsible for this spec]\ntags: [Optional: List of relevant tags or categories, e.g., `infrastructure`, `process`, `design`, `app` etc]\n---\n\n# Introduction\n\n[A short concise introduction to the specification and the goal it is intended to achieve.]\n\n## 1. Purpose & Scope\n\n[Provide a clear, concise description of the specification's purpose and the scope of its application. State the intended audience and any assumptions.]\n\n## 2. Definitions\n\n[List and define all acronyms, abbreviations, and domain-specific terms used in this specification.]\n\n## 3. Requirements, Constraints & Guidelines\n\n[Explicitly list all requirements, constraints, rules, and guidelines. Use bullet points or tables for clarity.]\n\n- **REQ-001**: Requirement 1\n- **SEC-001**: Security Requirement 1\n- **[3 LETTERS]-001**: Other Requirement 1\n- **CON-001**: Constraint 1\n- **GUD-001**: Guideline 1\n- **PAT-001**: Pattern to follow 1\n\n## 4. Interfaces & Data Contracts\n\n[Describe the interfaces, APIs, data contracts, or integration points. Use tables or code blocks for schemas and examples.]\n\n## 5. Acceptance Criteria\n\n[Define clear, testable acceptance criteria for each requirement using Given-When-Then format where appropriate.]\n\n- **AC-001**: Given [context], When [action], Then [expected outcome]\n- **AC-002**: The system shall [specific behavior] when [condition]\n- **AC-003**: [Additional acceptance criteria as needed]\n\n## 6. Test Automation Strategy\n\n[Define the testing approach, frameworks, and automation requirements.]\n\n- **Test Levels**: Unit, Integration, End-to-End\n- **Frameworks**: MSTest, FluentAssertions, Moq (for .NET applications)\n- **Test Data Management**: [approach for test data creation and cleanup]\n- **CI\u002FCD Integration**: [automated testing in GitHub Actions pipelines]\n- **Coverage Requirements**: [minimum code coverage thresholds]\n- **Performance Testing**: [approach for load and performance testing]\n\n## 7. Rationale & Context\n\n[Explain the reasoning behind the requirements, constraints, and guidelines. Provide context for design decisions.]\n\n## 8. Dependencies & External Integrations\n\n[Define the external systems, services, and architectural dependencies required for this specification. Focus on **what** is needed rather than **how** it's implemented. Avoid specific package or library versions unless they represent architectural constraints.]\n\n### External Systems\n- **EXT-001**: [External system name] - [Purpose and integration type]\n\n### Third-Party Services\n- **SVC-001**: [Service name] - [Required capabilities and SLA requirements]\n\n### Infrastructure Dependencies\n- **INF-001**: [Infrastructure component] - [Requirements and constraints]\n\n### Data Dependencies\n- **DAT-001**: [External data source] - [Format, frequency, and access requirements]\n\n### Technology Platform Dependencies\n- **PLT-001**: [Platform\u002Fruntime requirement] - [Version constraints and rationale]\n\n### Compliance Dependencies\n- **COM-001**: [Regulatory or compliance requirement] - [Impact on implementation]\n\n**Note**: This section should focus on architectural and business dependencies, not specific package implementations. For example, specify \"OAuth 2.0 authentication library\" rather than \"Microsoft.AspNetCore.Authentication.JwtBearer v6.0.1\".\n\n## 9. Examples & Edge Cases\n\n```code\n\u002F\u002F Code snippet or data example demonstrating the correct application of the guidelines, including edge cases\n```\n\n## 10. Validation Criteria\n\n[List the criteria or tests that must be satisfied for compliance with this specification.]\n\n## 11. Related Specifications \u002F Further Reading\n\n[Link to related spec 1]\n[Link to relevant external documentation]\n\n```\n","# Update Specification\n\nYour goal is to update the existing specification file `${file}` based on new requirements or updates to any existing code.\n\nThe specification file must define the requirements, constraints, and interfaces for the solution components in a manner that is clear, unambiguous, and structured for effective use by Generative AIs. Follow established documentation standards and ensure the content is machine-readable and self-contained.\n\n## Best Practices for AI-Ready Specifications\n\n- Use precise, explicit, and unambiguous language.\n- Clearly distinguish between requirements, constraints, and recommendations.\n- Use structured formatting (headings, lists, tables) for easy parsing.\n- Avoid idioms, metaphors, or context-dependent references.\n- Define all acronyms and domain-specific terms.\n- Include examples and edge cases where applicable.\n- Ensure the document is self-contained and does not rely on external context.\n\nThe specification should be saved in the `\u002Fspec\u002F` directory and named according to the following convention: `[a-z0-9-]+.md`, where the name should be descriptive of the specification's content and starting with the highlevel purpose, which is one of [schema, tool, data, infrastructure, process, architecture, or design].\n\nThe specification file must be formatted in well formed Markdown.\n\nSpecification files must follow the template below, ensuring that all sections are filled out appropriately. The front matter for the markdown should be structured correctly as per the example following:\n\n```md\n---\ntitle: [Concise Title Describing the Specification's Focus]\nversion: [Optional: e.g., 1.0, Date]\ndate_created: [YYYY-MM-DD]\nlast_updated: [Optional: YYYY-MM-DD]\nowner: [Optional: Team\u002FIndividual responsible for this spec]\ntags: [Optional: List of relevant tags or categories, e.g., `infrastructure`, `process`, `design`, `app` etc]\n---\n\n# Introduction\n\n[A short concise introduction to the specification and the goal it is intended to achieve.]\n\n## 1. Purpose & Scope\n\n[Provide a clear, concise description of the specification's purpose and the scope of its application. State the intended audience and any assumptions.]\n\n## 2. Definitions\n\n[List and define all acronyms, abbreviations, and domain-specific terms used in this specification.]\n\n## 3. Requirements, Constraints & Guidelines\n\n[Explicitly list all requirements, constraints, rules, and guidelines. Use bullet points or tables for clarity.]\n\n- **REQ-001**: Requirement 1\n- **SEC-001**: Security Requirement 1\n- **[3 LETTERS]-001**: Other Requirement 1\n- **CON-001**: Constraint 1\n- **GUD-001**: Guideline 1\n- **PAT-001**: Pattern to follow 1\n\n## 4. Interfaces & Data Contracts\n\n[Describe the interfaces, APIs, data contracts, or integration points. Use tables or code blocks for schemas and examples.]\n\n## 5. Acceptance Criteria\n\n[Define clear, testable acceptance criteria for each requirement using Given-When-Then format where appropriate.]\n\n- **AC-001**: Given [context], When [action], Then [expected outcome]\n- **AC-002**: The system shall [specific behavior] when [condition]\n- **AC-003**: [Additional acceptance criteria as needed]\n\n## 6. Test Automation Strategy\n\n[Define the testing approach, frameworks, and automation requirements.]\n\n- **Test Levels**: Unit, Integration, End-to-End\n- **Frameworks**: MSTest, FluentAssertions, Moq (for .NET applications)\n- **Test Data Management**: [approach for test data creation and cleanup]\n- **CI\u002FCD Integration**: [automated testing in GitHub Actions pipelines]\n- **Coverage Requirements**: [minimum code coverage thresholds]\n- **Performance Testing**: [approach for load and performance testing]\n\n## 7. Rationale & Context\n\n[Explain the reasoning behind the requirements, constraints, and guidelines. Provide context for design decisions.]\n\n## 8. Dependencies & External Integrations\n\n[Define the external systems, services, and architectural dependencies required for this specification. Focus on **what** is needed rather than **how** it's implemented. Avoid specific package or library versions unless they represent architectural constraints.]\n\n### External Systems\n- **EXT-001**: [External system name] - [Purpose and integration type]\n\n### Third-Party Services\n- **SVC-001**: [Service name] - [Required capabilities and SLA requirements]\n\n### Infrastructure Dependencies\n- **INF-001**: [Infrastructure component] - [Requirements and constraints]\n\n### Data Dependencies\n- **DAT-001**: [External data source] - [Format, frequency, and access requirements]\n\n### Technology Platform Dependencies\n- **PLT-001**: [Platform\u002Fruntime requirement] - [Version constraints and rationale]\n\n### Compliance Dependencies\n- **COM-001**: [Regulatory or compliance requirement] - [Impact on implementation]\n\n**Note**: This section should focus on architectural and business dependencies, not specific package implementations. For example, specify \"OAuth 2.0 authentication library\" rather than \"Microsoft.AspNetCore.Authentication.JwtBearer v6.0.1\".\n\n## 9. Examples & Edge Cases\n\n```code\n\u002F\u002F Code snippet or data example demonstrating the correct application of the guidelines, including edge cases\n```\n\n## 10. Validation Criteria\n\n[List the criteria or tests that must be satisfied for compliance with this specification.]\n\n## 11. Related Specifications \u002F Further Reading\n\n[Link to related spec 1]\n[Link to relevant external documentation]\n\n```\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fupdate-specification",5340,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-11 13:41:32",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add github\u002Fawesome-copilot --skill update-specification",{"tool":52,"command":53},"bunx","bunx skills add github\u002Fawesome-copilot --skill update-specification",{"tool":55,"command":56},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill update-specification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fupdate-specification\u002FSKILL.md",true,[],[61,96,123,152,185,202],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":75,"publishedAt":31},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[67,72],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000023","Skill与智能体开发",[76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":103,"publishedAt":31},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[102],{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},[104,105,106,107,108,109,27,110,111,112,113,114,115,116,117,118,119,120,121,122],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":135,"publishedAt":31},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[130],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[136,23,137,138,139,140,27,80,141,142,143,144,145,146,147,92,148,149,150,151],"custom","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"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":156,"sourceHtmlUrl":157,"categories":158,"keywords":163,"publishedAt":31},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[159,162],{"categoryNo":160,"categoryName":161,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},[164,165,166,167,168,169,170,171,172,24,173,174,175,176,177,81,178,179,180,181,182,27,183,184],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":189,"licenseFileUrl":190,"sourceHtmlUrl":191,"categories":192,"keywords":198,"publishedAt":31},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[193,194,197],{"categoryNo":160,"categoryName":161,"taxonomyType":70,"taxonomyTypeDesc":71},{"categoryNo":195,"categoryName":196,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},[199,107,24,200,201],"resemble detect","https","identity",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":189,"licenseFileUrl":206,"sourceHtmlUrl":207,"categories":208,"keywords":213,"publishedAt":31},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[209,212],{"categoryNo":210,"categoryName":211,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},[214,215,216,217,23,82,9,106,218,219,200,220,221,222,223,224,225,226,227,228,229,230,90,231,232,233,234],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]