Deep dive: profiles

This page is generated from data/catalog.json, built by scanning the Amplifier ecosystem repos (including amplifier-app-cli and installed collection repos). Each section below shows the concrete mount-plan frontmatter for a profile: orchestrator, context manager, providers, tools, hooks, and agents.

How to use this page

• Use it to answer “what does profile X actually mount?” (tools, hooks, providers).
• Follow the “Defined in” links to jump to the exact profile file in GitHub.
• If a profile has multiple definitions, treat that as a signal to be explicit about which one you’re using.

How profiles are loaded (conceptual)

• An application discovers available profiles from bundled content, installed collections, and user/project profile dirs.
• The app selects a profile (default or per-command) and compiles it into a mount plan.
• The mount plan drives module resolution and registration (provider/tools/hooks/orchestrator/context).