building-with-ai-engineers
Building with AI Engineers
In the era of AI-driven development, the primary bottleneck is no longer writing code, but the human's ability to act as a high-fidelity translator. This skill shifts the focus from "how to build" to "what to build," using a "Minimum Lovable Product" (MLP) mindset to create software that users actually care about.
The AI Collaboration Workflow
1. The Initial Prompt (Defining the MLP)
Instead of a Minimum Viable Product, aim for a Minimum Lovable Product. Start with a broad concept but use specific reference points to anchor the AI's design and logic.
- Identify the Anchor: Use a known entity as a baseline (e.g., "An Airbnb clone" or "A Tinder for cats").
- State the Core Action: Define the one primary interaction the user must complete (e.g., "User should be able to purchase a home listing directly").
2. High-Fidelity Refinement
Once the UI is generated, do not rely solely on text prompts for small changes.
- Visual Editing: If the tool allows, edit text and colors visually. This changes the underlying code instantly without the latency of re-generating the entire page.
- Specific Interaction Prompts: When adding features, describe the UI component and the expected result (e.g., "Add a button that triggers a pop-up modal for payment").
3. Using "Chat Mode" to Unstuck
If the AI introduces a bug or a logical loop, transition from "Command Mode" to "Chat Mode."
- Inquire, Don't Command: Ask, "How does this specific function work?" or "Why am I not getting the result I want here?"
More from samarv/shanon
agentic-workflow-automation
Transition from static LLM chats to autonomous agents that execute multi-step tasks. Use this when you need to automate cross-platform reports (e.g., Snowflake to Google Docs), build self-service tools for non-technical teams, or create "anticipatory" engineering workflows that draft PRs based on Slack discussions.
63b2b-value-negotiation
A framework for defending price and extracting maximum value in B2B sales. Use this skill when a prospect asks for a discount, when transitioning a POC to a commercial deal, or when presenting high-ticket pricing to budget-conscious stakeholders.
18niche-market-opportunity-mapping
A framework for identifying high-margin, low-competition business ideas ("fishing holes") by leveraging personal unfair advantages and avoiding overcrowded markets. Use this when vetting a new startup idea, choosing a niche for a service business, or seeking to pivot an existing product into a more profitable segment.
17b2b-saas-workflow-strategy
A framework to evaluate the market potential and strategic direction of B2B products based on workflow frequency and organizational breadth. Use it when validating a new startup idea, evaluating a product's "ceiling," or planning a pivot to increase market share.
14agentic-engineering-workflow
Transition from a hands-on "bricklayer" to a high-level "architect" by managing a fleet of autonomous AI agents. Use this when you need to scale engineering output with a small team, handle repetitive migrations/bug fixes, or onboard engineers to complex legacy codebases.
10b2b-category-creation-strategy
A framework for determining when to create a new software category versus winning an existing one, and the tactical steps to define and validate that category. Use this when your product is too disruptive for current labels, when existing categories have negative associations, or when you need to expand your TAM.
9