mirror of
https://github.com/github/awesome-copilot.git
synced 2026-02-20 18:35:14 +00:00
7a003fc75a
Replace Collections with Plugins as first-class citizens in the repo. With the Copilot CLI v0.409 release making plugins an on-by-default marketplace, collections are redundant overhead. ## What changed ### Plugin Infrastructure - Created eng/validate-plugins.mjs (replaces validate-collections.mjs) - Created eng/create-plugin.mjs (replaces create-collection.mjs) - Enhanced all 42 plugin.json files with tags, featured, display, and items metadata from their corresponding collection.yml files ### Build & Website - Updated eng/update-readme.mjs to generate plugin docs - Updated eng/generate-website-data.mjs to emit plugins.json with full items array for modal rendering - Renamed website collections page to plugins (/plugins/) - Fixed plugin modal to use <div> instead of <pre> for proper styling - Updated README.md featured section from Collections to Plugins ### Documentation & CI - Updated CONTRIBUTING.md, AGENTS.md, copilot-instructions.md, PR template - Updated CI workflows to validate plugins instead of collections - Replaced docs/README.collections.md with docs/README.plugins.md ### Cleanup - Removed eng/validate-collections.mjs, eng/create-collection.mjs, eng/collection-to-plugin.mjs - Removed entire collections/ directory (41 .collection.yml + .md files) - Removed parseCollectionYaml from yaml-parser.mjs - Removed COLLECTIONS_DIR from constants.mjs Closes #711
42 lines
1.8 KiB
JSON
42 lines
1.8 KiB
JSON
{
|
|
"name": "swift-mcp-development",
|
|
"description": "Comprehensive collection for building Model Context Protocol servers in Swift using the official MCP Swift SDK with modern concurrency features.",
|
|
"version": "1.0.0",
|
|
"author": {
|
|
"name": "Awesome Copilot Community"
|
|
},
|
|
"repository": "https://github.com/github/awesome-copilot",
|
|
"license": "MIT",
|
|
"tags": [
|
|
"swift",
|
|
"mcp",
|
|
"model-context-protocol",
|
|
"server-development",
|
|
"sdk",
|
|
"ios",
|
|
"macos",
|
|
"concurrency",
|
|
"actor",
|
|
"async-await"
|
|
],
|
|
"display": {
|
|
"ordering": "manual",
|
|
"show_badge": true
|
|
},
|
|
"items": [
|
|
{
|
|
"path": "instructions/swift-mcp-server.instructions.md",
|
|
"kind": "instruction"
|
|
},
|
|
{
|
|
"path": "prompts/swift-mcp-server-generator.prompt.md",
|
|
"kind": "prompt"
|
|
},
|
|
{
|
|
"path": "agents/swift-mcp-expert.agent.md",
|
|
"kind": "agent",
|
|
"usage": "recommended\n\nThis chat mode provides expert guidance for building MCP servers in Swift.\n\nThis chat mode is ideal for:\n- Creating new MCP server projects with Swift\n- Implementing async/await patterns and actor-based concurrency\n- Setting up stdio, HTTP, or network transports\n- Debugging Swift concurrency and ServiceLifecycle integration\n- Learning Swift MCP best practices with the official SDK\n- Optimizing server performance for iOS/macOS platforms\n\nTo get the best results, consider:\n- Using the instruction file to set context for Swift MCP development\n- Using the prompt to generate initial project structure\n- Switching to the expert chat mode for detailed implementation help\n- Specifying whether you need stdio, HTTP, or network transport\n- Providing details about what tools or functionality you need\n- Mentioning if you need resources, prompts, or special capabilities"
|
|
}
|
|
]
|
|
}
|