vibe-scratch-workflow

Accumulate vibe library definitions in a scratch database and finalize, normalize, and apply them.

26|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/mizchi/vibe-lang --skill vibe-scratch-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-scratch-workflow
Source: https://github.com/mizchi/vibe-lang/tree/main
Command: npx skills add https://github.com/mizchi/vibe-lang --skill vibe-scratch-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a practical workflow to build and evolve scratch libraries inside vibe by using a dedicated scratch database and guiding the process through finalize, normalize, and apply to safely export a usable library artifact.

Core Features & Use Cases

  • Scratch workspace setup with a dedicated scratch DB path
  • Accumulate library definitions via vibe shell-stdin --restore
  • Safely finalize, normalize, and apply to export a library artifact
  • Use case: prototype a new vibe library in isolation and iterate quickly

Quick Start

Run the scratch workflow by loading definitions with vibe shell-stdin --restore and then finalize, normalize, and apply to export your library.

Frequently Asked Questions about vibe-scratch-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prototype a vibe library in isolation without affecting my main workspace?

You prototype a vibe library in isolation by using a dedicated scratch database path to accumulate definitions safely. This allows iterative sketching and testing across multiple sessions before exporting any artifacts to your main workspace.

What is the scratch workflow for vibe libraries?

The scratch workflow for vibe libraries is a process of accumulating definitions in a scratch database and safely evolving them through finalize, normalize, and apply steps. This controlled Scratch namespace enables rapid iterative development before exporting.

How do I export a library artifact from a vibe scratch database?

You export a library artifact from a vibe scratch database by running the finalize, normalize, and apply commands in sequence after loading your definitions. This safely evolves your sketches into a usable library artifact.

Can I use vibe shell-stdin --restore to manage scratch library definitions?

Yes, you can use vibe shell-stdin --restore to load and accumulate library definitions into your scratch database. This workflow supports multiple sessions of definition sketching and testing within the controlled Scratch namespace.

Do I need a specific database path for vibe scratch workflow?

Yes, the vibe scratch workflow relies on the VIBE_SCRATCH_DB_PATH convention to maintain a dedicated scratch database. This setup is required to safely isolate your prototype library definitions during iterative development.