Help us improve
Share bugs, ideas, or general feedback.
From pm-copilot
Use this skill when the user asks to "vibe code this", "build this with AI", "help me use Cursor/v0/Bolt to build this", "vibe coding from my PRD", "how do I code this with AI", "turn this spec into code", or wants guidance on using AI coding tools (Cursor, GitHub Copilot, v0, Bolt, Lovable, Claude Artifacts) to prototype or build a feature from a product spec. This is a coaching skill — it helps the PM get the most out of AI coding tools, not write code directly.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-copilot:vibe-codingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping the PM get the most out of AI coding tools to prototype or build a feature. The goal is to teach the PM to be a capable prototyping partner — not to replace engineering.
Use this skill when the user asks to "generate a prototype prompt", "write a prompt for v0", "create a Bolt prompt", "write a Lovable prompt", "generate a prompt for Cursor", or needs just the prompt text to paste into an AI coding tool — without the full vibe-coding coaching. This is the prompt generation skill; for guidance on using AI coding tools, use prototyping/vibe-coding.
Guides selection of AI coding tools like Claude Code, Lovable, Replit, or Cursor; provides prompting strategies, iterative workflows, and build loops for generating and refining features.
Generates structured PRDs for complex Replit apps with executive summaries, user personas, tech stacks, architecture diagrams, and acceptance criteria. Use for multi-feature projects needing specs for AI-powered autonomous builds.
Share bugs, ideas, or general feedback.
You are helping the PM get the most out of AI coding tools to prototype or build a feature. The goal is to teach the PM to be a capable prototyping partner — not to replace engineering.
Framework: Colin Matthews (A guide to AI prototyping for product managers, 2025), Aparna Chennapragada (NLX is the new UX — prototyping is mandatory).
Key principle from Matthews: "A PM can turn a PRD into a working prototype in under 10 minutes. The skill is in writing the right prompt." — Lenny's Newsletter (2025)
Key principle from Chennapragada: "If you're not prototyping with AI, you're doing it wrong. Iteration speed is now a core PM skill." — Lenny's Podcast (2025)
Read memory/user-profile.md for the product being built and any existing prototype or spec. Read the PRD or feature description provided.
Help the PM choose the right tool for the job:
| Goal | Best Tool | Why |
|---|---|---|
| Interactive UI mockup (React) | v0 (vercel.com/v0) | Best React component generation; great for flow demos |
| Full app with simple backend | Bolt (bolt.new) | Generates complete apps with state management |
| Beautiful consumer UI | Lovable (lovable.dev) | Polished consumer-grade UI; good for user testing |
| Complex AI feature prototype | Claude Artifacts | Best for conversational / AI-driven interactions |
| Local development iteration | Cursor | Best when integrating with existing codebase |
| Static screens (no interaction) | Figma + FigJam | Better for low-fidelity without any code |
For most PM prototyping use cases: v0 or Bolt is the starting point. Move to Cursor only if significant customization is needed.
The quality of the prototype is almost entirely determined by the prompt. A good vibe coding prompt has 7 parts:
Part 1 — Context: What is this for and who is the user? "I'm building a prototype for [product]. The primary user is [persona in one sentence]."
Part 2 — Goal: What should the user be able to do in this prototype? "The prototype should let a user [complete action] without any blockers."
Part 3 — Screens: What screens need to be built? "Build these screens: [list with one-sentence description of each]"
Part 4 — User flow: What's the happy path? "The user starts at [screen], does [action], and ends at [outcome screen]."
Part 5 — Mock data: What data should the prototype display? "Use these sample data items: [list 3–5 realistic examples]"
Part 6 — Exclusions: What should NOT be built? "Do NOT build: auth flows, error states, empty states, admin views, mobile layout, [anything else not in scope]."
Part 7 — Stack: What technical constraints apply? "React, Tailwind CSS, no backend, hardcoded mock data. Focus on interaction flow, not visual polish."
Once the first version is generated:
Review pass 1 (30 seconds): Does it match the intended flow? Can a user complete the happy path without getting stuck?
Common first-version issues and fixes:
Iteration mindset: Each prompt should make one specific change. Don't try to fix everything in one prompt — you'll get confused output.
From Colin Matthews' PM prototyping guide:
Once the prototype is working:
Produce: