[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADX93JVT6FV5PP7JQK7GPB":3,"skill-same:01M6ADX93JVT6FV5PP7JQK7GPB":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":18,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6ADX93JVT6FV5PP7JQK7GPB","oo-component-documentation",null,"Create or update standardized object-oriented component documentation using a shared template plus mode-specific guidance for new and existing docs.","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\u002Foo-component-documentation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"component","documentation","oo component documentation","docs","create","update","template","guidance","shared","mode","object","for","Existing","new","2026-11-10 10:12:30",false,"---\nname: oo-component-documentation\ndescription: 'Create or update standardized object-oriented component documentation using a shared template plus mode-specific guidance for new and existing docs.'\n---\n\n# OO Component Documentation\n\nCreate new documentation for an object-oriented component or update an existing component documentation file by analyzing the current implementation.\n\n## Determine the mode first\n\nChoose the workflow before writing anything:\n\n1. Use **update mode** when the user provides an existing documentation Markdown file, points to a docs path, or explicitly asks to refresh or revise existing documentation. Follow [references\u002Fupdate-mode.md](references\u002Fupdate-mode.md).\n2. Use **create mode** when the user provides a source file or folder, points to a component path, or asks to generate documentation from code. Follow [references\u002Fcreate-mode.md](references\u002Fcreate-mode.md).\n3. If both code and an existing documentation file are provided, treat the existing documentation file as the output target and use the current source code as the source of truth.\n4. If the request is ambiguous, infer the mode from the path type whenever possible: existing Markdown documentation file means update mode; source\u002Fcomponent path means create mode.\n\n## Documentation standards\n\n- DOC-001: Follow C4 Model documentation levels (Context, Containers, Components, Code)\n- DOC-002: Align with Arc42 software architecture documentation template\n- DOC-003: Comply with IEEE 1016 Software Design Description standard\n- DOC-004: Use Agile Documentation principles (just enough documentation that adds value)\n- DOC-005: Target developers and maintainers as the primary audience\n\n## Shared analysis guidance\n\n- ANA-001: Determine the primary component boundary and whether the input represents a folder, file, or existing documentation target\n- ANA-002: Examine source code files for class structures, inheritance, composition, and interfaces\n- ANA-003: Identify design patterns, architectural decisions, and integration points\n- ANA-004: Document or refresh public APIs, interfaces, dependencies, and usage patterns\n- ANA-005: Capture method parameters, return values, asynchronous behavior, exceptions, and lifecycle concerns\n- ANA-006: Assess performance, security, reliability, maintainability, and extensibility characteristics\n- ANA-007: Infer data flow, collaboration patterns, and relationships with surrounding components\n- ANA-008: Keep the documentation grounded in the implementation; avoid inventing behavior that is not supported by the code\n\n## Shared output requirements\n\n- Use [assets\u002Fdocumentation-template.md](assets\u002Fdocumentation-template.md) as the canonical section checklist and baseline structure.\n- Keep the output in Markdown with a clear heading hierarchy, tables where useful, code blocks for examples, and Mermaid diagrams when architecture relationships need to be visualized.\n- Make examples and interface descriptions match the current implementation instead of generic placeholders.\n- Include only information that can be supported by the code, project structure, configuration, or clearly stated assumptions.\n- When source coverage is incomplete, document the limitation explicitly instead of guessing.\n\n## Language-specific optimizations\n\n- LNG-001: **C#\u002F.NET** - async\u002Fawait, dependency injection, configuration, disposal, options patterns\n- LNG-002: **Java** - Spring framework, annotations, exception handling, packaging, dependency injection\n- LNG-003: **TypeScript\u002FJavaScript** - modules, async patterns, types, npm dependencies, runtime boundaries\n- LNG-004: **Python** - packages, virtual environments, type hints, testing, dependency management\n\n## Error handling\n\n- ERR-001: If the path does not exist, explain what path was expected and whether the skill needs a source path or an existing documentation file\n- ERR-002: If no relevant source files are found, document the gap and suggest the likely locations to inspect next\n- ERR-003: If the documentation target cannot be inferred from the request, state the ambiguity and ask for the missing path only when inference is not possible\n- ERR-004: If the code uses non-standard architectural patterns, document the custom approach rather than forcing it into a generic pattern\n- ERR-005: If source access is incomplete, continue with available evidence and clearly call out any unsupported sections\n\n## Workflow\n\n1. Determine whether the task is create mode or update mode.\n2. Inspect the component implementation and any related files needed to understand its public surface area and internal structure.\n3. Use [assets\u002Fdocumentation-template.md](assets\u002Fdocumentation-template.md) as the shared documentation scaffold.\n4. Apply the mode-specific rules in [references\u002Fcreate-mode.md](references\u002Fcreate-mode.md) or [references\u002Fupdate-mode.md](references\u002Fupdate-mode.md).\n5. Produce or revise the documentation so that diagrams, examples, interfaces, dependencies, and quality attributes reflect the current implementation.\n\n## Completion criteria\n\n- The documentation clearly identifies the component purpose, architecture, interfaces, implementation details, usage patterns, quality attributes, and references.\n- Front matter fields are accurate for the selected mode.\n- Examples and diagrams match the implementation.\n- Any unknowns, gaps, or assumptions are explicitly called out.\n","# OO Component Documentation\n\nCreate new documentation for an object-oriented component or update an existing component documentation file by analyzing the current implementation.\n\n## Determine the mode first\n\nChoose the workflow before writing anything:\n\n1. Use **update mode** when the user provides an existing documentation Markdown file, points to a docs path, or explicitly asks to refresh or revise existing documentation. Follow [references\u002Fupdate-mode.md](references\u002Fupdate-mode.md).\n2. Use **create mode** when the user provides a source file or folder, points to a component path, or asks to generate documentation from code. Follow [references\u002Fcreate-mode.md](references\u002Fcreate-mode.md).\n3. If both code and an existing documentation file are provided, treat the existing documentation file as the output target and use the current source code as the source of truth.\n4. If the request is ambiguous, infer the mode from the path type whenever possible: existing Markdown documentation file means update mode; source\u002Fcomponent path means create mode.\n\n## Documentation standards\n\n- DOC-001: Follow C4 Model documentation levels (Context, Containers, Components, Code)\n- DOC-002: Align with Arc42 software architecture documentation template\n- DOC-003: Comply with IEEE 1016 Software Design Description standard\n- DOC-004: Use Agile Documentation principles (just enough documentation that adds value)\n- DOC-005: Target developers and maintainers as the primary audience\n\n## Shared analysis guidance\n\n- ANA-001: Determine the primary component boundary and whether the input represents a folder, file, or existing documentation target\n- ANA-002: Examine source code files for class structures, inheritance, composition, and interfaces\n- ANA-003: Identify design patterns, architectural decisions, and integration points\n- ANA-004: Document or refresh public APIs, interfaces, dependencies, and usage patterns\n- ANA-005: Capture method parameters, return values, asynchronous behavior, exceptions, and lifecycle concerns\n- ANA-006: Assess performance, security, reliability, maintainability, and extensibility characteristics\n- ANA-007: Infer data flow, collaboration patterns, and relationships with surrounding components\n- ANA-008: Keep the documentation grounded in the implementation; avoid inventing behavior that is not supported by the code\n\n## Shared output requirements\n\n- Use [assets\u002Fdocumentation-template.md](assets\u002Fdocumentation-template.md) as the canonical section checklist and baseline structure.\n- Keep the output in Markdown with a clear heading hierarchy, tables where useful, code blocks for examples, and Mermaid diagrams when architecture relationships need to be visualized.\n- Make examples and interface descriptions match the current implementation instead of generic placeholders.\n- Include only information that can be supported by the code, project structure, configuration, or clearly stated assumptions.\n- When source coverage is incomplete, document the limitation explicitly instead of guessing.\n\n## Language-specific optimizations\n\n- LNG-001: **C#\u002F.NET** - async\u002Fawait, dependency injection, configuration, disposal, options patterns\n- LNG-002: **Java** - Spring framework, annotations, exception handling, packaging, dependency injection\n- LNG-003: **TypeScript\u002FJavaScript** - modules, async patterns, types, npm dependencies, runtime boundaries\n- LNG-004: **Python** - packages, virtual environments, type hints, testing, dependency management\n\n## Error handling\n\n- ERR-001: If the path does not exist, explain what path was expected and whether the skill needs a source path or an existing documentation file\n- ERR-002: If no relevant source files are found, document the gap and suggest the likely locations to inspect next\n- ERR-003: If the documentation target cannot be inferred from the request, state the ambiguity and ask for the missing path only when inference is not possible\n- ERR-004: If the code uses non-standard architectural patterns, document the custom approach rather than forcing it into a generic pattern\n- ERR-005: If source access is incomplete, continue with available evidence and clearly call out any unsupported sections\n\n## Workflow\n\n1. Determine whether the task is create mode or update mode.\n2. Inspect the component implementation and any related files needed to understand its public surface area and internal structure.\n3. Use [assets\u002Fdocumentation-template.md](assets\u002Fdocumentation-template.md) as the shared documentation scaffold.\n4. Apply the mode-specific rules in [references\u002Fcreate-mode.md](references\u002Fcreate-mode.md) or [references\u002Fupdate-mode.md](references\u002Fupdate-mode.md).\n5. Produce or revise the documentation so that diagrams, examples, interfaces, dependencies, and quality attributes reflect the current implementation.\n\n## Completion criteria\n\n- The documentation clearly identifies the component purpose, architecture, interfaces, implementation details, usage patterns, quality attributes, and references.\n- Front matter fields are accurate for the selected mode.\n- Examples and diagrams match the implementation.\n- Any unknowns, gaps, or assumptions are explicitly called out.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Foo-component-documentation",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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add github\u002Fawesome-copilot --skill oo-component-documentation",{"tool":54,"command":55},"bunx","bunx skills add github\u002Fawesome-copilot --skill oo-component-documentation",{"tool":57,"command":58},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill oo-component-documentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Foo-component-documentation\u002FSKILL.md",true,[62,68,74],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"assets\u002Fdocumentation-template.md","ASSET","资产文件",2887,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Foo-component-documentation\u002Fassets\u002Fdocumentation-template.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fcreate-mode.md","REFERENCE","参考文档",1929,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Foo-component-documentation\u002Freferences\u002Fcreate-mode.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fupdate-mode.md",2047,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Foo-component-documentation\u002Freferences\u002Fupdate-mode.md",[79,114,140,170,204,221],{"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":93,"publishedAt":33},"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",[85,90],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":91,"categoryName":92,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000023","Skill与智能体开发",[94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":33},"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",[120],{"categoryNo":91,"categoryName":92,"taxonomyType":88,"taxonomyTypeDesc":89},[122,123,124,125,126,127,30,128,129,130,131,132,133,134,135,136,137,25,138,139],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","release","reconcile",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":152,"publishedAt":33},"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",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[153,154,155,156,157,158,30,98,159,160,161,162,163,164,165,110,166,167,168,169],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":174,"sourceHtmlUrl":175,"categories":176,"keywords":181,"publishedAt":33},"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",[177,180],{"categoryNo":178,"categoryName":179,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},[182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,99,197,198,199,200,201,30,202,203],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":208,"licenseFileUrl":209,"sourceHtmlUrl":210,"categories":211,"keywords":217,"publishedAt":33},"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",[212,213,216],{"categoryNo":178,"categoryName":179,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":214,"categoryName":215,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":91,"categoryName":92,"taxonomyType":88,"taxonomyTypeDesc":89},[218,125,191,219,220],"resemble detect","https","identity",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":208,"licenseFileUrl":225,"sourceHtmlUrl":226,"categories":227,"keywords":232,"publishedAt":33},"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",[228,231],{"categoryNo":229,"categoryName":230,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":91,"categoryName":92,"taxonomyType":88,"taxonomyTypeDesc":89},[233,234,235,236,154,100,9,124,237,238,219,239,240,241,242,243,244,245,246,247,248,249,108,250,251,252,253],"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"]