Add 5 framework-specific collections with shared agent and prompt for generating production-ready applications from OpenAPI specifications:
- Java Spring Boot
- Python FastAPI
- Node.js NestJS
- C# .NET
- Go
Reuses existing framework instructions for consistency and best practices.
Similar to c12041b which added outdated agent detection, this commit adds:
- Version comparison process for detecting outdated local assets
- Fetch remote versions step in the process workflow
- Updated icons reference with outdated status indicators
- Update handling sections for managing outdated assets
- Updated output table examples to show outdated status
- Replace static github-mcp-registry.json with live API calls
- Fetch from https://api.mcp.github.com/v0.1/servers/ with pagination support
- Extract displayName from GitHub metadata for better matching
- Implement smart matching logic:
* Case-insensitive comparison
* Match against both displayName and full name
* Strip common suffixes like -mcp-server for pattern matching
- Make build process async to support API calls
- Cache registry data to only hit API once per build run
- Remove obsolete github-mcp-registry.json file
Benefits:
- No more manual updates to registry data
- Always uses latest MCP registry information
- Improved server name matching resilience
- Successfully loads all 54 servers from registry
* Add Software Engineering Team collection with 7 specialized agents
Adds a complete Software Engineering Team collection with 7 standalone
agents covering the full development lifecycle, based on learnings from
The AI-Native Engineering Flow experiments.
New Agents (all prefixed with 'se-' for collection identification):
- se-ux-ui-designer: Jobs-to-be-Done analysis, user journey mapping,
and Figma-ready UX research artifacts
- se-technical-writer: Creates technical documentation, blogs, and tutorials
- se-gitops-ci-specialist: CI/CD pipeline debugging and GitOps workflows
- se-product-manager-advisor: GitHub issue creation and product guidance
- se-responsible-ai-code: Bias testing, accessibility, and ethical AI
- se-system-architecture-reviewer: Architecture reviews with Well-Architected
- se-security-reviewer: OWASP Top 10/LLM/ML security and Zero Trust
Key Features:
- Each agent is completely standalone (no cross-dependencies)
- Concise display names for GitHub Copilot dropdown ("SE: [Role]")
- Fills gaps in awesome-copilot (UX design, content creation, CI/CD debugging)
- Enterprise patterns: OWASP, Zero Trust, WCAG, Well-Architected Framework
Collection manifest, auto-generated docs, and all agents follow
awesome-copilot conventions.
Source: https://github.com/niksacdev/engineering-team-agents
Learnings: https://medium.com/data-science-at-microsoft/the-ai-native-engineering-flow-5de5ffd7d877
* Fix Copilot review comments: table formatting and code block syntax
- Fix table formatting in docs/README.collections.md by converting multi-line
Software Engineering Team entry to single line
- Fix code block language in se-gitops-ci-specialist.agent.md from yaml to json
for package.json example (line 41-51)
- Change comment syntax from # to // to match JSON conventions
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Fix model field capitalization to match GitHub Copilot convention
- Change all agents from 'model: gpt-5' to 'model: GPT-5' (uppercase)
- Aligns with existing GPT-5 agents in the repo (blueprint-mode, gpt-5-beast-mode)
- Addresses Copilot reviewer feedback on consistency
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Add ADR and User Guide templates to Technical Writer agent
- Add Architecture Decision Records (ADR) template following Michael Nygard format
- Add User Guide template with task-oriented structure
- Include references to external best practices (ADR.github.io, Write the Docs)
- Update Specialized Focus Areas to reference new templates
- Keep templates concise without bloating agent definition
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Fix inconsistent formatting: DevOps/CI-CD to DevOps/CI/CD
- Change "DevOps/CI-CD" (hyphen) to "DevOps/CI/CD" (slash) for consistency
- Fixed in collection manifest, collection docs, and README
- Aligns with standard industry convention and agent naming
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Shorten collection description per maintainer feedback
- Brief description in table: "7 specialized agents covering the full software
development lifecycle from UX design and architecture to security and DevOps."
- Move detailed context (Medium article, design principles, agent list) to
usage section following edge-ai-tasks pattern
- Addresses @aaronpowell feedback: descriptions should be brief for table display
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
* Migrating chat modes to agents now that's been released to stable
* Fixing collections
* Fixing names of agents
* Formatting
* name too long
* Escaping C# agent name
* Add droid custom partner agent
Add a new Droid CLI assistant agent to the partners collection that provides installation guidance, usage examples, and automation patterns for the Droid CLI, with emphasis on droid exec for CI/CD and non-interactive automation.
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
* Address PR #406 comments on droid agent
- Add model field to frontmatter
- Fix escaped pipe in Quick Reference table (remove unnecessary backslash from markdown table code cell)
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
---------
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: Aaron Powell <me@aaron-powell.com>
* Adding a collection for the meta prompts to help discover items in the awesome copilot repo
* Forgot to run validation locally
* YAML schema validation set and updating readme
* initial prototype of partners collection with featured collection support
* Starting to add the partners
* Preparing the repo for how the custom agents will work
* moving some files around
* Moving a bunch of stuff around to make the file easier to read
* improving the front matter parsing by using a real library
* Some verbage updates
* some more verbage
* Fixing spelling mistake
* tweaking badges
* Updating contributing guide to be correct
* updating casing to match product
* More agents
* Better handling link to mcp registry
* links to install mcp servers fixed up
* Updating collection tags
* writing the mcp registry url out properly
* Adding custom agents for C# and WinForms
Expert custom agents to improve your experience when working with C# and WinForms in Copilot
* Adding to agents readme
* Adding PagerDuty agent
* Fixing description for terraform agent
* Adding custom agents to the README usage
* Removing the button to make the links more obvious
* docs: relocate category READMEs to /docs and update generation + internal links
* Updating prompts for new path
* formatting
---------
Co-authored-by: Chris Patterson <chrispat@github.com>
* Add Java MCP Server Development collection
- Add Java MCP server best practices instruction
- Add Java MCP server project generator prompt
- Add Java MCP expert chat mode
- Add Java MCP development collection manifest
- Update category READMEs
Features:
- Server setup with official MCP Java SDK
- Tool/resource/prompt handlers with reactive streams
- Project Reactor for async processing
- Spring Boot integration with starters
- Stdio and HTTP transport support
- JSON schema construction with fluent builders
- Synchronous facade for blocking use cases
- Maven and Gradle build configurations
* Fix Java MCP generator prompt
- Add missing import statements for handler classes
- Add handler registration in test server setup
---------
Co-authored-by: Aaron Powell <me@aaron-powell.com>
- Add Swift MCP server best practices instruction
- Add Swift MCP server project generator prompt
- Add Swift MCP expert chat mode
- Add Swift MCP development collection manifest
- Update category READMEs
Features:
- Server setup with official Swift SDK package
- Tool/resource/prompt handlers with withMethodHandler
- Async/await and actor-based concurrency patterns
- ServiceLifecycle integration for graceful shutdown
- Stdio, HTTP, and network transport support
- JSON schema construction with Value type
- Swift 6.0+ with modern concurrency features
- Platform support: macOS 13+, iOS 16+, Linux
* Add Go MCP Server Development collection
* Fix: Wrap description in single quotes per prompt guidelines
* Fix: Wrap chatmode description in single quotes per guidelines
* Fix: Wrap instruction description in single quotes per guidelines
- Add instructions for Python MCP server development best practices
- Add prompt for generating complete Python MCP server projects
- Add expert chat mode for Python MCP development assistance
- Add collection grouping all Python MCP resources together
- Update README files with new contributions
Co-authored-by: Aaron Powell <me@aaron-powell.com>
* Add TypeScript MCP Server Development collection
- Add instructions for TypeScript MCP server development best practices
- Add prompt for generating complete TypeScript MCP server projects
- Add expert chat mode for TypeScript MCP development assistance
- Add collection grouping all TypeScript MCP resources together
- Update README files with new contributions
* Revert unintended change to power-bi-development.md
* Add C# MCP Server Development collection
- Add instructions for C# MCP server development best practices
- Add prompt for generating complete MCP server projects
- Add expert chat mode for C# MCP development assistance
- Add collection grouping all C# MCP resources together
- Update README files with new contributions
* Add applyTo field to C# MCP instructions
* Add Power BI resources: 4 chat modes, 6 instructions, 4 prompts, and resources README
* Remove power-bi-resources-README.md - not needed for PR
* Add Power BI Development collection
* Fix PR review feedback: Add collection YAML file and remove double fenced code blocks
- Add power-bi-development.collection.yml with proper metadata
- Remove outer 4-backtick fences from all Power BI files (chatmodes, instructions, prompts)
- Files now have only the standard 3-backtick fences for proper GitHub Copilot compatibility
* Remove outer code fences from Power BI chatmode files
* Add files via upload
* Revise Power Apps Code App project scaffolding
Update project scaffolding instructions for Power Apps Code Apps with PAC CLI setup, SDK integration, and connector configuration.
* Update Power Apps Code App scaffolding prompt
* Revise development instructions for Power Apps Code Apps
Update Power Apps Code Apps development instructions with new standards and best practices for TypeScript, React, and Power Platform integration.
* Update Power Platform expert chatmode with new details
* Revise Power Apps Code App project scaffold
Update project scaffolding details and add advanced patterns.
* Fixing line endings
---------
Co-authored-by: Aaron Powell <me@aaron-powell.com>
* Java 25 upgrade guide with best practices (Java 21 -> 25)
Added a description for the Java upgrade guide.
* Add Java Development Collection and Upgrade Guides
- Created a new collection for Java development, including prompts and instructions for Spring Boot, Quarkus, JPA, JUnit, and Javadoc.
- Added comprehensive markdown documentation for upgrading from Java 17 to Java 21, detailing new language features, API changes, and best practices.
- Introduced upgrade guide for transitioning from Java 21 to Java 25, highlighting new features, migration strategies, and performance considerations.
* Update upgrade guide headers and descriptions for Java 21 to 25
* Refactor Java Development Collection: Update Upgrade Guides with Descriptions
* Add Java 11 to Java 17 Upgrade Guide with best practices and migration patterns
* Rename files
* Add Technical Spike collection and related resources
- Introduced a new collection for Technical Spikes, including a chat mode for research and a prompt for creating spike documents.
- Updated the Project Planning & Management collection to include references to technical spikes.
- Enhanced README files to reflect the addition of technical spike resources.
- Created detailed documentation for the technical spike research methodology and prompt structure.
- Added new tags and items to facilitate better organization and discovery of technical spike-related content.
* CHANGE: Update research methodology for technical spikes
- Refine tool usage philosophy for exhaustive research
- Enhance todo management protocol for better tracking
- Improve spike document update protocol for real-time logging
