vibe coding editorial team and community
We write vibe coding guides and news, exchange prompts, share projects and meet in person. We talk on Discord, Slack and WhatsApp, and send one email on Thursdays.
Cloud QA agent built by three Polish ex-Callstack engineers. CLI, REST API, GitHub App: five integration patterns for Claude Code and Cursor.
Have an anti-pattern of your own? Add it to #ogólny.
in focus
Four articles about maintaining quality when an agent writes most of the code.
sections
Each section is a separate blog hub. We suggest two articles to start with in each one.
Enter one prompt and compare up to 4 models side by side on 40 coding tasks, including blind comparisons. The interface is in English.
A directory of 39 tools: from Cursor and Claude Code to Aider, Zed, Kiro and Warp.
Polish companies building AI. Filter by category and submit yours.
A calendar of conferences and meetups: Gdańsk, Warsaw and online.
getting started
Just starting out? Read these articles in order. Take the last step with us, in the channel.
A definition of vibecoding, the tool stack, and five anti-patterns that wreck projects.
How a non-technical person can build a working app by talking to AI, without the hype.
What a prompt is, the anatomy of a good one, common mistakes and a simple routine to improve.
Before your first prompt: repo, context, tests and a plan. Twelve steps.
Share a link and a few words about how you built your project. If something is not working, ask in #pomoc.
prompts
Tested prompts for Cursor, Claude Code, Bolt and Lovable. Copy with one click and share yours in #prompty.
Analyze /src and identify 3 modules to extract. For each: name, boundary, file list, migration risks. Plan in 200 words.
Migrate /pages to /app step by step. Make each step a separate commit. Stop after each one and ask for a review.
Pair-program with me using TDD. Ask about requirements before writing anything. Test first. Simplest implementation. Refactor.
from you
A community is more than an audience. Here are the simplest ways to get involved.
#pochwal-się
Built something with AI? Share a link, a screenshot and a few words about how you made it. The #pochwal-się channel is on Discord, Slack and WhatsApp.
#prompty
A prompt that works for you can help others. Post it in #prompty or check the library to see what is missing.
AI company directory
We collect Polish companies building AI, from voice and robotics to developer tools. Know one that is missing?
editorial team
A story idea, a correction, collaboration or a media partnership. We reply within 2 business days.
Come to a meetup. The next one is AI Salon Gdańsk #2: Dec 1, Tuesday, 17:30, STARTER Gdańsk, ul. Lęborska 3b. Register on Luma. Other conferences and meetups, including Vibecoding Meetup Warszawa, are in the event calendar.
Hackathons. Our format: 4 times a year, 48 hours online with prizes. Want to join? Follow #ogłoszenia.
from the editors
We write about vibe coding and practical AI in Polish. News, guides and reviews.
Editor-in-chief
Builds AI products from the first prompt to production. Runs vibecoding.pl.
definition and FAQ
Vibe coding is a way of building software where the programmer describes the goal in natural language and an AI agent writes the code — for example Claude Code, Cursor or Lovable. Andrej Karpathy coined the term in February 2025. The human still designs, reviews changes and owns the quality of what ships to production.
Want to try? Read the guides or take the vibe coding course. Vibe coding changes every week. Follow AI news and our roundup of AI news.
Vibe coding is a way of building software where the programmer describes the goal in natural language and an AI agent writes the code — for example Claude Code, Cursor or Lovable. Andrej Karpathy coined the term in February 2025. The human still designs, reviews changes and owns the quality of what ships to production.
Andrej Karpathy — OpenAI co-founder and former head of AI at Tesla — coined the term in a post on X in February 2025. It caught on so fast that Collins Dictionary named "vibe coding" its Word of the Year 2025.
Yes — the form of the work changes, not its essence. The programmer still owns architecture, code review, tests and the decision about what ships to production; the agent takes over the typing. Without that verification a project quickly turns into code nobody understands, which is why engineering experience still matters.
Install one tool — Claude Code or Cursor is the best start — pick a small project of your own and hand the agent its first concrete task. Our vibe coding course walks you through the 8 levels of working with agents, and the tool reviews and prompts help you pick a stack along the way.