Save this plugin to Following and return to review observed changes. Follow up to 10 plugins free.
Description
From the marketplace listing
Vibe Coding Library searches 241 public engineering workflows and loads the selected recipe with its domain skill, working contract and required references. Search and catalog metadata support English, Spanish, Russian and Simplified Chinese; technical instructions are in English. Workflows cover repository mapping, planning, code review, API contracts, data, infrastructure, AI and release checks. One bundled skill guides workflow selection. The read-only MCP tools require no account or API key. Your agent applies retrieved guidance using its project tools and permissions.
Language: English · Automatically detected from descriptions.
Exact text from the indicated source. A mention alone does not establish support for your task.
Plugin name
Vibe Coding Library
Package name
vibe-coding-library
Publisher full description
Vibe Coding Library searches 241 public engineering workflows and loads the selected recipe with its domain skill, working contract and required references. Search and catalog metadata support English, Spanish, Russian and Simplified Chinese; technical instructions are in English. Workflows cover repository mapping, planning, code review, API contracts, data, infrastructure, AI and release checks. One bundled skill guides workflow selection. The read-only MCP tools require no account or API key. Your agent applies retrieved guidance using its project tools and permissions.
---
name: vibe-library
description: "Find and load a Vibe Coding engineering workflow when the user invokes the library, asks which workflow fits a task, or requests a named recipe. Use the public MCP catalog; do not activate for every coding task."
---
# Vibe Coding Library
1. Identify the requested result and domain. Audit and review mean inspection; implement means authorized changes; check means verification. Preserve an explicit named workflow or ID.
2. Use `search_workflows` with concise technical keywords. Set `mode` only when the requested operation is clear; use a returned `skill` identifier to narrow an ambiguous domain. Choose the user's catalog language. Search instruction bodies only when catalog search is insufficient. Do not send source code, credentials or personal data.
3. Select the closest workflow by its title, domain and operation. Ask only when competing workflows require a decision that changes the result. Call `get_workflow` for that stable ID; select `host` only when the current environment is known.
4. Apply the returned working contract, domain skill and selected recipe using the user's project tools and permissions. Read the supplied instruction files once. `files[].path` identifies a library resource; use its returned text rather than resolving it from the user's repository. Source links identify versioned originals. Invocation examples for the full offline plugin apply only when those skills are installed. Follow `AGENTS.md` in Codex and the active `CLAUDE.md` and loaded rules in Claude.
5. For a linked alternative recipe, search and load that recipe only if the task needs it. Report actual changes, checks and limitations in the user's language. These tools supply guidance; repository evidence comes from the environment where the agent works.
For empty search results, revise the domain keywords or filter. For an unknown ID, search before retrying. If the server is unavailable, use an installed offline Vibe Coding skill when available and state the retrieval limitation; do not invent retrieved instructions or a successful check.
Referenced files: 1 — file references are metadata, not package contents.
Release notes
Vibe Coding Library 1.5.1 fixes UTF-8 handling in the cross-platform package builder and snapshot generator, preserving localized metadata on Windows. The public MCP search and selected workflow retrieval use the unchanged audited instruction library 1.4.1. Both read-only tools, stable IDs, schemas and workflow content remain compatible with 1.5.0.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.