[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADH8MA9FCG5C69PJN14N0Z":3,"skill-same:01M6ADH8MA9FCG5C69PJN14N0Z":109},{"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":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6ADH8MA9FCG5C69PJN14N0Z","efcore-d2-db-diagram",null,"Generate D2 database diagrams from Entity Framework Core models. USE FOR: EF Core database diagram, Entity Framework Core ERD, DbContext diagram, C# entity relationship diagram, PostgreSQL schema visualization, generate .d2 file from EF Core entities, Fluent API mapping diagram, migrations-based database diagram, table relationships, owned types, many-to-many join tables, indexes and constraints. DO NOT USE FOR: runtime debugging, database migration execution, schema deployment, SQL performance tuning, or draw.io diagrams.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fefcore-d2-db-diagram\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"diagram","db","d2","efcore d2 db diagram","file","types","join","io","relationship","diagrams","framework core","api","ef core","performance","postgresql","database","framework","visualization","generate","core","debugging","deployment","sql","fluent","2026-11-10 10:12:30",false,"---\nname: efcore-d2-db-diagram\ndescription: \"Generate D2 database diagrams from Entity Framework Core models. USE FOR: EF Core database diagram, Entity Framework Core ERD, DbContext diagram, C# entity relationship diagram, PostgreSQL schema visualization, generate .d2 file from EF Core entities, Fluent API mapping diagram, migrations-based database diagram, table relationships, owned types, many-to-many join tables, indexes and constraints. DO NOT USE FOR: runtime debugging, database migration execution, schema deployment, SQL performance tuning, or draw.io diagrams.\"\n---\n\n# EF Core D2 Database Diagram Generator\n\n## When to Use\n\nUse this skill when the user wants to generate a database \u002F ERD diagram from an Entity Framework Core codebase.\n\nTypical requests:\n\n- Generate a D2 database diagram from EF Core entities.\n- Visualize tables, columns, primary keys, foreign keys and relationships.\n- Analyze `DbContext`, `DbSet\u003CT>`, `IEntityTypeConfiguration\u003CT>`, Fluent API and migrations.\n- Produce a `.d2` file renderable to SVG\u002FPNG with the `d2` CLI.\n- Document the database model of an ASP.NET Core \u002F .NET project.\n\n## Goal\n\nCreate a readable D2 entity-relationship diagram that reflects the actual EF Core persistence model, not only the raw C# class shape.\n\nThe diagram must prioritize:\n\n1. Database tables and relationships.\n2. Primary keys, foreign keys, required\u002Foptional columns.\n3. Owned types and value objects.\n4. Many-to-many relationships and join tables.\n5. Indexes, unique constraints and table names.\n6. EF Core conventions only when explicit mapping is absent.\n\nOutput is `.d2` source code. It can be rendered to SVG or PNG via the `d2` CLI.\n\n## Tools\n\n- **d2 CLI**: render `.d2` files to SVG\u002FPNG.\n  - `d2 input.d2 output.svg`\n  - `d2 --layout=elk input.d2 output.svg`\n- **d2 fmt**: format D2 files.\n  - `d2 fmt input.d2`\n- No MCP server is required. The skill generates D2 source code as text.\n\n## Recommended Workflow\n\n1. Read the EF Core project structure.\n2. Locate all `DbContext` classes.\n3. Locate all `DbSet\u003CT>` declarations.\n4. Locate entity classes, owned types, enum types and value objects.\n5. Read `OnModelCreating` and all `IEntityTypeConfiguration\u003CT>` classes.\n6. Read migrations when available to confirm table names, join tables, indexes and delete behaviors.\n7. Build a normalized database model before writing D2.\n8. Ask the mandatory diagram questionnaire before generation.\n9. Generate the `.d2` file using the database model, not raw class nesting.\n10. Validate D2 syntax with `d2 fmt` before delivery.\n11. Render with `d2 --layout=elk schema.d2 schema.svg` when possible.\n12. If regenerating, re-read EF Core mappings and migrations first.\n\n## Mandatory Questions Before Diagram Generation\n\nAsk these questions for every new diagram and every regeneration unless the user already answered them in the same request.\n\n1. `Which DbContext should be diagrammed? (auto-detect\u002Fall\u002Fspecific name)`\n2. `Display columns? (all\u002Fkey-only\u002Fnone)`\n3. `Display column types? (Yes\u002FNo)`\n4. `Display nullable\u002Frequired markers? (Yes\u002FNo)`\n5. `Display indexes and unique constraints? (Yes\u002FNo)`\n6. `Display enum values? (Yes\u002FNo)`\n7. `Display owned types? (inline\u002Fseparate\u002Fhide)`\n8. `Display many-to-many join tables? (explicit\u002Fcompact\u002Fhide)`\n9. `Display audit\u002Ftechnical tables? (Yes\u002FNo)`\n10. `Display migration-only tables not present as entities? (Yes\u002FNo)`\n11. `Which grouping mode? (bounded-context\u002Fschema\u002Fnamespace\u002Fflat)`\n12. `Which layout engine? (elk\u002Fdagre\u002Ftala)`\n13. `Which output format? (d2\u002Fsvg\u002Fpng)`\n\nDefault values, when the user asks for a quick generation:\n\n- DbContext: `auto-detect`\n- Columns: `key-only`\n- Column types: `Yes`\n- Nullable markers: `Yes`\n- Indexes: `Yes`\n- Enums: `No`\n- Owned types: `inline`\n- Join tables: `explicit`\n- Audit\u002Ftechnical tables: `No`\n- Migration-only tables: `Yes`\n- Grouping: `bounded-context`\n- Layout: `elk`\n- Output: `d2`\n\n## Reference Documents\n\nLoad these on demand when needed:\n\n| Reference | When to load |\n|---|---|\n| `references\u002Fefcore-model-extraction.md` | Rules for reading DbContext, DbSet, Fluent API, configurations and migrations |\n| `references\u002Fd2-erd-style.md` | D2 syntax and visual conventions for ERD diagrams |\n| `references\u002Frelationship-rules.md` | How to infer one-to-one, one-to-many, many-to-many and owned relationships |\n| `references\u002Fgrouping-modes.md` | Rules for bounded-context, schema, namespace and flat grouping |\n| `references\u002Fquality-gate.md` | Final checklist before delivering the generated diagram |\n\n## EF Core Extraction Rules\n\n### Source Priority\n\nUse this priority order when sources disagree:\n\n1. Latest applied migration \u002F migration snapshot.\n2. Fluent API configuration in `OnModelCreating` or `IEntityTypeConfiguration\u003CT>`.\n3. Data annotations.\n4. EF Core conventions.\n5. Raw C# class shape.\n\n### Required EF Core Concepts to Detect\n\nDetect and represent:\n\n- `DbContext` and `DbSet\u003CT>`.\n- Entity class names and actual table names from `ToTable`.\n- Schema names from `ToTable(\"Table\", \"schema\")`.\n- Primary keys from `HasKey`, `[Key]`, conventions and migrations.\n- Composite keys.\n- Foreign keys from `HasForeignKey`, navigation properties and migration operations.\n- Delete behavior when explicit: `Cascade`, `Restrict`, `NoAction`, `SetNull`, `ClientSetNull`.\n- Required\u002Foptional relationship markers.\n- Owned types from `OwnsOne`, `OwnsMany` and `[Owned]`.\n- Many-to-many relationships from `UsingEntity` and implicit EF Core join tables.\n- Indexes from `HasIndex`, `IsUnique` and migrations.\n- Alternate keys from `HasAlternateKey`.\n- Shadow properties configured in Fluent API.\n- Value conversions when they affect persisted type or readability.\n- Enum properties.\n- Ignored properties and ignored entities.\n\n## Diagram Rendering Rules\n\n### Tables\n\nRepresent each persisted table as a D2 node with `shape: sql_table` when possible.\n\nUse this content convention:\n\n```d2\nClients: {\n  shape: sql_table\n  constraint: primary_key\n  Id: uuid {constraint: primary_key}\n  Name: text\n  Status: enum\n}\n```\n\nIf `sql_table` is unavailable or causes validation issues, fallback to a rectangle with structured text.\n\n### Relationships\n\nUse directional edges from dependent table to principal table.\n\nLabels must include relationship cardinality and FK name when known:\n\n```d2\nOffers.ClientId -> Clients.Id: \"N:1 FK_Offers_Clients_ClientId\"\n```\n\nUse these cardinality labels:\n\n- `1:1`\n- `1:N`\n- `N:1`\n- `N:N`\n- `owned`\n\n### Owned Types\n\nOwned types default to inline rendering.\n\nInline example:\n\n```d2\nClients: {\n  shape: sql_table\n  Id: uuid {constraint: primary_key}\n  Address.Street: text\n  Address.ZipCode: text\n  Address.City: text\n}\n```\n\nIf the user chooses `separate`, represent owned types as visually subordinate tables and use an `owned` relationship.\n\n### Many-to-Many\n\nDefault to explicit join tables because EF Core creates real tables.\n\nFor implicit many-to-many relationships, create a generated join table node and mark it as `implicit join`.\n\n### Technical Tables\n\nHide technical tables by default unless requested.\n\nExamples:\n\n- `__EFMigrationsHistory`\n- Hangfire tables\n- ASP.NET Identity tables\n- Audit logs\n- Outbox tables\n\nIf technical tables are hidden, mention them in the summary after the diagram.\n\n## Grouping Modes\n\n- `bounded-context`: group by detected domain area or folder\u002Fmodule.\n- `schema`: group by database schema, e.g. `public`, `auth`, `billing`.\n- `namespace`: group by C# namespace.\n- `flat`: no containers, all tables at the same level.\n\n## Style Rules\n\nUse consistent styles:\n\n- Primary entity tables: solid border.\n- Join tables: dashed border.\n- Owned types: lighter stroke or nested inline fields.\n- Technical tables: muted style.\n- External tables or migration-only tables: dotted border.\n- Required relationships: solid line.\n- Optional relationships: dashed line.\n- Cascade delete: label suffix `cascade`.\n\n## Quality Gate Before Delivery\n\nBefore delivering the diagram, verify:\n\n- [ ] The selected DbContext is clear.\n- [ ] All `DbSet\u003CT>` entities are considered.\n- [ ] Fluent API configurations are read.\n- [ ] Migrations are checked when present.\n- [ ] Table names and schema names match EF Core mapping.\n- [ ] Primary keys are present.\n- [ ] Foreign keys and cardinalities are represented.\n- [ ] Owned types are handled according to user choice.\n- [ ] Many-to-many join tables are explicit unless the user asked otherwise.\n- [ ] Hidden technical tables are listed in the final summary.\n- [ ] D2 syntax is valid with `d2 fmt`.\n- [ ] Edge endpoints use full dot-notation when inside containers.\n- [ ] The diagram remains readable and avoids crossing-heavy layouts.\n\n## Output Format\n\nWhen the user asks for a skill installation, provide this folder structure:\n\n```text\n.github\u002F\n  skills\u002F\n    efcore-d2-db-diagram\u002F\n      SKILL.md\n      references\u002F\n        efcore-model-extraction.md\n        d2-erd-style.md\n        relationship-rules.md\n        grouping-modes.md\n        quality-gate.md\n```\n\nWhen the user asks to generate a diagram, provide:\n\n1. The `.d2` source file content.\n2. The render command using the selected layout engine.\n3. A concise summary of assumptions and hidden tables.\n","# EF Core D2 Database Diagram Generator\n\n## When to Use\n\nUse this skill when the user wants to generate a database \u002F ERD diagram from an Entity Framework Core codebase.\n\nTypical requests:\n\n- Generate a D2 database diagram from EF Core entities.\n- Visualize tables, columns, primary keys, foreign keys and relationships.\n- Analyze `DbContext`, `DbSet\u003CT>`, `IEntityTypeConfiguration\u003CT>`, Fluent API and migrations.\n- Produce a `.d2` file renderable to SVG\u002FPNG with the `d2` CLI.\n- Document the database model of an ASP.NET Core \u002F .NET project.\n\n## Goal\n\nCreate a readable D2 entity-relationship diagram that reflects the actual EF Core persistence model, not only the raw C# class shape.\n\nThe diagram must prioritize:\n\n1. Database tables and relationships.\n2. Primary keys, foreign keys, required\u002Foptional columns.\n3. Owned types and value objects.\n4. Many-to-many relationships and join tables.\n5. Indexes, unique constraints and table names.\n6. EF Core conventions only when explicit mapping is absent.\n\nOutput is `.d2` source code. It can be rendered to SVG or PNG via the `d2` CLI.\n\n## Tools\n\n- **d2 CLI**: render `.d2` files to SVG\u002FPNG.\n  - `d2 input.d2 output.svg`\n  - `d2 --layout=elk input.d2 output.svg`\n- **d2 fmt**: format D2 files.\n  - `d2 fmt input.d2`\n- No MCP server is required. The skill generates D2 source code as text.\n\n## Recommended Workflow\n\n1. Read the EF Core project structure.\n2. Locate all `DbContext` classes.\n3. Locate all `DbSet\u003CT>` declarations.\n4. Locate entity classes, owned types, enum types and value objects.\n5. Read `OnModelCreating` and all `IEntityTypeConfiguration\u003CT>` classes.\n6. Read migrations when available to confirm table names, join tables, indexes and delete behaviors.\n7. Build a normalized database model before writing D2.\n8. Ask the mandatory diagram questionnaire before generation.\n9. Generate the `.d2` file using the database model, not raw class nesting.\n10. Validate D2 syntax with `d2 fmt` before delivery.\n11. Render with `d2 --layout=elk schema.d2 schema.svg` when possible.\n12. If regenerating, re-read EF Core mappings and migrations first.\n\n## Mandatory Questions Before Diagram Generation\n\nAsk these questions for every new diagram and every regeneration unless the user already answered them in the same request.\n\n1. `Which DbContext should be diagrammed? (auto-detect\u002Fall\u002Fspecific name)`\n2. `Display columns? (all\u002Fkey-only\u002Fnone)`\n3. `Display column types? (Yes\u002FNo)`\n4. `Display nullable\u002Frequired markers? (Yes\u002FNo)`\n5. `Display indexes and unique constraints? (Yes\u002FNo)`\n6. `Display enum values? (Yes\u002FNo)`\n7. `Display owned types? (inline\u002Fseparate\u002Fhide)`\n8. `Display many-to-many join tables? (explicit\u002Fcompact\u002Fhide)`\n9. `Display audit\u002Ftechnical tables? (Yes\u002FNo)`\n10. `Display migration-only tables not present as entities? (Yes\u002FNo)`\n11. `Which grouping mode? (bounded-context\u002Fschema\u002Fnamespace\u002Fflat)`\n12. `Which layout engine? (elk\u002Fdagre\u002Ftala)`\n13. `Which output format? (d2\u002Fsvg\u002Fpng)`\n\nDefault values, when the user asks for a quick generation:\n\n- DbContext: `auto-detect`\n- Columns: `key-only`\n- Column types: `Yes`\n- Nullable markers: `Yes`\n- Indexes: `Yes`\n- Enums: `No`\n- Owned types: `inline`\n- Join tables: `explicit`\n- Audit\u002Ftechnical tables: `No`\n- Migration-only tables: `Yes`\n- Grouping: `bounded-context`\n- Layout: `elk`\n- Output: `d2`\n\n## Reference Documents\n\nLoad these on demand when needed:\n\n| Reference | When to load |\n|---|---|\n| `references\u002Fefcore-model-extraction.md` | Rules for reading DbContext, DbSet, Fluent API, configurations and migrations |\n| `references\u002Fd2-erd-style.md` | D2 syntax and visual conventions for ERD diagrams |\n| `references\u002Frelationship-rules.md` | How to infer one-to-one, one-to-many, many-to-many and owned relationships |\n| `references\u002Fgrouping-modes.md` | Rules for bounded-context, schema, namespace and flat grouping |\n| `references\u002Fquality-gate.md` | Final checklist before delivering the generated diagram |\n\n## EF Core Extraction Rules\n\n### Source Priority\n\nUse this priority order when sources disagree:\n\n1. Latest applied migration \u002F migration snapshot.\n2. Fluent API configuration in `OnModelCreating` or `IEntityTypeConfiguration\u003CT>`.\n3. Data annotations.\n4. EF Core conventions.\n5. Raw C# class shape.\n\n### Required EF Core Concepts to Detect\n\nDetect and represent:\n\n- `DbContext` and `DbSet\u003CT>`.\n- Entity class names and actual table names from `ToTable`.\n- Schema names from `ToTable(\"Table\", \"schema\")`.\n- Primary keys from `HasKey`, `[Key]`, conventions and migrations.\n- Composite keys.\n- Foreign keys from `HasForeignKey`, navigation properties and migration operations.\n- Delete behavior when explicit: `Cascade`, `Restrict`, `NoAction`, `SetNull`, `ClientSetNull`.\n- Required\u002Foptional relationship markers.\n- Owned types from `OwnsOne`, `OwnsMany` and `[Owned]`.\n- Many-to-many relationships from `UsingEntity` and implicit EF Core join tables.\n- Indexes from `HasIndex`, `IsUnique` and migrations.\n- Alternate keys from `HasAlternateKey`.\n- Shadow properties configured in Fluent API.\n- Value conversions when they affect persisted type or readability.\n- Enum properties.\n- Ignored properties and ignored entities.\n\n## Diagram Rendering Rules\n\n### Tables\n\nRepresent each persisted table as a D2 node with `shape: sql_table` when possible.\n\nUse this content convention:\n\n```d2\nClients: {\n  shape: sql_table\n  constraint: primary_key\n  Id: uuid {constraint: primary_key}\n  Name: text\n  Status: enum\n}\n```\n\nIf `sql_table` is unavailable or causes validation issues, fallback to a rectangle with structured text.\n\n### Relationships\n\nUse directional edges from dependent table to principal table.\n\nLabels must include relationship cardinality and FK name when known:\n\n```d2\nOffers.ClientId -> Clients.Id: \"N:1 FK_Offers_Clients_ClientId\"\n```\n\nUse these cardinality labels:\n\n- `1:1`\n- `1:N`\n- `N:1`\n- `N:N`\n- `owned`\n\n### Owned Types\n\nOwned types default to inline rendering.\n\nInline example:\n\n```d2\nClients: {\n  shape: sql_table\n  Id: uuid {constraint: primary_key}\n  Address.Street: text\n  Address.ZipCode: text\n  Address.City: text\n}\n```\n\nIf the user chooses `separate`, represent owned types as visually subordinate tables and use an `owned` relationship.\n\n### Many-to-Many\n\nDefault to explicit join tables because EF Core creates real tables.\n\nFor implicit many-to-many relationships, create a generated join table node and mark it as `implicit join`.\n\n### Technical Tables\n\nHide technical tables by default unless requested.\n\nExamples:\n\n- `__EFMigrationsHistory`\n- Hangfire tables\n- ASP.NET Identity tables\n- Audit logs\n- Outbox tables\n\nIf technical tables are hidden, mention them in the summary after the diagram.\n\n## Grouping Modes\n\n- `bounded-context`: group by detected domain area or folder\u002Fmodule.\n- `schema`: group by database schema, e.g. `public`, `auth`, `billing`.\n- `namespace`: group by C# namespace.\n- `flat`: no containers, all tables at the same level.\n\n## Style Rules\n\nUse consistent styles:\n\n- Primary entity tables: solid border.\n- Join tables: dashed border.\n- Owned types: lighter stroke or nested inline fields.\n- Technical tables: muted style.\n- External tables or migration-only tables: dotted border.\n- Required relationships: solid line.\n- Optional relationships: dashed line.\n- Cascade delete: label suffix `cascade`.\n\n## Quality Gate Before Delivery\n\nBefore delivering the diagram, verify:\n\n- [ ] The selected DbContext is clear.\n- [ ] All `DbSet\u003CT>` entities are considered.\n- [ ] Fluent API configurations are read.\n- [ ] Migrations are checked when present.\n- [ ] Table names and schema names match EF Core mapping.\n- [ ] Primary keys are present.\n- [ ] Foreign keys and cardinalities are represented.\n- [ ] Owned types are handled according to user choice.\n- [ ] Many-to-many join tables are explicit unless the user asked otherwise.\n- [ ] Hidden technical tables are listed in the final summary.\n- [ ] D2 syntax is valid with `d2 fmt`.\n- [ ] Edge endpoints use full dot-notation when inside containers.\n- [ ] The diagram remains readable and avoids crossing-heavy layouts.\n\n## Output Format\n\nWhen the user asks for a skill installation, provide this folder structure:\n\n```text\n.github\u002F\n  skills\u002F\n    efcore-d2-db-diagram\u002F\n      SKILL.md\n      references\u002F\n        efcore-model-extraction.md\n        d2-erd-style.md\n        relationship-rules.md\n        grouping-modes.md\n        quality-gate.md\n```\n\nWhen the user asks to generate a diagram, provide:\n\n1. The `.d2` source file content.\n2. The render command using the selected layout engine.\n3. A concise summary of assumptions and hidden tables.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fefcore-d2-db-diagram",5344,"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-13 02:05:36",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add github\u002Fawesome-copilot --skill efcore-d2-db-diagram",{"tool":69,"command":70},"bunx","bunx skills add github\u002Fawesome-copilot --skill efcore-d2-db-diagram",{"tool":72,"command":73},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill efcore-d2-db-diagram","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fefcore-d2-db-diagram\u002FSKILL.md",true,[77,83,89,93,97,101,105],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"assets\u002Fqa-console.html","ASSET","资产文件",32392,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fqa-html\u002Fassets\u002Fqa-console.html",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"AUTHORING.md","REFERENCE","参考文档",5944,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fqa-html\u002FAUTHORING.md",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fd2-erd-style.md",490,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fefcore-d2-db-diagram\u002Freferences\u002Fd2-erd-style.md",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fefcore-model-extraction.md",927,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fefcore-d2-db-diagram\u002Freferences\u002Fefcore-model-extraction.md",{"path":98,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fgrouping-modes.md",401,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fefcore-d2-db-diagram\u002Freferences\u002Fgrouping-modes.md",{"path":102,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fquality-gate.md",516,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fefcore-d2-db-diagram\u002Freferences\u002Fquality-gate.md",{"path":106,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Frelationship-rules.md",1010,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fefcore-d2-db-diagram\u002Freferences\u002Frelationship-rules.md",[110,143,171,199,229,246],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":122,"publishedAt":48},"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",[116,119],{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":48},"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",[149],{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},[151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"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":175,"sourceHtmlUrl":176,"categories":177,"keywords":183,"publishedAt":48},"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",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":181,"taxonomyTypeDesc":182},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[184,185,186,187,188,189,157,127,45,190,191,192,193,194,195,139,196,197,44,198],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","applications","local","azure","worker","upgrades","package","apps","Legacy","workflows",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":203,"sourceHtmlUrl":204,"categories":205,"keywords":208,"publishedAt":48},"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",[206,207],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":179,"categoryName":180,"taxonomyType":181,"taxonomyTypeDesc":182},[209,210,35,211,212,213,214,215,216,28,217,218,219,220,221,128,222,223,224,225,226,157,227,228],"winmd api search","search","windows","desktop","file access","enumeration","ui","ml","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":233,"licenseFileUrl":234,"sourceHtmlUrl":235,"categories":236,"keywords":242,"publishedAt":48},"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",[237,238,241],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":239,"categoryName":240,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},[243,154,28,244,245],"resemble detect","https","identity",{"skillNo":247,"name":248,"nameZh":6,"description":249,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":233,"licenseFileUrl":250,"sourceHtmlUrl":251,"categories":252,"keywords":257,"publishedAt":48},"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",[253,256],{"categoryNo":254,"categoryName":255,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},[258,259,260,261,185,129,9,153,262,263,244,264,265,266,267,268,269,270,271,272,273,274,137,275,276,277,278],"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"]