Vibe-Coder
name: vibe-coder
by calecorbett · published 2026-03-22
$ claw add gh:calecorbett/calecorbett-vibe-coder---
name: vibe-coder
description: "Expert vibe-coding workflow for building apps, tools, and scripts from scratch based on plain-English descriptions. Use when a user asks to build something — an app, tool, CLI, script, web app, automation, or any software project — described in natural language. Handles the full build lifecycle: understanding the brief, planning phases, building incrementally, error recovery, iteration, and final delivery. Never silently gets stuck."
---
# Vibe-Coder
Build anything from a plain-English description. Six phases. No silent failures.
Phase 1 — Understand the Brief
Before writing a single line of code:
**Questions to consider:**
Phase 2 — Plan the Build
Break into exactly 5 phases:
1. **Structure** — project scaffold, file layout, dependencies
2. **Functionality** — core logic, data flow, business rules
3. **UI Polish** — interface, UX, error states, edge cases
4. **Testing** — happy path, edge cases, error scenarios
5. **Final Review** — cleanup, docs, delivery packaging
Present the plan with bullet points under each phase. Get explicit approval before starting Phase 3.
Phase 3 — Build Phase by Phase
For each phase:
1. **Announce what you're about to build** before writing code
2. Write clean, commented code
3. Explain each major section in plain English (1-2 sentences max per section)
4. After each phase, ask: "Does this look right? Anything to change before I move on?"
5. Incorporate feedback before proceeding
Never skip a phase. Never start the next phase without confirmation.
Phase 4 — Error Handling
If you hit a bug or blocker:
Phase 5 — Iterate
After each phase, active feedback loop:
Phase 6 — Final Delivery
Deliver:
1. **Working product** — all files, runnable as described
2. **Build summary** — what was built, key decisions made, anything deferred
3. **Usage instructions** — how to run it, configure it, and extend it
Format the summary as:
## What Was Built
[2-3 sentences]
## Key Decisions
- [decision + rationale]
## How to Run
[commands]
## Known Limitations / Next Steps
- [if any]General Rules
More tools from the same signal band
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...