buildgreatproducts
- 39 skills
- 0 followers
- 33 repo stars
- 2 months ago last updated
- ▌ Studio Setup · buildgreatproductsUse as the first thing after receiving ProductOS — it installs the system into the app repo and adopts the custom programme plan when one shipped with the copy. Triggers on phrases like "set up ProductOS", "install ProductOS", "studio setup", "wire my repo", "adopt my plan", "get ProductOS working in this repo", or any request to install or initialise ProductOS in a codebase. Verifies productos/ sits inside a git repo (and walks a standalone checkout through creating the app repo and moving in), wires the coding-agent guidelines from productos/setup/ into the repo root (copy whole, or append the marked block — never overwriting), adds productos/ to .gitignore, and — if the copy shipped with a plan at productos/PLAN.md — moves it to docs/PLAN.md and runs a light verification pass against the actual repo. Ends by naming the member's literal first action. Run once at install; safe to re-run any time.
- ▌ Cc Build Loop · buildgreatproductsUse when building features with **Claude Code** in any codebase and the work should go through a disciplined build → review → test → fix loop. Triggers on "run the build loop", "build the next task", "continue the plan", "build this feature properly", or any request to implement work from a plan file or a direct feature prompt. Builds from the plan (or the prompt if no plan exists), runs Claude Code's `/review` (plus `/security-review` for sensitive surfaces) and fixes every issue found, tests and verifies the feature end to end, fixes anything testing surfaces, and reports back once complete. Repeats until all plan tasks are checked off.
- ▌ Studio Launch · buildgreatproductsUse at each phase's launch moment — the recurring ritual that puts the product in front of real potential customers and logs the signal. Four launches, one ladder: the Mini-Launch (Define — win: one reply), "here's what it looks like" (Design — win: one signup or "can I try it?"), the beta invite (Develop — win: one activated user), the public launch (Distribute — win: first payment). Triggers on phrases like "mini-launch", "mini launch", "relaunch", "launch post", "beta invite", "get my first signal", "put my offer in front of people", "write my launch post", "draft my DM", "ship the ask", "invite my believers", "message the people who replied", or any request to draft, ship, and log an outreach moment based on the ProductOS documents. Reads docs/LAUNCHES.md (and docs/PLAN.md's launches-remaining, when present) to know which launch this is, drafts 2–3 message variants in the persona's language, ships within 48 hours, then logs every response and grows the believers list. Closes each phase.
- ▌ Codex Build Loop · buildgreatproductsUse when building features with **Codex** (OpenAI Codex CLI) in any codebase and the work should go through a disciplined build → review → test → fix loop. Triggers on "run the build loop", "build the next task", "continue the plan", "build this feature properly", or any request to implement work from a plan file or a direct feature prompt. Builds from the plan (or the prompt if no plan exists), runs Codex's `/review` on uncommitted changes and fixes every issue found, tests and verifies the feature end to end, fixes anything testing surfaces, and reports back once complete. Repeats until all plan tasks are checked off.
- ▌ Cursor Build Loop · buildgreatproductsUse when building features with **Cursor** in any codebase and the work should go through a disciplined build → review → test → fix loop. Triggers on "run the build loop", "build the next task", "continue the plan", "build this feature properly", or any request to implement work from a plan file or a direct feature prompt. Builds from the plan (or the prompt if no plan exists), runs Cursor's `/review` and fixes every issue found, tests and verifies the feature end to end, fixes anything testing surfaces, and reports back once complete. Repeats until all plan tasks are checked off.
- ▌ Studio Define Pricing · buildgreatproductsUse when the user has filled out their Product Offer (and ideally their Customer Persona) and needs one honest launch price fast — enough to make a real ask this week, with no heavyweight strategy work. Triggers on phrases like "what should I charge", "pick my launch price", "pricing strategy", "put a price on it", "how much is this worth", "what's my price line", "price for my mini-launch", or any request to fill in a four-section Pricing Strategy (Who Pays, Launch Price, Price Anchors, Your Price Line). Reads the Product Offer and Customer Persona, researches 2–3 real anchor prices, and produces a filled-in Pricing Strategy document in a 20–30 minute session. Deliberately the week-one slice of pricing — the full ladder, cost & margin, and revenue model live in the optional Business Strategy Deep Dive (studio-define-business-strategy). Especially appropriate in a ProductOS Define workflow, immediately before the Mini-Launch.
- ▌ Studio Define Product · buildgreatproductsUse when the user has filled in the Define-phase documents (Product Offer, Customer Persona, Pricing Strategy, Mini-Launch) and wants a single concise summary of the entire product strategy. Triggers on phrases like "create PRODUCT.md", "synthesise my define docs", "summarise my product", "roll up the define folder", "build my PRODUCT doc", "condense my strategy", "one-page product summary", "create a readable summary of my product", or any request to merge the Define documents into a single readable summary. Reads all the source documents, translates framework jargon into plain English, and produces an 8-section PRODUCT.md (Summary, Customer, Problem, Mechanism, Why, Business model, Proof, Goal) in the docs folder — readable in 4–6 minutes by a co-founder, designer, advisor, or new hire without context. Especially appropriate as the final step in a ProductOS-style Define workflow.
- ▌ Studio Develop Golive · buildgreatproductsUse when the user's product is built (or nearly built) and they want to get it live and accessible to customers. Triggers on phrases like "create my deploy checklist", "how do I deploy this", "help me launch", "get this live", "put this in production", "ship it to customers", "what do I need to do to go live", or any request for a step-by-step path from working code to a product customers can use. Audits the current codebase — stack, services, environment variables, payments, deploy config — then writes a plain-English, step-by-step deployment guide to `docs/DEPLOY.md`. Every step is marked as something the user must do themselves, something their coding agent can do, or both together, and all technical terms are explained for non-technical founders.
- ▌ Studio Develop Migrate · buildgreatproductsUse inside (or alongside) an app built on a prompt-to-app platform — Lovable, Bolt, v0, Base44, Replit Agent, and similar — when the user wants to move it into their own repository and a developer agent tool like Claude Code, Codex, or Cursor. Triggers on phrases like "migrate from Lovable", "get my app out of Lovable", "move my project to Claude Code", "leave Bolt/v0/Base44", "own my codebase", "migration plan", or any request to take a platform-built app to a self-owned repo, stack, and deployment. Inventories everything the platform manages (hosting, database, auth, secrets, storage, functions, webhooks, domains), recommends the target stack, researches the platform's current export mechanics live, and writes `docs/MIGRATION.md` — a phased, checkbox-tracked plan the coding agent executes, ending with a verification gate before the old platform is decommissioned. Migration moves and rewires; it does not improve code — run `studio-develop-refactor-plan` afterwards for that.
- ▌ Studio Define From Code · buildgreatproductsUse when the user already has a product — a codebase, live app, landing page, or app store listing — and needs the Define-phase documents extracted from it fast, instead of built from blank templates. Triggers on phrases like "extract my offer from my code", "fast-track define", "I already built it, backfill the strategy docs", "reverse-engineer my product offer", "define from my existing product", "my product exists but I have no PRODUCT.md", or any request to derive the Product Offer, Customer Persona, and Pricing Strategy from an existing product. Reads the evidence (repo, live site, listing, existing docs), infers draft answers for all six offer elements plus persona and observed pricing, pre-fills the three Define templates in place marked as extracted drafts, confirms the load-bearing inferences with the user, then hands off to studio-define-offer-review for sharpening and studio-define-product for synthesis. The Define fast-track for members who aren't starting from scratch.
- ▌ Studio Design UX Writing · buildgreatproductsUse when the user has their Product Identity's Tone of Voice and wants the in-product copy system — buttons, labels, errors, empty states, confirmations, toasts, notifications, and a terminology lexicon. Triggers on phrases like "write my UX copy", "UX writing", "microcopy", "fix my button labels", "write my error messages", "empty states", "in-app copy", "copy audit", "make my copy clearer", or any request to make interface writing clear, concise, and concrete. Reads the Identity's tone of voice and `productos/design/BONUS-UX-Writing-Best-Practice.md`, walks the user through the voice chart, terminology lexicon, and per-surface copy rules in the voice of a senior UX writer, and writes `docs/COPY.md` — the copy system coding agents follow the way they follow `docs/DESIGN.md`. In a repo with real UI strings it also audits and rewrites them. Works standalone without ProductOS. For marketing copy use `studio-design-landing-page` or `studio-design-app-listing` instead.
- ▌ Studio Develop Cro Audit · buildgreatproductsUse when the user has a working product codebase (web/mobile app, SaaS, marketplace, dev tool, extension, or landing page) and wants a conversion rate optimization audit of the code — what's slowing conversion, what's missing, what to fix first. Triggers on phrases like "audit my conversion rate", "CRO audit", "review my code for conversion", "what's hurting my signup rate", "find my conversion bottlenecks", "why aren't users converting", or "are my forms killing conversion". Runs in the app repo — the repository that contains `productos/`. Detects product type, scans for conversion-relevant patterns (forms, CTAs, Core Web Vitals, analytics, mobile, paywall placement, trust signals), and writes a prioritized audit to `docs/CRO-AUDIT.md` (or repo root if no `docs/`). Optionally references ProductOS files (`docs/PRODUCT.md`, `productos/design/1-Product-Identity.md`, `productos/design/2-Magic-Moment.md`) if present; works standalone.
- ▌ Studio Develop Mvp Build · buildgreatproductsUse in the app repo — the repository that contains `productos/` — when the user wants the full MVP built from their ProductOS spec documents. Triggers on phrases like "build my MVP", "build the app", "execute the roadmap", "start the build", "work through the whole roadmap", "build everything", or any request to implement the entire plan rather than a single task or phase. Requires `docs/PRD.md` and `docs/ROADMAP.md` (plus `docs/PRODUCT.md` and `docs/DESIGN.md` for context). Works through every roadmap task in order — implementing, testing, and verifying each before moving on, marking checkboxes and updating the status line, committing at each phase boundary — and runs until all tasks are complete and the magic moment works end to end.
- ▌ Studio Design App Listing · buildgreatproductsUse when the user has a finished `docs/PRODUCT.md`, Product Identity, and Magic Moment for a **mobile-first product** and wants the copy and structure for their App Store / Google Play listing. Triggers on phrases like "write my app store listing", "design my app store copy", "draft my screenshot captions", "outline my App Store page", "design my icon and screenshots", "I need an ASO spec", "build my Play Store listing", or any request to translate the product strategy into mobile-acquisition copy. Reads `productos/design/BONUS-App-Store-Listing-Best-Practice.md`, walks the user through every element in the voice of a senior product marketer with ASO expertise, and writes `productos/design/4b-App-Store-Listing.md` covering icon, title, subtitle, keywords, screenshots + captions, preview video, both store descriptions, Custom Product Pages, review timing, and localization. For web/desktop, use `studio-design-landing-page`.
- ▌ Studio Define Offer Review · buildgreatproductsUse when the user has filled out their Product Offer and wants a rigorous, strategic critique before moving on. Triggers on phrases like "review my product offer", "critique my offer", "is my offer any good", "tear apart my product offer", "audit my offer", "sanity-check my positioning", "what's wrong with my offer", or any request to evaluate, sharpen, pressure-test, or rewrite the six elements (Customer, Pain, Outcome, Mechanism, Guarantee, Proof) of a product offer. Reads the filled-in Product Offer, identifies gaps in thinking, references the worked Product Offer Examples as calibration anchors, proposes rewrites in the voice of a strategic startup advisor with deep launch and exit experience, and applies approved edits directly to the Product Offer file. Especially appropriate inside a ProductOS-style "Define" workflow where the user has filled in `1-Product-Offer.md` and wants it sharpened before building the customer persona or strategy.
- ▌ Studio Design Landing Page · buildgreatproducts bundleUse when the user has a finished `docs/PRODUCT.md`, Product Identity (`productos/design/1-Product-Identity.md`), and Magic Moment (`productos/design/2-Magic-Moment.md`) for a **web or desktop product** and wants to design the copy and structural direction for their landing page / marketing site. Triggers on phrases like "write my landing page", "design my landing page copy", "draft my marketing site", "outline my homepage", "design my hero", "write the hero copy", "I need a landing page spec", or any request to translate the product strategy into web-acquisition copy. Reads `productos/design/BONUS-Web-Landing-Page-Best-Practice.md`, walks the user through every section in the voice of a senior product marketing strategist, writes `productos/design/4a-Landing-Page.md` with every headline, CTA, body section, and visual direction needed to ship, and optionally generates a lo-fi HTML wireframe at `productos/design/landing-page-wireframe.html`. For mobile-first, use `studio-design-app-listing` instead.
- ▌ Studio Design Magic Moment · buildgreatproductsUse when the user has a finished `docs/PRODUCT.md` and wants to identify their product's aha moment — the specific instant the customer realizes the product is worth keeping. Triggers on phrases like "find my aha moment", "identify the magic moment", "what's my product's aha", "where should the wow happen", "design the activation moment", "what's the Facebook-7-friends moment for my product", "magic number for my product", "where does the customer first realize the value", or any request to recommend candidate aha moments for a product. Reads `docs/PRODUCT.md`, does live research on category-specific aha-moment patterns, recommends three candidate magic moments in the voice of a senior growth strategist, picks a primary, and writes the result to `productos/design/2-Magic-Moment.md`. Especially appropriate after the Product Identity is locked in and the user is ready to design onboarding around a specific activation event.
- ▌ Studio Develop Code Review · buildgreatproductsUse when the user has uncommitted changes and wants them reviewed before committing — the deliberate whole-diff correctness pass. Triggers on phrases like "review my changes", "code review", "check my work before I commit", "am I ready to commit", "review what we just built", "anything wrong with this diff", or any request to review uncommitted work. Runs in the app repo — the repository that contains `productos/`. Reads the working tree, staged changes, and new untracked files, states what the change is trying to do, reviews across five lenses (correctness, regressions, edge cases, a thin security pass, consistency), verifies every finding against the actual source before reporting, and delivers an in-conversation report — must-fix items, considerations, pre-existing issues — ending in an explicit verdict: ready to commit or not. Works standalone in any repo.
- ▌ Studio Develop Prd Roadmap · buildgreatproductsUse when the user has a finished `docs/PRODUCT.md` and `docs/DESIGN.md` and is ready to scope their MVP and generate the two documents a coding agent builds from — `docs/PRD.md` (technical spec) and `docs/ROADMAP.md` (phased build plan with task checkboxes). Triggers on phrases like "create my PRD", "generate my roadmap", "scope my MVP", "what should my MVP be", "turn my product docs into a build plan", "start the develop phase", "I'm ready to build", or any request to translate Define and Design outputs into implementation-ready spec documents. Reads the Define docs, Magic Moment, Onboarding Flow, and Landing Page or App Store Listing, runs a structured MVP scoping interview in the voice of a senior technical product lead — core loop, feature cuts, tech stack selection — then generates both documents per the guides in `productos/develop/guides/`. Especially appropriate as the first step in a ProductOS-style Develop workflow.
- ▌ Studio Define Offer Builder · buildgreatproductsUse when the user has a product idea (or is brainstorming one) and wants to build their Product Offer from scratch. Triggers on phrases like "help me create my product offer", "walk me through the product offer", "build my offer", "craft my offer", "I have an idea help me turn it into an offer", "write my product offer", "fill out the product offer", "turn this idea into an offer", or any request to guide a founder through filling in the six elements (Customer, Pain, Outcome, Mechanism, Guarantee, Proof) of a Product Offer. Does live web research on what's currently working in AI software and apps, walks the user through each element in the voice of a strategic startup advisor, critiques weak answers using AI-aware failure patterns, and rewrites the Product Offer file in place. Especially appropriate inside a ProductOS-style "Define" workflow where the Product Offer template is empty or partial and the user wants help building it from scratch.
- ▌ Studio Design Design System · buildgreatproducts bundleUse when the user wants to turn an image reference — a screenshot, mockup, Figma URL, or live website they love — into their Design System. Triggers on phrases like "build my design system", "create my DESIGN.md", "design from image", "image to design system", "translate this screenshot into a design system", "extract design tokens", "make my design.md", "here's a site I love, capture its design", or when the user shares an image/URL in a design context with no other clear intent. Produces two mirrored artifacts: docs/DESIGN.md (Google-format YAML tokens + prose, the source of truth coding agents read) and docs/DESIGN.html (a self-contained live style guide for the human). Reads the image(s), asks only the context questions the ProductOS docs don't already answer, derives the tokens, reconciles them with the Product Identity, and writes both files together. Design phase Step 3 — runs after the UX Writing Guide and supplies the colours, fonts, and tokens the identity leaves undecided.
- ▌ Studio Develop Design Better · buildgreatproductsUse when the user is building or refactoring UI in their product codebase and wants designer-quality frontend code — not just functional code. Triggers on phrases like "design better", "make this UI feel more designed", "elevate the design quality", "build this with design best practices", "follow UX heuristics", "make this feel professional", "apply design polish", "review this for craft", or any request to apply UX/UI craft heuristics to code generation or review. Pairs with `docs/DESIGN.md`: the design system file owns **style** (colors, typography, spacing tokens, components), this skill owns **craft** (hierarchy, interaction, accessibility, motion, polish). Reference DESIGN.md tokens by name for every visual decision; apply the 50-item heuristics catalogue below for every craft decision. When a heuristic implies a token DESIGN.md doesn't have, flag it as a New Pattern for `studio-develop-design-review` to promote — never invent a value inline.
- ▌ Studio Develop Design Review · buildgreatproductsUse when the user has a `docs/DESIGN.md` and uncommitted changes in their product codebase (new components, modified styles, new screens) and wants a design-system adherence review before committing or merging. Triggers on phrases like "design review", "review my design system adherence", "check my changes against DESIGN.md", "design system check", "what design tokens am I missing", or "promote my new patterns to DESIGN.md". Runs in the app repo — the repository that contains `productos/`. Reads `docs/DESIGN.md`, inspects uncommitted git changes (working tree + staged), classifies each visual change as an Inconsistency, a New Pattern, or Already-Aligned, and writes a prioritized, timestamped report to `design-review/` (a new file per run): a fix to-do list, a promotion checklist for `docs/DESIGN.md`, and a paste-ready fix prompt for a coding agent. Optionally references `productos/design/1-Product-Identity.md` for tone if present; works standalone.
- ▌ Studio Develop Refactor Plan · buildgreatproductsUse inside an **existing app codebase** when the user wants a plan to bring the code in line with their ProductOS spec documents. Triggers on phrases like "create a refactor plan", "audit my codebase against the PRD", "plan the refactor", "what's different between my app and the PRD", "make REFACTOR.md", or any request to compare an existing codebase to `docs/PRD.md` and produce an actionable migration plan. Reads `docs/PRD.md` and `docs/ROADMAP.md` when they exist; when they don't, generates its own refactor-scoped PRD from `docs/PRODUCT.md`, `docs/DESIGN.md`, the codebase, and a short interview — no need to run `studio-develop-prd-roadmap` first. Audits the codebase, classifies every difference (missing / divergent / extra), walks the user through keep-or-remove decisions one at a time, then writes `docs/REFACTOR.md` — a phased, checkbox-tracked plan in the same format as the roadmap, executable by `studio-develop-refactor-build`.
- ▌ Studio Define Leverage Finder · buildgreatproductsUse when the user runs a business or has deep expertise but no software idea yet and wants one MVP worth building. Triggers on phrases like "find my idea", "what should I build", "I have a business but no product idea", "find the leverage in my business", "turn my expertise into software", "audit my business for software ideas", "I don't know what to build", "productize my service", "software idea for my business", or any request to go from a running business to a single software idea. Audits where the money and time actually go, inventories leverage points, generates a 3-5 idea shortlist, scores it, routes between an internal tool (removing your own bottleneck) and a customer-facing product (productizing the value you already deliver), converges on ONE idea, and writes the Leverage Audit before handing off to studio-define-offer-builder. Not for picking features in an existing codebase — that's studio-develop-feature-finder. The Define entry point for members arriving with a business instead of an idea.
- ▌ Studio Design Onboarding Flow · buildgreatproducts bundleUse when the user has a finished `docs/PRODUCT.md`, a Product Identity, and a Magic Moment hypothesis, and wants to design the onboarding flow that engineers the user toward that magic moment. Triggers on phrases like "design the onboarding flow", "create my onboarding", "build the activation flow", "wireframe my onboarding", "lay out the first-session experience", "what screens do I need for onboarding", "make the onboarding flow document", "click-through wireframe of my onboarding", or any request to translate the activation hypothesis into a screen-by-screen flow spec. Auto-selects the best-practice reference from `productos/design/onboarding/` based on product type, drafts a screen-by-screen flow in the voice of a senior onboarding designer, writes `productos/design/3-Onboarding-Flow.md`, and generates a clickable lo-fi HTML wireframe at `productos/design/onboarding-wireframe.html` the user can click through to feel the flow.
- ▌ Studio Develop Feature Finder · buildgreatproductsUse in the app repo when the user wants feature or change recommendations to achieve a specific objective. Triggers on phrases like "what should I build next", "find features to improve retention", "how do I get more users to upgrade", "recommend features", "what would increase activation", "feature ideas for my app", or any request to translate a business goal (retention, activation, conversion, revenue, referrals, engagement) into concrete product changes. Asks for the objective, reviews the codebase to understand what the app does today, researches live best practices and what comparable products have done, then delivers ranked feature recommendations with evidence, effort estimates, and how to measure each — and offers to add the chosen ones to the plan file.
- ▌ Studio Develop Refactor Build · buildgreatproductsUse in the app repo — the repository that contains `productos/` — when `docs/REFACTOR.md` exists (generated by `studio-develop-refactor-plan`) and the user wants the refactor executed. Triggers on phrases like "run the refactor", "execute the refactor plan", "work through REFACTOR.md", "start refactoring", "apply the refactor plan", or any request to carry out the planned refactor task by task. Works through every task in `docs/REFACTOR.md` in order — implementing, testing, and verifying each before moving on, marking checkboxes and updating the status line, committing at each phase boundary — and runs until all tasks are complete and the codebase is fully aligned with `docs/PRD.md`.
- ▌ Studio Develop Security Audit · buildgreatproductsUse for a full security audit of the app — the whole codebase or just uncommitted changes — producing docs/SECURITY-AUDIT.md, a verdict-first report with a checkbox fix plan a coding agent can execute. Triggers on phrases like "security audit", "is my app secure", "check for vulnerabilities", "audit my code for security", "am I safe to launch", "security review of my codebase", or any request to find security problems before or after launch. Runs in the app repo — the repository that contains `productos/`. Detects the stack (framework, database, auth, payments), maps the attack surface, audits by severity tier (secrets, database access control, unprotected routes, IDOR, exposed keys first), verifies every finding to a concrete exploit path before reporting, and separates agent-executable fixes from human-only actions like key rotation. Never auto-fixes. Works standalone in any repo.
- ▌ Studio Define Customer Persona · buildgreatproductsUse when the user has filled out their Product Offer and wants to develop a sharp, evidence-backed Customer Persona. Triggers on phrases like "build a customer persona", "define my customer", "fill in the customer persona", "who is my ideal customer", "create an ICP", "target customer profile", "persona for my product", or any request to translate a product offer into a customer persona document. Reads the user's Product Offer, researches the target market online, then walks them section by section through the Customer Persona framework — proposing hypotheses, critiquing vague answers, and producing a filled-in customer persona document. Especially appropriate inside a ProductOS-style "Define" workflow where a Product Offer markdown file already exists and a Customer Persona template is waiting to be filled in.
- ▌ Studio Design Identity Creator · buildgreatproductsUse when the user has a synthesised `docs/PRODUCT.md` (the plain-English roll-up of their Define-phase work) and wants to build their minimum viable brand identity from it. Triggers on phrases like "help me create my product identity", "build my brand identity", "design my brand", "name my product", "what's my brand worldview", "develop my brand voice", "define my visual style", or any request to guide a founder through the five word-level elements (Name, Worldview, Contrarian Belief, Tone of Voice, Visual Style) of a Product Identity. Reads `docs/PRODUCT.md`, does live research on the category's names and visual defaults, walks the user through each element in the voice of a senior brand strategist and design director, and rewrites `productos/design/1-Product-Identity.md` in place — every section ending in a concrete artifact, assembled into a one-glance Brand Card. Colours, fonts, and tokens are deliberately downstream — the Design System step derives them from a real image reference.
- ▌ Studio Design Prompt Generator · buildgreatproductsUse when the user has a finished `productos/design/1-Product-Identity.md` and `docs/PRODUCT.md` and wants paste-ready prompts for AI design tools (Pencil, paper.design, Claude Design, or MagicPath) that produce on-brand designs immediately. Triggers on phrases like "generate design prompts", "create AI design prompts", "make screen prompts for my product", "give me prompts for Claude Design / Pencil / paper / MagicPath", "prompts to design my screens", "draft my screens with AI", "give me a design prompt for [screen]", "what should I prompt my AI design tool with", or any request to translate the Product Identity into design-tool prompts. Reads both source files and writes `productos/design/Design-Prompts.md` with three prompts: Prompt 1 is always a comprehensive UI design system foundation (colors, typography, components, layout, motion) so screens share a consistent component vocabulary; Prompts 2 and 3 are two priority screens for the product type.
- ▌ Studio Distribute Gtm Strategy · buildgreatproducts bundleUse when the user wants a concrete go-to-market plan to get a product's first users — which distribution channels to use and exactly how to start each. Triggers on phrases like "go-to-market strategy", "GTM plan", "distribution plan", "how do I get users", "which channels should I use", "where do I distribute this", "marketing plan for my app", "first 100 users", "launch plan", or "pick my channels". Standard path: reads docs/PRODUCT.md or the Define docs from the ProductOS folder (productos/ at the app repo root). Standalone fallback: in a repo without ProductOS it reads the codebase for product context and asks qualifying questions to fill the gaps. Then it researches the actual named channels and competitor distribution for the niche, walks the user through choosing three ranked channels, and builds a simple, product-specific, step-by-step starter plan for each — producing a filled-in Go-To-Market Strategy document. Especially useful in a ProductOS Distribute workflow.
- ▌ Studio Define Business Strategy · buildgreatproductsUse for the optional deep dive into how the product makes money — when the money questions get real: before paid channels in Distribute, at first revenue, or when an investor asks how the model works. Requires a filled-in Product Offer. Triggers on phrases like "build my business strategy", "what's my revenue model", "what are my margins", "what's my unfair advantage", "what's my north star metric", "pricing ladder", "monetization strategy", "business model for my app", or any request to translate a product offer into the five-section Business Strategy (Revenue Model, Pricing Ladder, Cost & Margin, Unfair Advantage, North Star Metric). Reads the Product Offer, researches competitive pricing and benchmarks, then walks the user section by section — proposing hypotheses, critiquing weak choices — and fills in BONUS-Business-Strategy-Deep-Dive.md. A BONUS deep dive, not a checklist step: the week-one pricing pass (studio-define-pricing) covers most people until scaling.
- ▌ Studio Distribute Scale Automate · buildgreatproducts bundleUse after the user has run growth experiments and logged results, when they want to scale what's proven and automate it. Triggers on phrases like "scale my product", "automation roadmap", "automate what works", "double down on what works", "how do I scale this", "systematize my marketing", "make my growth scalable", "what should I automate", or "scale my growth". Reads the Growth Experiments Tracker (or, in a repo without ProductOS, asks what's already working), takes only the proven winners, and builds a roadmap that amplifies each one (do more, do better) and automates it with specific tools, MCPs/plugins, and scheduled tasks — sequenced Now/Next/Later on a manual-to-delegated maturity ladder. Produces a Scale & Automation Roadmap document. Works with ProductOS in the repo (productos/ at the app repo root) or standalone in a repo without it.
- ▌ Studio Distribute Growth Experiments · buildgreatproducts bundleUse after the user has a go-to-market plan (or live channels) and wants to systematically improve and scale them. Triggers on phrases like "growth experiments", "growth plan", "growth backlog", "what should I test", "how do I scale this channel", "marketing experiments", "improve my channel", "A/B test ideas", "growth loop", or "optimize my funnel". Reads the Go-To-Market Strategy doc (or, in a repo without ProductOS, the codebase plus a couple of questions) for the chosen channels, researches current tactics and competitor distribution for the niche, then designs product-specific experiments and writes a simple execution list — 1–3 experiments running now, each with concrete steps and a number-plus-date pass bar, plus an ordered up-next queue — and seeds a running results tracker. Prioritization (effort/impact, quick wins first) happens in the session; only the instructions land in the file. Works with ProductOS in the repo (productos/ at the app repo root) or standalone in a repo without it.
- ▌ Studio Design Design System From Code · buildgreatproductsUse when the user already has a product codebase and wants to reverse-engineer the design system already in the code into a Google-format `docs/DESIGN.md` — extracting the colors, typography, spacing, radii, elevation, and components actually used, flagging internal inconsistencies (competing values for one role — several "primary" blues, forked paddings, mixed radii, stray hex), resolving each with the user, then writing the file. Triggers on "design system from code", "reverse-engineer my design system", "I have a codebase but no DESIGN.md", "audit my codebase for design tokens", "consolidate my design tokens". Runs in the app repo — the repository that contains `productos/` — and reads CSS variables, Tailwind config, theme files and components; surfaces inconsistencies to resolve interactively; writes `docs/DESIGN.md` in Google's exact format (YAML tokens + eight sections), matching `studio-design-design-system`, compatible with `studio-develop-design-review`.
- ▌ Studio Distribute Activation Retention Audit · buildgreatproductsUse when the user has a working product codebase and wants to find the activation and retention leaks — why new users don't reach the magic moment, and why existing users don't come back — and fix them. Triggers on phrases like "activation audit", "retention audit", "find my leaks", "why do users churn", "fix my onboarding", "users sign up but don't come back", "leaky bucket", or "audit my activation funnel". Runs in the app repo — the repository that contains `productos/`. Detects product type, maps the as-built activation funnel (signup to magic moment) and retention loop (what brings users back), checks instrumentation, and writes a prioritized audit to `docs/ACTIVATION-RETENTION-AUDIT.md` (or repo root if no `docs/`) with a paste-ready fix prompt. Optionally references ProductOS files (`docs/PRODUCT.md`, `productos/design/2-Magic-Moment.md`, `productos/design/3-Onboarding-Flow.md`, `productos/distribute/BONUS-Measurement-and-Attribution.md`) if present; works standalone.
- ▌ Plaid · buildgreatproducts bundleProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".