414 件 ・ 関連度順
概要と使いどころ
When the user wants a summary of what's trending on Product Hunt, Hacker News, Indie Hackers, or other product/startup communities. Also use when the user mentions "what launched today", "trending products", "HN front page", or "keep up with the market".
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to choose between technologies, frameworks, or tools — or says "which framework should I use", "compare X vs Y", "should we migrate from X to Y", "what database should I use", "calculate TCO".
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to plan, prioritize, or structure a content program -- including identifying content pillars, mapping content to the buyer journey, choosing content types, or building an editorial calendar.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to review an existing contract, assess risk in proposed terms, or evaluate a contract before signing.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Also use when the user mentions "track competitors", "what are competitors doing", "competitor alerts", or "market watch".
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to find Slack groups, Discord servers, Reddit communities, forums, or online communities where their target audience hangs out. Also use when the user mentions "where to promote", "find communities", "community marketing", or "distribution channels".
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to analyze, categorize, or extract actionable insights from customer feedback across multiple sources, especially feature requests.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to design, improve, or audit a post-signup activation flow to get new users to their first value moment. Activate when activation is lagging, time-to-value feels excessive, or first sessions lack impact.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency analysis. Also activate for "design the system", "how should I architect this", "monolith vs microservices", or architecture decision records.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create or update their startup context document. Also use when the user mentions "set up context", "tell you about my startup", or any other skill needs context that doesn't exist yet.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to stakeholders.
日本語の概要は準備中です。原文の説明を表示しています。
Generates monthly/quarterly investor updates. Takes KPIs, milestones, challenges, financials. Writes professional investor-update.md with highlights, metrics dashboard, product updates, team news, financial summary, upcoming milestones, asks. Multiple tones from seed-stage casual to Series B formal. Use when founders need to communicate progress to investors.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a website URL, product docs, or a founder's rambling description into a tight 60-90 second explainer video built in HyperFrames -- problem/solution narrative, animated product walkthrough scenes, captions, and voiceover, ready for the homepage hero, sales emails, and onboarding.
日本語の概要は準備中です。原文の説明を表示しています。
Build a positioning and narrative where the developer is the hero and a real trend is the villain. Use when the messaging describes the product instead of the problem, sounds like every competitor, or has no urgency because nothing is at stake.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a curious developer into an activated one: the docs, the quickstart, and the first-run experience that gets them to their first real win fast, and back again. Use when people sign up or star the repo but never get it working, come once and never return, or you're about to pour traffic into a first-run that leaks.
日本語の概要は準備中です。原文の説明を表示しています。
Help the user decide what to charge and how to package it: the value metric, the tiers, the free-to-paid line, and finding the actual number. Use when the user is guessing at a price, priced too cheap and can't change it, is stuck on free vs paid, or believes "developers won't pay" so never charges.
日本語の概要は準備中です。原文の説明を表示しています。
Write a developer value proposition that is specific, provable, and free of puffery. Use when the messaging leans on "powerful," "better," "seamless," or "best-in-class," when claims have no proof, or when the same line is supposed to reach both the developer and the buyer.
日本語の概要は準備中です。原文の説明を表示しています。
Measure GTM with the metrics that matter (net developer retention, DREAM funnel) instead of vanity numbers. Use when the user has dashboards full of stars and pageviews but can't tell if go-to-market is working, or is optimizing acquisition over a leaky bucket.
日本語の概要は準備中です。原文の説明を表示しています。
Before showing the user any substantive GTM deliverable (positioning, value prop, homepage, launch post, pricing, sales script, the brief or roadmap), stress-test it against the standard as an independent critic, because the agent that wrote it is the worst judge of whether it is good. Use as a gate right before presenting work, or when the user asks whether something is actually strong.
日本語の概要は準備中です。原文の説明を表示しています。
Position an AI product when everyone claims AI and skeptics call it "just a wrapper." Find the real wedge (data, workflow, trust, domain), make reliability the differentiator, answer "won't the big labs just build this," and stop leading with "AI-powered." Use when your AI or dev tool blends into a sea of similar demos, buyers doubt the accuracy, or you can't say why you win when the model is a commodity.
日本語の概要は準備中です。原文の説明を表示しています。
Turn developer love into revenue by enabling champions and choosing a GTM model. Use when developers adopt the free tier but nobody pays, when the user is cold-selling the VP instead of arming the developer, or when picking between open-source, PLG, inbound, and sales-led.
日本語の概要は準備中です。原文の説明を表示しています。
Run developer customer discovery via a Technical Advisory Board (TAB). Use when the user has never interviewed a user who isn't a friend, is inventing messaging from a conference room, or is guessing at the roadmap instead of hearing the pain firsthand.
日本語の概要は準備中です。原文の説明を表示しています。
Structure a dev-tool homepage that converts developers into champions. Use when the landing page is written for the buyer instead of the developer, reads as salesy, buries what the product does, or makes it hard to start. Pairs with the ShipReady homepage audit.
日本語の概要は準備中です。原文の説明を表示しています。
Define a real ICP and the developer personas in the sale. Use when the user says the product is "for developers," can't name who would say no, or is marketing to whoever holds the budget instead of who actually adopts.
日本語の概要は準備中です。原文の説明を表示しています。