ai-native-builder-workflow
This workflow enables non-technical individuals to build production-ready applications by orchestrating AI models as a technical co-founder, developer, and QA lead.
Core Principles
- The CTO Persona: Treat the AI as a Technical Owner. Instruct it to challenge your ideas, avoid "people-pleasing" (sycophancy), and own the technical architecture while you own the problem and user experience.
- Exposure Therapy: Gradually move from simple chat interfaces (ChatGPT/Claude Projects) to dedicated builders (Bolt/Lovable) to pro-level IDEs (Cursor/Claude Code).
- Planning over Vibe-ing: Never let the AI start coding until a markdown plan is finalized. Eager coding leads to architectural debt and complex bugs.
The /Command Workflow
Implement these custom prompts as reusable /commands within your AI coding environment (Cursor, Claude Code, or IDE system prompts).
1. Capture: /create-issue
Purpose: Quickly capture bugs or features without breaking development flow.
- Instruction: Tell the AI to stop what it's doing and summarize the thought into a specific format.
- Format: TLDR, Current State, Expected Outcome, and Priority.
- Integration: Use MCP (Model Context Protocol) to automatically create a ticket in Linear or GitHub.
2. Deep Dive: /exploration-phase
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