[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADXBDZTQRMTKEC6Z6ZMEJQ":3,"skill-same:01M6ADXBDZTQRMTKEC6Z6ZMEJQ":63},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6ADXBDZTQRMTKEC6Z6ZMEJQ","openapi-to-application-code",null,"Generate a complete, production-ready application from an OpenAPI specification","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41156,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fopenapi-to-application-code\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33],"code","openapi to application code","openapi","application","generate","Production","ready","specification","complete","production-ready","2026-11-10 10:12:30",false,"---\nname: openapi-to-application-code\ndescription: 'Generate a complete, production-ready application from an OpenAPI specification'\n---\n\n# Generate Application from OpenAPI Spec\n\nYour goal is to generate a complete, working application from an OpenAPI specification using the active framework's conventions and best practices.\n\n## Input Requirements\n\n1. **OpenAPI Specification**: Provide either:\n   - A URL to the OpenAPI spec (e.g., `https:\u002F\u002Fapi.example.com\u002Fopenapi.json`)\n   - A local file path to the OpenAPI spec\n   - The full OpenAPI specification content pasted directly\n\n2. **Project Details** (if not in spec):\n   - Project name and description\n   - Target framework and version\n   - Package\u002Fnamespace naming conventions\n   - Authentication method (if not specified in OpenAPI)\n\n## Generation Process\n\n### Step 1: Analyze the OpenAPI Specification\n- Validate the OpenAPI spec for completeness and correctness\n- Identify all endpoints, HTTP methods, request\u002Fresponse schemas\n- Extract authentication requirements and security schemes\n- Note data model relationships and constraints\n- Flag any ambiguities or incomplete definitions\n\n### Step 2: Design Application Architecture\n- Plan directory structure appropriate for the framework\n- Identify controller\u002Fhandler grouping by resource or domain\n- Design service layer organization for business logic\n- Plan data models and entity relationships\n- Design configuration and initialization strategy\n\n### Step 3: Generate Application Code\n- Create project structure with build\u002Fpackage configuration files\n- Generate models\u002FDTOs from OpenAPI schemas\n- Generate controllers\u002Fhandlers with route mappings\n- Generate service layer with business logic\n- Generate repository\u002Fdata access layer if applicable\n- Add error handling, validation, and logging\n- Generate configuration and startup code\n\n### Step 4: Add Supporting Files\n- Generate appropriate unit tests for services and controllers\n- Create README with setup and running instructions\n- Add .gitignore and environment configuration templates\n- Generate API documentation files\n- Create example requests\u002Fintegration tests\n\n## Output Structure\n\nThe generated application will include:\n\n```\nproject-name\u002F\n├── README.md                      # Setup and usage instructions\n├── [build-config]                 # Framework-specific build files (pom.xml, build.gradle, package.json, etc.)\n├── src\u002F\n│   ├── main\u002F\n│   │   ├── [language]\u002F\n│   │   │   ├── controllers\u002F       # HTTP endpoint handlers\n│   │   │   ├── services\u002F          # Business logic\n│   │   │   ├── models\u002F            # Data models and DTOs\n│   │   │   ├── repositories\u002F      # Data access (if applicable)\n│   │   │   └── config\u002F            # Application configuration\n│   │   └── resources\u002F             # Configuration files\n│   └── test\u002F\n│       ├── [language]\u002F\n│       │   ├── controllers\u002F       # Controller tests\n│       │   └── services\u002F          # Service tests\n│       └── resources\u002F             # Test configuration\n├── .gitignore\n├── .env.example                   # Environment variables template\n└── docker-compose.yml             # Optional: Docker setup (if applicable)\n```\n\n## Best Practices Applied\n\n- **Framework Conventions**: Follows framework-specific naming, structure, and patterns\n- **Separation of Concerns**: Clear layers with controllers, services, and repositories\n- **Error Handling**: Comprehensive error handling with meaningful responses\n- **Validation**: Input validation and schema validation throughout\n- **Logging**: Structured logging for debugging and monitoring\n- **Testing**: Unit tests for services and controllers\n- **Documentation**: Inline code documentation and setup instructions\n- **Security**: Implements authentication\u002Fauthorization from OpenAPI spec\n- **Scalability**: Design patterns support growth and maintenance\n\n## Next Steps\n\nAfter generation:\n\n1. Review the generated code structure and make customizations as needed\n2. Install dependencies according to framework requirements\n3. Configure environment variables and database connections\n4. Run tests to verify generated code\n5. Start the development server\n6. Test endpoints using the provided examples\n\n## Questions to Ask if Needed\n\n- Should the application include database\u002FORM setup, or just in-memory\u002Fmock data?\n- Do you want Docker configuration for containerization?\n- Should authentication be JWT, OAuth2, API keys, or basic auth?\n- Do you need integration tests or just unit tests?\n- Any specific database technology preferences?\n- Should the API include pagination, filtering, and sorting examples?\n","# Generate Application from OpenAPI Spec\n\nYour goal is to generate a complete, working application from an OpenAPI specification using the active framework's conventions and best practices.\n\n## Input Requirements\n\n1. **OpenAPI Specification**: Provide either:\n   - A URL to the OpenAPI spec (e.g., `https:\u002F\u002Fapi.example.com\u002Fopenapi.json`)\n   - A local file path to the OpenAPI spec\n   - The full OpenAPI specification content pasted directly\n\n2. **Project Details** (if not in spec):\n   - Project name and description\n   - Target framework and version\n   - Package\u002Fnamespace naming conventions\n   - Authentication method (if not specified in OpenAPI)\n\n## Generation Process\n\n### Step 1: Analyze the OpenAPI Specification\n- Validate the OpenAPI spec for completeness and correctness\n- Identify all endpoints, HTTP methods, request\u002Fresponse schemas\n- Extract authentication requirements and security schemes\n- Note data model relationships and constraints\n- Flag any ambiguities or incomplete definitions\n\n### Step 2: Design Application Architecture\n- Plan directory structure appropriate for the framework\n- Identify controller\u002Fhandler grouping by resource or domain\n- Design service layer organization for business logic\n- Plan data models and entity relationships\n- Design configuration and initialization strategy\n\n### Step 3: Generate Application Code\n- Create project structure with build\u002Fpackage configuration files\n- Generate models\u002FDTOs from OpenAPI schemas\n- Generate controllers\u002Fhandlers with route mappings\n- Generate service layer with business logic\n- Generate repository\u002Fdata access layer if applicable\n- Add error handling, validation, and logging\n- Generate configuration and startup code\n\n### Step 4: Add Supporting Files\n- Generate appropriate unit tests for services and controllers\n- Create README with setup and running instructions\n- Add .gitignore and environment configuration templates\n- Generate API documentation files\n- Create example requests\u002Fintegration tests\n\n## Output Structure\n\nThe generated application will include:\n\n```\nproject-name\u002F\n├── README.md                      # Setup and usage instructions\n├── [build-config]                 # Framework-specific build files (pom.xml, build.gradle, package.json, etc.)\n├── src\u002F\n│   ├── main\u002F\n│   │   ├── [language]\u002F\n│   │   │   ├── controllers\u002F       # HTTP endpoint handlers\n│   │   │   ├── services\u002F          # Business logic\n│   │   │   ├── models\u002F            # Data models and DTOs\n│   │   │   ├── repositories\u002F      # Data access (if applicable)\n│   │   │   └── config\u002F            # Application configuration\n│   │   └── resources\u002F             # Configuration files\n│   └── test\u002F\n│       ├── [language]\u002F\n│       │   ├── controllers\u002F       # Controller tests\n│       │   └── services\u002F          # Service tests\n│       └── resources\u002F             # Test configuration\n├── .gitignore\n├── .env.example                   # Environment variables template\n└── docker-compose.yml             # Optional: Docker setup (if applicable)\n```\n\n## Best Practices Applied\n\n- **Framework Conventions**: Follows framework-specific naming, structure, and patterns\n- **Separation of Concerns**: Clear layers with controllers, services, and repositories\n- **Error Handling**: Comprehensive error handling with meaningful responses\n- **Validation**: Input validation and schema validation throughout\n- **Logging**: Structured logging for debugging and monitoring\n- **Testing**: Unit tests for services and controllers\n- **Documentation**: Inline code documentation and setup instructions\n- **Security**: Implements authentication\u002Fauthorization from OpenAPI spec\n- **Scalability**: Design patterns support growth and maintenance\n\n## Next Steps\n\nAfter generation:\n\n1. Review the generated code structure and make customizations as needed\n2. Install dependencies according to framework requirements\n3. Configure environment variables and database connections\n4. Run tests to verify generated code\n5. Start the development server\n6. Test endpoints using the provided examples\n\n## Questions to Ask if Needed\n\n- Should the application include database\u002FORM setup, or just in-memory\u002Fmock data?\n- Do you want Docker configuration for containerization?\n- Should authentication be JWT, OAuth2, API keys, or basic auth?\n- Do you need integration tests or just unit tests?\n- Any specific database technology preferences?\n- Should the API include pagination, filtering, and sorting examples?\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fopenapi-to-application-code",5360,"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-14 05:37:52",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add github\u002Fawesome-copilot --skill openapi-to-application-code",{"tool":55,"command":56},"bunx","bunx skills add github\u002Fawesome-copilot --skill openapi-to-application-code",{"tool":58,"command":59},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill openapi-to-application-code","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fopenapi-to-application-code\u002FSKILL.md",true,[],[64,99,127,152,186,203],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":78,"publishedAt":34},"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",[70,75],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":76,"categoryName":77,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000023","Skill与智能体开发",[79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":106,"publishedAt":34},"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",[105],{"categoryNo":76,"categoryName":77,"taxonomyType":73,"taxonomyTypeDesc":74},[107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":34},"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",[134],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[136,24,137,138,139,140,113,83,141,142,143,144,145,146,147,95,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":34},"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":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,84,179,180,181,182,183,113,184,185],"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":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":190,"licenseFileUrl":191,"sourceHtmlUrl":192,"categories":193,"keywords":199,"publishedAt":34},"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",[194,195,198],{"categoryNo":160,"categoryName":161,"taxonomyType":73,"taxonomyTypeDesc":74},{"categoryNo":196,"categoryName":197,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":76,"categoryName":77,"taxonomyType":73,"taxonomyTypeDesc":74},[200,110,173,201,202],"resemble detect","https","identity",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":190,"licenseFileUrl":207,"sourceHtmlUrl":208,"categories":209,"keywords":214,"publishedAt":34},"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",[210,213],{"categoryNo":211,"categoryName":212,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":76,"categoryName":77,"taxonomyType":73,"taxonomyTypeDesc":74},[215,216,217,218,24,85,9,109,219,220,201,221,222,223,224,225,226,227,228,229,230,231,93,232,233,234,235],"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"]