Start with intent
Write a trigger-first skill, focused agent, or reusable prompt that solves a real workflow.
Inventory
A live snapshot from library.yaml
Counts, statuses, tags, and bundle membership are generated from the repo catalog. Materialized entries have checked-in content; plugin-managed entries remain references installed by their plugin system.
Ready-made operators
Featured capabilities for real work
These entries highlight the repeatable workflows the Vault already carries: review, validation, research, packaging, document work, and domain-specific delivery.
Find the right tool
Search across skills, agents, and prompts
Filter by asset type, lifecycle status, capability, or domain. URL parameters preserve the current view so searches can be shared with another builder or agent.
No catalog entries match this view
Clear filters or broaden the search terms to inspect more of the Vault.
Installable sets
Bundles turn the catalog into workflows
Each bundle groups reusable skills with the rules, templates, and placeholders a downstream repo needs to start from a coherent operating pattern.
For external builders
Help build the vault without breaking the catalog
Catalog it
Add the entry to library.yaml with type, status, origin, and capability or domain tags.
Materialize it
Keep checked-in content under skills, agents, or prompts unless it is explicitly plugin-managed.
Validate drift
Run the repo checks so counts, missing files, orphaned files, and hardcoded paths stay honest.
Local first
Build it locally, then move it to Azure when ready
Local preview
make showcase-serve
Regenerates the catalog snapshot and serves the site on port 4173 by default.
Static Web Apps
npm run build
Use app location apps/vault-showcase and publish dist/client after the build.
Container
dist/client
Serve the generated client folder from nginx, Caddy, Express, or any static server.