Module 3, Lesson 2: Writing the Spec with Claude Desktop
How do you write a spec with Claude Desktop? You point Claude at the docs you built in Module 2, then have it turn them into structured feature specs, written into your project as files. The result is a /specs folder your codebase gets built from, not a note or
Module 3, Lesson 1: Setting Up WebStorm + Claude
How do you set up WebStorm and connect it to Claude? You install WebStorm, create your project, then enable MCP and wire it to Claude Desktop. Now Claude can control your editor and write straight into the codebase. It turns your Module 2 docs into a real build environment. What
Module 2, Lesson 7: User Flow in Figma
How do you build a user flow diagram in Figma with Claude? You hand Claude your four product docs, then connect Figma over MCP so Claude draws the whole flow in FigJam for you. You never touch Figma yourself. You just need an account and a browser. This is also
Prompt Library
All Prompt organized
Module 2, Lesson 6: Generating the GTM Document
How do you generate a go-to-market document with Claude? You feed Claude the research and specs you already built, and it produces a concrete sales and marketing playbook: who you sell to, the channels that reach them, the message, and the launch order. It is the bridge from
Module 2, Lesson 5: Generating the Investor Summary
What is an investor summary and how do you write one with Claude? An investor summary, also called a stakeholder summary, is a non-technical, high-level document that answers one question above all: will this make money? You write it by prompting Claude to lead with consequences rather than
Module 2, Lesson 4: Generating the UX/UI Document
What is a UX/UI document and how do you create one with Claude? A UX/UI document defines how your product looks and how users move through it: design philosophy, UI references, colour palette, typography, component recommendations, key user flows, screen inventory, and empty states. You create it by
Module 2, Lesson 3: Generating the Technical Document
What is a technical document and how do you generate one with Claude? A technical document is the blueprint that answers what exactly you are building and how: the app name, the recommended stack, the architecture, cost projections, and environment setup. You generate it by feeding your validated research into
Module 2, Lesson 2: Reviewing Your Market Research
How do you review AI generated market research? You treat the AI output as a first draft, not the final answer, then pressure test it against reality. That means visiting competitor websites yourself, reading real app store reviews where actual customer pain lives, studying the biggest player in the space,
Module 2, Lesson 1: Market Research
How do you do market research with Claude? You use Claude Desktop's Deep Research feature, driven by structured prompts, to size the market, map competitors, and surface real demand before committing to a build. A useful trick is to have Claude ask you clarifying questions first, which makes