VibeWare Manifesto

Human intent. AI implementation. Accountable human review.

Taking the stigma out of vibe coding.

Since 5 October 2026

Why I built VibeWare

I started VibeWare because I couldn't accept how much software some small jobs seemed to need. Why should the software for a mouse ask for an 800 MB download and half a gigabyte of RAM when I could make the controls I actually use in seven or eight megabytes? I wanted tools that did their job without taking over my computer.

I felt the same way about my Ulanzi D200H console. Its software was close to a gigabyte, so I built my own controller in Rust; the executable is under ten megabytes. How is that possible? AI helped me write it, but I chose what to build, guided the work and kept responsibility for the result. That is why I started VibeWare, and why I wrote this manifesto.

I want VibeWare to remove the stigma around "vibe coding": with care and testing, it can mean quality. I want to give back by sharing what AI and I built with anyone who doesn't want two or three gigabytes of RAM tied up by a mouse driver or a small button console.

MANIFESTO

Human intent comes first.

VibeWare begins with a person who knows what they want to build and why. The human defines the purpose, chooses the constraints, makes the design decisions and accepts responsibility for the result. AI executes much of the implementation, and that contribution is declared openly.

AI makes software creation accessible to more people, but access does not remove the need for understanding. Good direction requires curiosity, technical judgment and the ability to recognize when an answer is incomplete, unsafe or simply wrong.

AI execution deserves real engineering.

AI-produced code can be quality code. It still needs the same discipline as any other software: thoughtful architecture, careful review, meaningful tests, security checks, useful documentation and ongoing maintenance.

The limits of generated code are real. Models can introduce errors, unnecessary complexity, insecure patterns and confident explanations that do not match the implementation. Keeping a capable person in the loop is how those risks are found, challenged and corrected.

VibeWare is not a shortcut around engineering. It is a way to apply engineering judgment to a new method of execution.

Quality is shown through evidence.

A label does not prove quality. Behavior, measurements and reproducible checks do. Projects should state what was tested, under which conditions, what passed and what remains unverified.

Focused software matters too. AI is no excuse for bloat or carelessness. We value tools that solve a clear problem, use resources deliberately and remain understandable enough to maintain.

Make the process visible.

Where practical, develop in public so others can inspect, question and improve the work. Record the AI tools that actually contributed, preserve useful history and publish relevant validation evidence while protecting private information.

Say what the AI did. Say what the human decided. Say what was checked. Say what still needs work.

Build useful things.

VibeWare carries forward the hands-on spirit of early personal computing: curiosity, experimentation and the pleasure of making something useful. Its pixel-art floppy is a reminder that new tools are most valuable when people understand, shape and take responsibility for what they create with them.

This is an open invitation to developers, tinkerers and people discovering new ways to build: use AI boldly, examine its work carefully and let the result speak for itself.

Files / 01