vibe-coding
Vibe Coding helps users build functional software using AI tools through natural language conversation rather than traditional coding. Use this skill when someone wants to create prototypes, MVPs, or internal tools without deep technical expertise, needs guidance on breaking problems into iterative AI prompts, or should understand when professional engineering is required instead of AI-assisted development.
git clone --depth 1 https://github.com/RefoundAI/lenny-skills /tmp/vibe-coding && cp -r /tmp/vibe-coding/skills/vibe-coding ~/.claude/skills/vibe-codingSKILL.md
# Vibe Coding Help the user build software using AI tools and natural language, using frameworks and insights from 3 product leaders. ## How to Help When the user asks for help with vibe coding: 1. **Understand the goal** - Ask what they're trying to build and who it's for (prototype, internal tool, production app) 2. **Guide the approach** - Help them break down the problem into smaller pieces for iterative AI prompts 3. **Set expectations** - Discuss what vibe coding is good for (prototypes, MVPs) versus when professional engineering is needed 4. **Coach on iteration** - Help them understand how to refine output through follow-up prompts ## Core Principles ### Vibe coding is a new skill Elena Verna: "I vibe code myself so I would put that as even as a skill on my resume now." This is a distinct, transformative skill for non-technical roles - PMs, marketers, designers - to build functional software using natural language. ### Replace Figma with prototypes Kevin Weil: "Instead of showing stuff in Figma, we should be showing prototypes that people are vibe coding over the course of 30 minutes to illustrate proofs of concept." Functional code prototypes can be built in the time it takes to create static mockups. ### Build tools to build tools Alexander Embiricos: "They'll vibe code an animation editor and then they use the animation editor to build the animation." Non-engineers can now build functional software and custom tools without deep technical mastery. ### Go beyond prompt engineering Vibe coding is not just writing prompts - it's iteratively building functional software through conversation with AI. It requires understanding how to break problems down, test outputs, and refine through follow-up. ### Know the limits Vibe-coded software is great for prototypes, internal tools, and MVPs. Production-grade systems with complex requirements still need professional engineering review. ## Questions to Help Users - "What are you trying to build, and who will use it?" - "Is this a throwaway prototype or something that needs to scale?" - "Can you break this down into smaller pieces to build incrementally?" - "What's the simplest version that would let you test your hypothesis?" - "Have you tried describing what's not working and asking the AI to fix it?" - "Do you need this to be production-grade, or is it okay if it's rough?" ## Common Mistakes to Flag - **Trying to build everything at once** - Break complex projects into smaller, iterative builds - **Not testing the output** - Always run and test what the AI generates; don't assume it works - **Expecting production quality** - Vibe-coded apps are great for validation but may need engineering for production - **Unclear specifications** - The clearer your description of what you want, the better the output - **Giving up after one try** - Vibe coding is iterative; refine through follow-up prompts ## Deep Dive For all 3 insights from 3 guests, see `references/guest-insights.md` ## Related Skills - Writing PRDs - Usability Testing - Building with LLMs - Shipping Products
Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.
Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.
Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.
Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.