VibeWare Manifesto

A 400 MB mouse driver? Really?

Taking the stigma out of vibe coding.

VibeWare pixel-art floppy
VibeWare

Initiative started on

Why I built VibeWare

I started building my own tools because I couldn't accept how much software some small jobs seemed to need. Why should the software for a mouse ask for a 400 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 multimedia console. Its software was close to a gigabyte, so I built UlanziDeck, my own native controller in Rust. AI helped me write it, but I chose what to build, guided the work and kept responsibility for the result.

Then comes the question: “But did you use AI?” That is why I started VibeWare and wrote this manifesto: I want to answer that question once. Yes, I use AI, and I will keep using it with technical judgment and responsibility. Read the manifesto for what that means.

I created VibeWare to take the stigma out of vibe coding. A developer can use AI while applying their experience and the same engineering discipline they bring to any software: review the code, consider security, test it meaningfully and understand it well enough to maintain it. AI is a powerful tool; using it well still requires understanding what you are building.

Security starts before an app ships. I review third-party dependencies and their origins, including npm and NuGet packages, to reduce supply-chain risk. I also pay attention to memory, CPU and bottlenecks: small tools should respect the computer they run on. Each project documents its own checks, protections and limitations.

Bloated software was around long before AI. I saw it in the 1980s. Yes, I'm that old. Vibe coding did not invent bloatware or poor engineering. Careless use of a powerful tool can produce problems; thoughtful use deserves to be judged by the work and its evidence.

I don't want to repeat the same explanation fifty times. “This is VibeWare” is my way of pointing people to these principles. Each project should still say what the AI contributed, what I decided, what was checked and what remains unverified.

MANIFESTO

Human intent, AI execution, and plenty of tokens

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.

Created by Umberto Giacobbi. I started the VibeWare initiative on .

Open source / VibeWare

Explore the code. Take the kit.

Two repositories, one hands-on approach. Explore the apps in VibeKit, or use the VibeWare manifesto and templates in your own project.

Just need a file? Start here.

Manifesto

Read it, keep a copy, or share it.

Code & project templates

Source headers, README credits and a record of how AI contributed. Adapt them to your project.

Other uses of the VibeWare term (TXT)