Collections

⚠️ Deprecation Notice

Collections are deprecated and being replaced by bundles.

Bundles provide a simpler, more composable way to package and share Amplifier configurations. They use markdown with YAML frontmatter instead of Python packages.

Migration guide: MIGRATION_COLLECTIONS_TO_BUNDLES.md

Learn about bundles: Bundles page

What Collections Were

A collection is an installable pack of profiles, agents, and domain context. Collections are optional: they extend what's available, but you don't need them to use the core CLI.

Note: This documentation is maintained for users migrating from collections to bundles.

What a collection is (and is not)

Is: a way to ship “expert setups” (profiles/agents/context) for a domain.
Is not: the same thing as a runtime module (which is code that executes).

Why collections exist

Keep the default installation small while allowing powerful add-ons.
Share repeatable workflows without forcing everyone to install everything.
Let teams standardize profiles/agents for specific work (design, ops, testing, etc.).

Existing collections (scanned)

This list is rendered from data/catalog.json. Use the deep dive page to see what profiles each collection provides.

Deep Dive (All)

How you use collections

amplifier collection add git+https://github.com/microsoft/amplifier-collection-toolkit@main
amplifier collection list
amplifier profile use toolkit-dev

Verified mechanism reference: Collections discovery (verified).

Security warning

Collections may reference modules (tools/hooks/providers) that execute code in your environment. Only install from sources you trust.