Overview
Reference for developers taking Vibe Coding for Production
Welcome. Treat this site as a working reference for Vibe Coding for Production: use the sidebar, copy snippets, and open linked references when they help your task.
Shell commands (macOS, Linux, Windows)
Where it matters, pages show macOS / Linux examples (usually bash or zsh) and Windows examples (PowerShell). When a command is the same everywhere (claude, npm, npx), you may see a single block labeled All platforms. For .sh scripts, Windows users typically run them in Git Bash, WSL, or bash from Git for Windows if bash is on your PATH.
Example first prompt in a new repo
I just opened this repository. If AGENTS.md or CLAUDE.md exists, read them; otherwise infer from the tree. Tell me how to install dependencies, run the app locally, and run the main test or build command, then stop until I pick a task.Tools required
You’ll need three coding agents installed and signed in before the workshop. Each one teaches a different surface (terminal, cloud, and IDE), and we’ll move between all three.
- 00
Claude Code
Anthropic
Terminal-native coding agent. CLAUDE.md project instructions, granular permission rules, and lifecycle hooks.
install - 01
OpenAI Codex
OpenAI
CLI, IDE, desktop, and cloud agent. AGENTS.md, sandboxed execution, browser verification, and parallel work.
install - 02
Cursor
Anysphere
Desktop IDE with first-class AI. Parallel agents, multi-file diffs, and design-mode tooling for any stack you open in the workspace.
install
Start with OpenAI Codex for its CLI, desktop, cloud, computer-use, and sandbox workflows; use Getting Started with Cursor for the IDE and worktree model. The rest of the curriculum is Claude-first but cross-links equivalent Codex and Cursor features where the product behavior differs.
During the session
- Work through each section in order, or jump to any topic from the sidebar when you need it.
- Paste commands and configuration from here instead of typing from the screen.
- The Taskflow landing demo uses Next.js and Tailwind as written. The capstone build at the end of First steps lets you pick one of several paths (dashboards, calendar, queue, richer marketing) on any local web stack you can run, as long as you tell the agent which framework and styling to keep.
- Come back here after the workshop to revisit commands, patterns, and links.
Workshop demos
Each exercise lives in its own repository following the pattern
https://github.com/Elfocrash/vibi<number>. Replace <number> with the
workshop number given during the session.
# Replace <number> with the workshop number given during the session
git clone https://github.com/Elfocrash/vibi<number>.git
cd vibi<number>Each repo is self-contained and has its own README with the install and run commands. Open the repo in your editor (or point your agent at it) so the agent's context stays focused on the exercise.