1,004 件 ・ 関連度順
概要と使いどころ
Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant. Use when reframing competitive strategy, escaping commoditization, designing a new category, or applying Strategy Canvas, ERRC, Six Paths, Three Tiers of Noncustomers, Buyer Utility Map, or Strategic Sequence. Includes selection-bias caveats and inline decline notes for iconic cases that later collapsed.
日本語の概要は準備中です。原文の説明を表示しています。
Conducts evidence-based product discovery through customer interviews and assumption testing. Use at project start to validate problem-solution fit.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, conditional browser lane. Reads the ticket ledger and the account, billing, and usage surfaces the member named, and decides which paying customers are about to leave. Every flag is a dossier carrying the trip wires that fired, the exact evidence behind each one, that account's whole history, and one suggested save with its cost and the screen it happens on. It reads billing screens and touches no control on them: a refund, a credit, a plan change, and a cancellation are named and never made.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, conditional browser lane. Selects from the ticket ledger hardest first, meaning by severity and then by age within severity, and writes each customer a reply into a dated queue file the member reads, edits, and sends by hand. Where the right answer is a refund, a credit, a plan change, or a cancellation, it names the remedy, the exact amount, and the exact screen, and leaves the granting to the member. It sends only where you released the channel, never posts, never resolves a ticket, spends only where you released it, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Hire one of the eight open source AI Employees (GTM Engineer, SEO/AEO, Web Dev, Social Media, Ad Manager, Sales, Customer Satisfaction, Chief of Staff) into a local folder, prove it runs, and hand over its install prompt. Also answers which one to hire first, how a hired employee runs on a schedule, how to direct it, how it improves from corrections, and how to upgrade it. Use when the user says hire an employee, install an AI employee, set up the GTM Engineer, names one of the eight, or asks how AI Employees work. It copies files and runs self tests only. It registers no schedule and sends nothing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user is launching or running a DROPSHIPPING business end to end — the full 12-phase pipeline: product research with winning criteria, Minea and PiPiAds, supplier sourcing on AliExpress, CJ, Spocket, and Zendrop, Shopify store and app setup, the 10-ads-per-week creative pipeline, interest and lookalike targeting, 3-5x markup and BE-ROAS math, customer service, and scaling. Trigger on 'start dropshipping', 'winning product research', 'Shopify store setup', 'AliExpress supplier', 'scale my dropshipping store', 'my store gets traffic and no sales'. Not for — only the ad copy, see `05-ad-copy-global`; only the product page, see `12-landing-page-brief-global`; only the account audit, see `21-ads-audit-global`; only pricing, see `17-pricing-strategy-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Dung khi can hieu khach hang du sau de viet duoc content va chon duoc tep — persona 3 tang, cau noi noi tam, pain map, objection list va ngan hang ngon ngu khach hang lay tu review va inbox that. Kich hoat khi user nhac 'insight khach hang', 'chan dung khach hang', 'customer persona', 'khach hang cua toi la ai', 'khach nghi gi', 'ho mua vi ly do gi'. Khong dung cho — thu thap thong tin khi agency nhan khach moi thi dung skill 20-brief-client-intake; nghien cuu tep de chay ads thi dung skill 51-audience-research.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a NEW product, offer, or course is going to market — beachhead segment selection, launch messaging, channels by phase across pre-launch, launch, and post-launch, milestones, success metrics, and go or no-go criteria. Trigger on 'go-to-market', 'GTM plan', 'product launch plan', 'we are launching a new product', 'beachhead segment', 'how do we launch this course'. Also use when the user has a finished product and no route to the first customers. Not for — the day-by-day execution checklist, see `60-launch-playbook-global`; the ongoing period plan, see `00-marketing-plan-global`; one campaign inside the launch, see `02-campaign-brief-global`; positioning first, see `58-positioning-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting work on a new product, client, or market — this skill creates the file `.agents/product-marketing-context-global.md` that 60+ other global skills read before they write anything: product, ICP, positioning, proof, objections, brand voice, pricing, and KPIs, with a region variant for US, EU, SEA, or LATAM. Run once, reuse forever. Trigger on 'set up marketing context', 'new client setup', 'onboard a new product', 'the AI does not know my product', 'US marketing context', 'EU GDPR setup', 'SEA market context', 'LATAM setup'. Also use when the user complains every answer comes back generic because nothing about the business was ever provided. Not for — a personal brand belonging to a founder, coach, or creator, see `22-personal-brand-context-global`; deep persona and JTBD research, see `09-customer-insight-global`; the period plan itself, see `00-marketing-plan-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when positioning needs defining or sharpening — a statement built on Promise, Proof, and Path, a differentiation matrix against competitors, category entry points, a three-level message hierarchy, and tagline directions. Trigger on 'positioning', 'positioning statement', 'what makes us different', 'USP', 'why should customers choose us over them', 'we sound the same as everyone else'. Also use when the user can list features but not a reason to pick them. Not for — competitor teardown research, see `08-competitor-research-global`; how the brand sounds in writing, see `35-brand-voice-global`; the offer and its value stack, see `31-offer-design-global`; the launch built on it, see `59-go-to-market-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when paid ad AUDIENCES must be researched and defined before launch — target profile, interest and behavior mapping per platform, audience sizing, cold, warm, and hot tiering, lookalike seeds, exclusions, and ranked targeting hypotheses to test. Trigger on 'audience research', 'who should I target', 'interest targeting', 'Meta audience for this product', 'TikTok targeting ideas', 'my targeting is too broad'. Also use when launch is imminent and the ad set targeting is still empty. Not for — persona and JTBD depth for content, see `09-customer-insight-global`; warm retargeting tiers, see `56-retargeting-plan-global`; where the budget goes, see `54-media-plan-global`; the campaign hierarchy, see `52-account-structure-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a price has to be set or changed — value-based pricing, anchoring, charm pricing, decoy tiers, good-better-best packaging, discount policy, and margin math, with currency psychology for US, EU, SEA, and LATAM plus dropshipping markup and BE-ROAS. Trigger on 'pricing strategy', 'how much should I charge', 'should I raise prices', 'price tiers', 'customers say it is too expensive', 'dropshipping markup'. Also use when the product is not selling and the user suspects price is the reason. Not for — bonuses, guarantee, and value stack around the price, see `31-offer-design-global`; persuasion beyond price, see `16-marketing-psychology-global`; ad budget math, see `10-reverse-kpi-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Generates user-facing changelogs and release notes from git commit history. Parses conventional commits, categorizes changes into features, fixes, breaking changes, and more, then rewrites technical messages into customer-friendly language. Use when the user asks to generate a changelog, write release notes, summarize recent commits, prepare CHANGELOG.md, or document what changed between versions.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a Disaster Recovery plan with RTO/RPO targets. Use when someone asks to "create a DR plan", "disaster recovery", "business continuity", or "RTO RPO". Do NOT use for step-by-step restoration runbooks — use /pmstudio-recovery instead. Designed for SaaS platform products where Coco Inc is the customer — focuses on service continuity, data recovery, and vendor dependency management rather than infrastructure rebuild.
日本語の概要は準備中です。原文の説明を表示しています。
Develop an evidence based business plan spanning customers, product, operating costs, hiring and governance. Use for this Bot Generator Bot template; creates drafts or simulations within its declared scope.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a customer problem into distinct ideas, a small prototype and a measurable learning test. Use for this Bot Generator Bot template; creates drafts or simulations within its declared scope.
日本語の概要は準備中です。原文の説明を表示しています。
Your brand designer. Names the business (with the trademark, domain and handle checks to run before falling in love with a name), writes the voice, a one-line promise and a tagline, and briefs the look: colours, type, logo and the first things a customer sees, so they match the positioning the marketing director chose. Use when the user says "name my business", "brand this", "logo", "brand identity", "what should it look like", "tagline", or "brand voice".
日本語の概要は準備中です。原文の説明を表示しています。
Maps every competitor and the gap they leave. Finds the direct competitors, indirect ones and the substitutes a buyer would use instead, from public sources only, and records what each sells, at what price, how they position themselves and what their customers complain about in public reviews, every fact with a link. Ends with a positioning map and the gap the new business can own. Use when the user says "who are my competitors", "is this market crowded", "what else is out there", "competitor analysis", "find the gap", or "who am I up against".
日本語の概要は準備中です。原文の説明を表示しています。
Time-based cohort analysis with retention and behaviour tracking. Activate when you need to measure how groups of users/customers behave over time — retention rates, revenue by cohort, or feature adoption curves.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate customer-impacting OpenAI Ruby SDK defects and privately handled security risks, then dispatch at most five evidenced, independent fixes to isolated project worktrees.
日本語の概要は準備中です。原文の説明を表示しています。
Security-first SOP for multi-tenant RAG systems. Activate when a calling agent is building, reviewing, or debugging any retrieval pipeline whose vector store is shared across more than one user, organisation, workspace, customer, or permission scope. Encodes the single non-negotiable rule — **filter at the vector store query, never after retrieval / never after rerank** — together with the per-vendor query-time filter APIs (Pinecone namespaces + `$eq`/`$in`, Weaviate `multiTenancyConfig` + tenant handle, Qdrant `is_tenant` payload index + `Filter.must`, Chroma `where`, pgvector RLS), and the cross-framework adapters (LlamaIndex `MetadataFilters`, LangChain `filter=` dict). Frame the work as preventing CVE-2024-41892 / EchoLeak / Slack-AI-class cross-tenant leakage, not as "adding a filter for relevance".
日本語の概要は準備中です。原文の説明を表示しています。
Help founders and marketers nail their positioning. Use when someone mentions "positioning," "value proposition," "who is this for," "how do I describe my product," "messaging," "ICP," "ideal customer," or is struggling to articulate what makes their product different.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a positioning canvas (competitive alternatives, differentiated value, best-fit customer, category) plus a strategic narrative and sales-pitch storyboard, and grades existing positioning or messaging. Use for 'positioning', 'how do we describe our product', 'messaging', 'our pitch isn't landing', 'category', 'differentiation', 'one-liner', 'value prop', 'old game new game'. Draws on 43 Lenny's Podcast guests incl. April Dunford, Andy Raskin and Arielle Jackson.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a product or startup idea into a ranked list of riskiest assumptions, the cheapest test for each, pass/kill thresholds, and a go/pivot/kill readout, before anyone builds. Use when someone says "validate my idea", "is this worth building", "what's the riskiest assumption", "design an MVP", "fake door", "smoke test", "will people pay", "pre-sell", "customer discovery plan" or "should we build this". Draws on 82 Lenny's Podcast guests incl. Mike Maples Jr., Eric Ries and Jake Knapp.
日本語の概要は準備中です。原文の説明を表示しています。