A visual marketplace for discovering, installing, and managing GitHub Copilot prompt libraries from multiple sources.
AI Primitives Hub transforms how you discover and manage GitHub Copilot prompts. Browse a visual marketplace, search by tags, and install curated prompt libraries with a single click—no manual file copying or repository cloning required.
ℹ️ Note: This project was formerly known as Prompt Registry. It has been renamed to AI Primitives Hub to better reflect its broader scope. The extension ID (
AmadeusITGroup.prompt-registry) and package name remain unchanged for compatibility — seeingprompt-registryin install commands and file names is expected.
- Quick Start
- Key Features
- Core Concepts
- Ask Copilot About AI Primitives Hub
- Documentation
- Installation
- Supported Sources
- Architecture Overview
- Repository Structure
- Troubleshooting
- Contributing
- License
- Install — Search "AI Primitives Hub" in VS Code Extensions (
Ctrl+Shift+X) - Select Hub — On first launch, choose a hub from the welcome dialog (or skip to configure later)
- Browse — Click "MARKETPLACE" in the AI Primitives Hub sidebar
- Install — Click any bundle tile, then click Install
- Use — Open Copilot Chat and type
/to see your installed prompts, or run the "AI Primitives Hub: Sync All Bundles" command to verify everything synced 🎉
The extension automatically adds the Awesome Copilot source and syncs your selected hub's profiles on startup.
- 🎨 Visual Marketplace — Browse bundles in a tile-based interface with search, filters, and one-click install (details)
- 🔌 Multi-Source Support — Connect to GitHub, local directories, APM repositories, or Awesome Copilot collections (details)
- 📦 Version Management — Track versions, detect updates, and enable automatic background updates (details)
- 👥 Profiles & Hubs — Organize bundles by project/team and share configurations across your organization (details)
- 🤖 Built-in Copilot Skill — Ask GitHub Copilot questions about AI Primitives Hub directly in chat — setup, authoring, troubleshooting, and more
- 🌍 Cross-Platform — Works on macOS, Linux, and Windows with all VS Code flavors
New to the project? These six terms appear everywhere:
| Term | Meaning |
|---|---|
| Primitive | A single AI asset: a prompt, instruction, agent, chat mode, skill, or MCP server configuration |
| Bundle | An installable package of primitives, described by a deployment-manifest.yml |
| Collection | A repository that offers one or more bundles |
| Source | Anywhere bundles come from — a GitHub repo, a local directory, an APM repository, or Awesome Copilot |
| Hub | A shared configuration that defines profiles for a team or organization |
| Profile | A named set of bundles within a hub (e.g. "frontend team") |
Every bundle ships a manifest that declares its contents. A minimal example:
# deployment-manifest.yml
name: my-team-prompts
version: 1.0.0
description: Shared prompts for the frontend team
primitives:
- type: prompt
path: prompts/write-unit-tests.prompt.md
- type: instruction
path: instructions/typescript-style.instructions.mdManifests are validated against the JSON schemas in schemas/ at install time.
→ Author Guide: Creating a Collection
AI Primitives Hub ships with a built-in Copilot skill that lets you ask GitHub Copilot questions about the extension directly in chat. No extra setup is required — the skill is available as soon as the extension is installed.
What you can ask:
- Users — "How do I add a local source?", "What scopes are available?", "Why isn't my hub showing?"
- Authors — "How do I create a collection?", "What fields are required in a manifest?", "How do I publish to a hub?"
The skill answers from the extension's own documentation, so responses are always grounded in the actual behavior of your installed version.
Note: The skill covers user and author topics only. For contributor questions (architecture, testing, internals), consult the Contributor Guide directly.
Seeing incorrect or unexpected answers? Please open an issue describing the question you asked and the response you received, or reach out to one of the project contributors directly.
| Audience | Description | Link |
|---|---|---|
| Users | Installation, marketplace, sources, profiles, troubleshooting | User Guide |
| Authors | Creating, validating, and publishing prompt collections | Author Guide |
| Contributors | Development setup, architecture, testing, coding standards | Contributor Guide |
| Reference | Commands, settings, adapter API, hub schema | Reference Docs |
From VS Code Marketplace:
- Open VS Code → Press
Ctrl+Shift+X - Search "AI Primitives Hub" → Click Install
From VSIX:
Download the latest .vsix from the Releases page, then install it (replace <version> with the version you downloaded):
code --install-extension prompt-registry-<version>.vsixFrom Source:
git clone https://github.com/AmadeusITGroup/ai-primitives-hub.git
cd ai-primitives-hub
npm install
npm run package:vsix
# Install the VSIX produced by the previous step (the filename includes the current version)
code --install-extension prompt-registry-<version>.vsixFor custom VS Code instances (with custom user-data-dir/extensions-dir):
# After building the VSIX above, install to your custom VS Code instance
code --user-data-dir "$ud" --extensions-dir "$ed" --install-extension prompt-registry-<version>.vsix| Source Type | Description |
|---|---|
| Awesome Copilot | Curated community collections |
| GitHub | Direct from GitHub repositories |
| Local | File system directories |
| APM | APM package repositories |
The extension is layered: UI → Commands → Services → Adapters → Storage, with the RegistryManager orchestrating everything. All source types are accessed through a common adapter interface, so the rest of the codebase never contains source-specific logic.
flowchart TD
UI[Marketplace webview and tree views] --> CMD[Commands]
CMD --> RM[RegistryManager<br/>central orchestrator]
RM --> AD[Adapters<br/>GitHub / Local / APM / Awesome Copilot]
AD --> BI[BundleInstaller<br/>validate, extract, record]
BI --> MCP[MCP server integration]
BI --> SYNC[User scope sync<br/>copies primitives into Copilot folders]
RM --> ST[(Persistent registry state)]
Install flow: the adapter fetches the bundle → its deployment-manifest.yml is validated against the JSON schemas → contents are extracted to managed storage → primitives are synced into the folders GitHub Copilot reads → the update service tracks the bundle for new versions.
→ Full Architecture Documentation
| Path | What lives there |
|---|---|
src/ |
The VS Code extension: activation, commands, services, adapters, webview UI |
lib/ |
Core library and CLI — install bundles from the terminal without VS Code |
schemas/ |
JSON schemas for collection and bundle manifests |
github-actions/ |
Reusable GitHub Action for validating collections in CI |
docs/ |
User, author, and contributor documentation |
website/ |
Documentation website |
templates/ |
Scaffolding templates for new collections |
test/ |
Unit and integration tests |
Bundles not showing in Copilot?
- Check sync completed in extension logs
- Run "AI Primitives Hub: Sync All Bundles"
- Reload VS Code (Command Palette → "Developer: Reload Window")
- Verify the synced files exist on disk:
| OS | Synced prompts location |
|---|---|
| Linux | ~/.config/Code/User/prompts |
| macOS | ~/Library/Application Support/Code/User/prompts |
| Windows | %APPDATA%\Code\User\prompts |
Installation fails?
- Verify network connection and repository access
- Check bundle has valid
deployment-manifest.yml(validated againstschemas/)
We welcome contributions! See CONTRIBUTING.md for guidelines.
→ Development Setup | Coding Standards
Apache 2.0 — See SECURITY.md for security policy.
- Microsoft - For GitHub Copilot and VS Code
- Awesome Copilot Community - For curated prompt collections
- Contributors - Everyone who has contributed to this project