| name | ai-native-product-building |
| description | Rapidly build, prototype, and deploy full-stack software using AI "text-to-app" tools. Use this when you need to create a greenfield application, build a high-fidelity working prototype for user testing, or bypass traditional engineering bottlenecks for internal tools. |
AI-native product building shifts the Product Manager’s role from writing requirements for others to directly directing an AI agent to build the software. This approach reduces development time from months to weeks and costs by up to 99%.
The "JIRA-Prompt" Framework
Treat every interaction with an AI agent (like Bolt) as if you are writing a high-quality ticket for a senior developer.
1. Define the Technical Scope
Instead of general descriptions, provide the specific parameters the AI needs to spin up the environment:
- Identify the Core Functionality: "Make a Spotify clone with streaming, playlists, and MP3 file support."
- Specify the Stack: State the desired integrations (e.g., "Use Supabase for the database and Netlify for hosting").
- Provide Data Context: Paste raw data (e.g., LinkedIn bio, CSV rows, or brand guidelines) directly into the prompt to give the AI context.
2. Balance Specification with "Vibes"
AI agents perform best when given a mix of rigid requirements and creative freedom.
- High Specificity: Use this for business logic, data schemas, and user flows.
- The "Vibe" Prompt: For UI/UX, use descriptive language rather than specific CSS.
- Example: "Make it look like a high-end medical donation site—clean, professional, and trustworthy."
- Example: "Make it prettier and more modern."
3. Implement Iterative Debugging
When the AI gets stuck or produces an error:
- Screenshot Debugging: Upload a screenshot of the UI issue or the error message and ask: "Fix this to match the intended design."
