The Vibe Coder Manifesto

We are uncovering better ways of not writing software by not writing it ourselves and helping others not write it. Through this work we have come to value:

• Vibes over tests
• Prompts over documentation
• Deploying over understanding
• A subscription over an education

That is, while there is value in the items on the right, we have simply never tried them.

Principles

1. 01Our highest priority is to make it stop crashing. By any means.
2. 02Welcome changing requirements at any stage: the AI doesn't care.
3. 03Ship the product as often as possible — preferably before it works.
4. 04Business people and developers must work together. The developer is a chat window.
5. 05Build projects around motivated individuals and their subscriptions.
6. 06The most efficient method of conveying information is a screenshot of code taken with a phone.
7. 07Working prod is the primary measure of progress. Prod being down is also a measure.
8. 08Simplicity — the art of not reading the diff — is essential.
9. 09The best architectures emerge in a new chat after the words “forget everything”.
10. 10At regular intervals, the team reflects on how to become more effective, then opens a new chat.