Every new microservice at a growing org reimplements the same 80%: the ownership model, service metadata, setup guidance, and a starting repository. If those conventions are not captured somewhere, every team does them slightly differently — and months later you are dealing with a patchwork of approaches.
VibeControls Templates lets you capture a component snapshot with a category, version, descriptive file tree, variables, setup instructions, and an optional source repository. Publish that template to the workspace catalog so teams can start from the same metadata and conventions.
Now a new team picks it from the gallery, fills in the requested parameters, and instantiates a component from the frozen snapshot. When a source repository is configured, the flow can create or fork a GitHub repository and add the template's rendered README and setup guidance.
The catalog retains the template relationship for instantiated components. Automated generation of Dockerfiles, CI, VibeDeck buttons, security configuration, and cross-version drift reporting are planned enhancements, not part of the current template flow.
Do it yourself
Package a component snapshot as a reusable template, publish it to the catalog, and let teams instantiate consistent components with requested parameters and setup guidance.
Open Templates, choose Publish, and pick an existing component as the source. Give it a name, category, and version.
You should see: VibeControls freezes a snapshot of your component and creates a draft template tied to that exact version.
Ready to make this your story?
