vibe-codingBuild software with AI by describing what you want. Covers prompting techniques, workflow patterns, rules files, and when to intervene.
Install via ClawdBot CLI:
clawdbot install ivangdavila/vibe-codingProgramming where you describe what you want and let AI generate code. You evaluate by results, not by reading every line. Coined by Andrej Karpathy (Feb 2025).
Key distinction (Simon Willison): If you review, test, and can explain the code ā that's software development, not vibe coding. Vibe coding means accepting AI output without fully understanding every function.
| Topic | File |
|-------|------|
| Prompting techniques | prompting.md |
| Research-Plan-Implement workflow | workflow.md |
| Rules files (.cursorrules, CLAUDE.md) | rules-files.md |
| Common pitfalls and fixes | pitfalls.md |
| Tool selection by use case | tools.md |
Vague prompts ā vague results. Before touching your AI tool:
Bad: "Build a social media app"
Good: "Build a social feed: text posts (280 chars), follow users, chronological feed, likes/comments. Use React, Tailwind, Supabase."
Persistent context that teaches AI your conventions. Put it in once, applies to every interaction:
See rules-files.md for templates.
Before implementing, have AI explore and plan:
Catching misunderstanding during planning = 10x cheaper than debugging cascading errors.
AI generates code that looks flawless but has subtle bugs. After every change:
The Karpathy move: copy error message, paste with no comment, usually it fixes it. If AI can't fix after 2-3 attempts, describe the behavior you want instead.
Set explicit boundaries:
Good for: Prototypes, MVPs, internal tools, weekend projects, UI components, boilerplate, learning
Bad for: Security-critical code, performance-critical code, compliance-heavy domains, long-term production systems
The best vibe coders understand architecture, spot bad AI output, and know when to intervene. If you can't evaluate whether AI produced good code, you need to learn more before vibe coding production systems.
Generated Mar 1, 2026
A startup team uses vibe coding to quickly build a minimum viable product for a new social networking app, focusing on generating UI components and basic CRUD operations with React and Supabase. This allows them to validate the idea with users in days rather than weeks, while adhering to constraints like a 280-character post limit and chronological feed.
A marketing agency employs vibe coding to create custom dashboards and automation scripts for client reporting, using AI to generate boilerplate code and integrate with APIs like Google Analytics. This speeds up development for non-critical internal tools, enabling the team to focus on creative work rather than coding details.
A coding bootcamp leverages vibe coding to help students build weekend projects and learning exercises, such as simple web apps or UI components, by describing intents and letting AI handle repetitive code. This enhances hands-on learning without getting bogged down in syntax, while instructors review security-critical parts like user authentication.
A design firm uses vibe coding to rapidly prototype and generate reusable UI components in Tailwind CSS for client websites, following style constraints from rules files. This streamlines the design-to-development workflow, allowing designers to iterate quickly and ensure consistency across projects without deep coding expertise.
Offer a free tier for basic vibe coding features like prompting techniques and rule files, with premium subscriptions for advanced workflows, team collaboration, and integration with popular IDEs. Revenue comes from monthly or annual subscriptions, targeting individual developers and small teams who need rapid prototyping tools.
Provide consulting services to help businesses adopt vibe coding for internal tool development and MVP creation, along with training workshops on best practices like the Research-Plan-Implement workflow. Revenue is generated through hourly rates or project-based fees, focusing on industries like tech startups and marketing agencies.
Create a marketplace where developers can buy and sell pre-made rules files, prompting templates, and workflow patterns tailored to specific stacks like React or Supabase. Revenue comes from transaction fees or subscriptions for access to premium content, catering to experienced developers looking to streamline their vibe coding process.
š¬ Integration Tip
Integrate vibe coding by setting up rules files like .cursorrules in your project root to maintain consistent coding conventions, and use the Research-Plan-Implement workflow to catch errors early before implementation.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Provides a 7-step debugging protocol plus language-specific commands to systematically identify, verify, and fix software bugs across multiple environments.
A comprehensive skill for using the Cursor CLI agent for various software engineering tasks (updated for 2026 features, includes tmux automation guide).
Write, run, and manage unit, integration, and E2E tests across TypeScript, Python, and Swift using recommended frameworks.
Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.