Made on
Tilda
Vibecoding is a community of people who build products together with AI.
We help you start: from an idea to a working prototype.
The first international conference on vibecoding in Russia. Organised by the Centre for Transfer and Management of Socio-Economic Information at HSE University together with the Vibecoding non-profit. 24 September 2026, HSE University (Moscow) and online.
Go to the conference siteUntil the start
An autonomous non-profit organisation based in Russia. We help people with no development background start building products together with AI.
We break down tools and approaches so that a first working prototype can be assembled in one evening — with no programming course first.
The vibecoders' club: meetups, project reviews, code review and prompt exchange. There is no entrance exam.
We connect vibecoders and the state: we show what already works in practice and help take it into account in decisions.
The stack directory: we collect tools and sort them onto shelves — the software stack first of all. Vibecoding is wider than code, so the list keeps growing.
We are not utopians: a tool on its own does not make a product successful.
But the choice you make now decides who will be creating products tomorrow. Eight principles on how we work with AI and with responsibility for the result.
A tool on its own does not make a product successful — but it changes who is able to create that product.
The tool does not make the product. Responsibility for the result stays with the human — the model does not take it away.
You can start with no experience. A first working prototype matters more than a first programming textbook.
A prompt is a technical specification. The more precise the context, the fewer fixes later.
Code has to be read — even code a model wrote. Unread code becomes someone else's within a week.
Check before production. Code review, tests and common sense are not cancelled by speed.
The data is not yours. It is always worth knowing where the context goes and what stays with the model provider.
The community is open. We share prompts, scenarios and mistakes — mistakes especially.
Dialogue with institutions. We explain how this works instead of waiting for decisions made blind.
The manifesto is a working document. If you disagree with a wording, write to us: we discuss it in the club.
We categorise what appears on the market — the software stack first of all. Vibecoding is wider than code, so the list keeps growing: send us what is missing.
The part that writes the code. The choice depends on language, data privacy and token price.
Where the project lives. The agent works with the whole folder, not with a single file.
The shortest path to a first prototype: text goes in, a link comes out.
For when the product is not a website but services and models wired to each other.
The notes on the cards are about access from Russia, payment method and a free tier. Terms change: check on the vendor's site before paying.
An agent in the terminal and the editor: reads the whole project and edits code from a task description.
Sber's Russian model — for when the data has to stay inside the country.
Yandex models, available through the API and the cloud.
An editor with an AI agent: edits across the whole project, not one file at a time.
An editor with an agent mode and a preview of the changes.
Completion and an agent inside a familiar environment and in pull requests.
An environment in the browser: code, database and deployment in one window.
A web app from a description — with a database and authentication.
Interfaces from text: generates ready-made components.
A prototype in the browser from a single prompt, deployment included.
Turns a design and a description into a working prototype.
Scenarios between services and models without code.
A place where people ask «how do I do this» and get an answer from someone who already has. No entrance exam: you need interest, not a CV.
A member brings a task, together we assemble a prototype and look at where the prompt worked and where the code had to be read.
We show what to look at in generated code before publishing: data, access, dependencies.
A shared set of prompts and automation scenarios that club members keep adding to.
From application to a first build it usually takes one meeting.
Send us a couple of lines about yourself and what you want to build. A technical background is not required.
We send an invitation to the next meetup and a short set of materials so you arrive prepared.
You pick a tool from the stack and assemble a working prototype together with a mentor from the club.
Universities, institutes and companies we make the conference and the community programmes with.
If you would like to become a partner or a sponsor, write to us.
State and educational resources we use ourselves and rely on in our work.
Write to us if you want to join the club, become a partner, invite us to an event or suggest a tool for the stack directory.
Vibecoding, an autonomous non-profit organisation
t.me/ANOVIBECODING vibecoding.hse.ru ANOvibecoding@yandex.ru
Vibecoding is wider than code: we categorise the tools and teach people to use them.