* 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>
This commit is contained in:
Aaron Powell
2025-10-29 06:07:13 +11:00
committed by GitHub
parent f4533e683c
commit 56d7ce73a0
55 changed files with 5683 additions and 1110 deletions

View File

@@ -51,8 +51,8 @@ node create-collection.js my-collection-id
1. Create `collections/my-collection-id.collection.yml`
2. Use the template above as starting point
3. Add your items and customize settings
4. Run `node validate-collections.js` to validate
5. Run `node update-readme.js` to generate documentation
4. Run `npm run validate:collections` to validate
5. Run `npm start` to generate documentation
## Validation
@@ -64,7 +64,7 @@ Collections are automatically validated to ensure:
Run validation manually:
```bash
node validate-collections.js
npm run validate:collections
```
## File Organization
@@ -78,4 +78,4 @@ Collections don't require reorganizing existing files. Items can be located anyw
3. **Good Descriptions**: Explain who should use the collection and what benefit it provides
4. **Relevant Tags**: Add discovery tags that help users find related collections
5. **Reasonable Size**: Keep collections focused - typically 3-10 items work well
6. **Test Items**: Ensure all referenced files exist and are functional before adding to a collection
6. **Test Items**: Ensure all referenced files exist and are functional before adding to a collection