「pr」の検索結果

Win #1 Product of the Day on Product Hunt. Completely reverse-engineered from 30x daily winner and 3x weekly winner campaigns — ranking algorithm decoded, launch timing optimized, hunter selection guide, community engagement approach, and post-launch momentum playbook. Use this if you're: (1) already read PH launch guides but still can't break into Top 5 and need algorithm-level deep optimization, (2) targeting Daily #1 and 5,000+ sign-ups with a proven 30+ case validated approach, or (3) an investor/accelerator coaching portfolio companies on PH launches. What's inside: PH ranking algorithm decoded: weighted factors for first 3 hours, 24 hours, and weekly ranking · Pre-launch preparation: gallery optimization, product URL selection, tagline refinement (≤60 chars) · Launch timing optimization: exact PST launch windows + scheduling guide · Community engagement KPIs: upvote targets, comment response time, maker comment strategy · Platform compliance guide: understanding PH's quality signals and organic growth · Post-launch 72-hour plan: maintaining momentum, conditions for Weekly #1 · Case studies: 3 different categories (AI Tool, App, SaaS) dissected Expected outcomes: Product Hunt Daily #1 ranking · strong community engagement on launch day · 3,000–10,000+ sign-ups (depending on product-market fit) 🇨🇳 Product Hunt 打榜完整攻略 | 🇯🇵 Product Hunt ローンチガイド | 🇰🇷 Product Hunt 런칭 가이드 Keywords: Product Hunt #1, Product Hunt launch strategy, PH ranking algorithm, PH #1 daily winner, Product Hunt tips, product launch, startup launch, ranking optimization, PH gallery optimization, Community engagement strategy, maker community engagement, product strategy, launch tactics, how to win Product Hunt, product hunt best practices

🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"

This skill should be used when the user asks about "Hyprland configuration", "hyprland.lua", "hyprland.conf", "Hyprland Lua config", "hyprctl", "Hyprland keybinds", "Hyprland window rules", "Hyprland monitors", "Hyprland dispatchers", "Hyprland animations", "Hyprland workspaces", "Hyprland IPC", "Hyprland plugins", "hyprlock", "hypridle", "hyprpaper", "hyprcursor", "hyprpicker", "hyprsunset", "xdg-desktop-portal-hyprland", "Hyprland on NixOS", "Hyprland Home Manager", "Hyprland layouts", "Hyprland dwindle", "Hyprland master layout", "Hyprland FAQ", "Hyprland performance", "Hyprland Nvidia", "Hyprland screen sharing", "Hyprland special workspace", "Hyprland smart gaps", "Hyprland multi-monitor", "Hyprland tearing", or any topic related to configuring, troubleshooting, or extending the Hyprland Wayland compositor and its ecosystem tools.

日本語の概要は準備中です。原文の説明を表示しています。

Use when configuring the Salesforce product catalog and pricing structure: creating Product2 records, setting up Standard and custom Pricebooks, managing PricebookEntry junction records, enabling multi-currency pricing, configuring Product Schedules (Revenue and Quantity), or troubleshooting incorrect prices on Opportunity line items and Quotes. Triggers: 'add product to pricebook', 'pricebook entry', 'standard pricebook', 'product catalog', 'multi-currency product pricing', 'product schedule', 'revenue schedule', 'quantity schedule', 'deactivate product'. NOT for bulk catalog loads — use data/product-catalog-data-model. NOT for CPQ bundles and product rules — use admin/cpq-product-catalog-setup.

日本語の概要は準備中です。原文の説明を表示しています。

Configuring or troubleshooting Salesforce CPQ Advanced Approvals: SBAA__ApprovalRule__c, SBAA__ApprovalVariable__c for cross-line aggregation, SBAA__ApprovalChain__c for ordered approver sequences, escalation timeouts, Smart Approvals for re-quote skip logic, and the managed package's permission sets. Trigger keywords: CPQ Advanced Approvals, SBAA approval rule, approval variable, approval chain, discount approval, line-level approval, Smart Approvals, requote approval. NOT for standard non-CPQ Salesforce approval processes - use admin/approval-processes. NOT for CPQ price rules and discount schedules - use admin/cpq-pricing-rules.

日本語の概要は準備中です。原文の説明を表示しています。

Extract complete product information from any e-commerce product page. Returns name, price, currency, brand, images, description, SKU/ASIN/EAN/UPC/GTIN/MPN identifiers, stock availability, rating, review count, variants, and seller. Works on Shopify, Amazon, WooCommerce, eBay, Walmart, Etsy, AliExpress, Alibaba, Target, Best Buy, Rakuten, Magento, BigCommerce, PrestaShop, and any public e-commerce site. Accepts product URL, keyword, or product identifier (SKU/ASIN/EAN/UPC). Use when: scrape product page, get product details, extract price and availability, product info extraction, check product data, product detail scraping, get product from URL, keyword product search, ASIN lookup, EAN search, UPC lookup, price check, product research, compare products, monitor product price, get product images, product brand and description, ecommerce data extraction, product catalog scraping, product page scraper, get item price, fetch product info.

日本語の概要は準備中です。原文の説明を表示しています。

Scrape Product Hunt daily/weekly/monthly/yearly leaderboard launches with full product details, maker profiles, and website contact info. Use when user mentions Product Hunt, producthunt, PH scraper, product hunt launches, product hunt leaderboard, scrape product hunt, product hunt data, PH daily launches, product hunt upvotes, product hunt maker info, extract product hunt, product hunt today, top products product hunt, product hunt archive, PH products, product hunt email extraction, product hunt contact info, producthunt.com scraping, get product hunt launches, product hunt API alternative. Also applies to: startup launch monitoring, new product discovery, maker/founder contact enrichment, product hunt lead generation, daily product hunt digest, competitive product tracking.

日本語の概要は準備中です。原文の説明を表示しています。

Programmatically driving Salesforce Approval Processes from Apex — `Approval.process(ProcessSubmitRequest)` to submit, `ProcessWorkitemRequest` to approve / reject / reassign, recall semantics, querying `ProcessInstance` and `ProcessInstanceWorkitem` to find pending approvals, and the bulk-submit / bulk-action error-row handling. Covers when to use Apex-driven approval (system-initiated submission, batch approvals, custom UIs) vs leaving the platform's standard buttons in place. NOT for the Approval Process metadata definition itself (that's admin / declarative — see admin/approval-processes), NOT for Flow-based approvals (use flow/flow-orchestration-patterns).

日本語の概要は準備中です。原文の説明を表示しています。

Act as a project-management copilot (PM/PMO) for the delivery loop: charters, plans and schedules, estimates, risk registers, status reports, scope changes, stakeholder communication, meeting actions, lessons learned, and portfolio roll-ups, in a per-project `_project/` workspace. Use whenever the user wants to start, plan, track, rescue, or report on a project: "kick off this project", "make a project plan / timeline / WBS", "what date can I commit to", "build a risk register", "run a pre-mortem", "write the weekly status report", "the deadline slipped, what now", "turn this meeting into action items", "review my project portfolio", in any language ("quản lý dự án", "gestion de projet", "プロジェクト管理", "项目管理"), even when they never say "project management". Also use whenever a `_project/` directory exists and the user asks about schedule, deadline, risk, status, scope, budget, or stakeholders. Not for what to build (product-manager) or company-level bets (strategy-board).

Act as a product-manager copilot that turns evidence into product decisions and artifacts: backlogs and prioritization, PRDs and user stories, metrics and OKRs, experiments, launch plans, feedback triage, and pricing/packaging, kept in a per-product workspace. Use whenever the user wants to decide what to build, spec it, or ship it: "write a PRD for…", "prioritize our backlog", "what should we build next", "plan OKRs", "define our north star metric", "design an A/B test", "plan the launch", "triage this customer feedback", "platform or feature?", in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "プロダクト管理", "产品经理"), even when they never say "product manager". Also use when the user returns to a product workspace this skill created (a directory holding `product.md`, `state.md`, and `decisions.md`). Not for deep user discovery (design-thinking), desk market facts (market-researcher), or company-level bets (strategy-board).

SwiftUI のレイアウト落とし穴・ベストプラクティス・非推奨パターンと、 iOS / watchOS アプリの実機配布 (Provisioning / App Group / Code Signing / Apple Watch Developer Mode / Xcode 15+ Debug dylib) トラブルシューティング のガイド。コード生成・修正時に既知のレイアウトバグを防ぎ、 App Group + watchOS + Apple Watch の実機インストール失敗を 7 段階フレームワークで診断・解消する。 Use when: SwiftUI のコードを書く・修正するとき。 レイアウト崩れを修正するとき。safeAreaInset や ViewThatFits を使うとき。 マルチデバイス対応するとき。iOS + watchOS アプリの実機ビルド / 配布で provisioning / App Group / Manual Signing / Apple Watch の UDID / Xcode 自動署名の 罠に詰まったとき。Apple Watch に "Could not install at this time" が出たとき。 Triggers: "SwiftUI", "layout", "safeAreaInset", "ViewThatFits", "GeometryReader", "レイアウト", "崩れ", "表示バグ", "iPhone SE", "ATT", "ATTrackingManager", "requestTrackingAuthorization", "AdMob", "広告", "Provisioning Profile", "App Group", "Manual Signing", "Code Signing", "Apple Watch", "watchOS", "Install できない", "Could not install at this time", "Bundle ID 紐付け", "Xcode Automatic Signing", "embedded.mobileprovision", "Spaceship", "App Store Connect API", "WKCompanionAppBundleIdentifier", "Developer Mode", "Privacy & Security", "watchOS Developer Mode", "Apple Watch に App を入れられない", "整合性を確認できなかった", "integrity check", "ENABLE_DEBUG_DYLIB", "__preview.dylib", "debug.dylib", "Xcode 15 Preview", "SwiftUI Preview dylib", "ENABLE_PREVIEWS", "AppIntents", "AppShortcut", "AppShortcutsProvider", "AppEntity", "AppEnum", "Siri", "Siri に流れる", "Siri がリマインダーに流れる", "updateAppShortcutParameters", "Invalid parameter type", "Invalid Utterance", "applicationName", "CFBundleDisplayName", "CFBundleSpokenName", "TaskEntityQuery", "AppEntityQuery", "TimelineProvider", "recommendations", "WatchConnectivity", "WCSession", "updateApplicationContext", "sessionDidBecomeInactive", "iPhone と Watch でデータ共有", "App Group 共有できない", "scenePhase", "ポーリング", "watchOS バッテリー", "TextField 文字色 watchOS", "Picker 文字色 watchOS", "Single Size AppIcon", "watchOS AppIcon"

Research an affiliate program and create a verified listing for openaffiliate.dev. Use this skill when the user asks anything about listing a program, adding an affiliate program to the directory, submitting a program to list, creating a listing, documenting an affiliate program, sharing an affiliate program, writing a program profile, posting a program to openaffiliate.dev, or contributing a new program. Also trigger for: "list a program", "add affiliate program", "submit program to list", "create listing for X", "document affiliate program", "share affiliate program", "write a listing", "post to openaffiliate.dev", "add X to the directory", "register an affiliate program", "publish affiliate program", "new program listing", "profile this affiliate program", "catalog this program".

日本語の概要は準備中です。原文の説明を表示しています。

Use when hosting, deploying, or operating an app on the Prisma Platform: projects, branches, preview environments, services and their versions, Prisma Postgres databases, object-store buckets, environment variables, custom domains, logs, or the GitHub integration. Triggers on "Prisma Platform", "Prisma Compute", "Prisma Postgres", "Prisma Storage", "preview environment", `prisma deploy`, `prisma dev`, `prisma auth`, `prisma project`, `prisma branch`, `prisma service`, `prisma postgres`, `prisma bucket`, `prisma git`, `prisma.config.ts`, promote, rollback.

日本語の概要は準備中です。原文の説明を表示しています。

Use when configuring or troubleshooting Salesforce CPQ pricing: Price Rules, Price Conditions, Price Actions, Lookup Queries, Discount Schedules, Block Pricing, Percent of Total, and Contracted Prices. Trigger keywords: CPQ price rule, price action, discount schedule, block pricing, percent of total, contracted price, SBQQ__PriceRule__c, CPQ quote calculation engine, price waterfall. NOT for picking the pricing method — use admin/pricing-model-design. NOT for pricebook pricing without CPQ — use admin/products-and-pricebooks.

日本語の概要は準備中です。原文の説明を表示しています。

Design, review, or troubleshoot Salesforce Approval Processes. Triggers: 'submit for approval', 'approver', 'record locked', 'recall approval', 'approval step', 'discount approval', 'approvalProcess metadata', 'ProcessInstanceWorkitem', 'recordEditability', 'process order', 'no approver found', 'pending approval'. NOT for submitting or acting on approvals from Apex - use admin/approval-process-apex-patterns. NOT for CPQ Advanced Approvals (SBAA rules and chains) - use admin/cpq-approval-workflows. NOT for multi-stage cross-object orchestration with SLAs - use flow/orchestration-flows.

日本語の概要は準備中です。原文の説明を表示しています。

Walmart product detail page extractor: given a walmart.com product URL (walmart.com/ip/...), extract full product data including itemId, title, brand, model, UPC, price, wasPrice, currency, availability, category path, seller info, all images, shortDescription, longDescription, product highlights, full specifications as key-value map, color/size variants with item IDs, fulfillment options (shipping/pickup/delivery with dates), return policy, and review summary with rating breakdown. Use when user mentions walmart product detail, walmart item page, walmart product page, scrape walmart product, extract walmart item, walmart product data, walmart item details, walmart product info, walmart product scraper, walmart item scraper, walmart product URL, walmart ip URL, walmart.com/ip, walmart specifications, walmart product specs, walmart product images, walmart variants, walmart color options, walmart size options, walmart seller info, walmart return policy, walmart fulfillment options, walmart shipping info, walmart availability, walmart product enrichment. Also applies to enriching a list of walmart product URLs with full details, monitoring walmart product price and availability changes, building a walmart product catalog, competitive product research on walmart, and batch collection of full product data from walmart item IDs.

日本語の概要は準備中です。原文の説明を表示しています。

Optimize pricing pages, pricing models, and pricing strategy. Use when the user asks about pricing, pricing pages, how to price a product, tiered pricing, freemium vs. paid, price testing, pricing psychology, or pricing page design. Trigger phrases include "pricing", "pricing page", "how to price", "pricing strategy", "freemium", "tiered pricing", "per-seat pricing", "usage-based pricing", "pricing experiment", "price anchoring", "pricing psychology", "pricing optimization".

日本語の概要は準備中です。原文の説明を表示しています。

音乐制作 / 混音 (音乐制作 / 混音 (Music Production & Mixing) — 录音棚与卧室工作室里把一首歌从编曲/录音/编程做到混音/母带成品的工程+艺术认知操作系统，面向制作人(producer)、混音师(mixing engineer)、母带工程师(mastering engineer)、beatmaker、唱作人/bedroom producer，以及想入行/服务这行(录音棚、plugin 厂商、sample 公司)的视角。覆盖: (a) 第一性张力 — **服务歌曲/情绪 (serve the song / emotion-first: 技术只为打动人，'if it sounds good it is good'，用耳朵不用眼睛) ⇄ 技术正确/工程纪律 (technical correctness: gain staging 增益结构、headroom 余量、相位 phase、监听校准、LUFS 响度规范)**; **黄金耳朵/直觉混音 (mix by ears, reference-driven, 不看分析仪) ⇄ 看表/分析仪/规则 (mix by metrics: EQ 曲线、频谱仪 spectrum analyzer、相关计 correlation meter)**; **少即是多/减法混音 (subtractive, 'less is more', 录好源头 = 混音成功一半) ⇄ 重度处理/'we'll fix it in the mix' (heavy processing, 后期补救)**; **In-the-box 全数字 (ITB: DAW + 插件，召回方便，bedroom 可达专业) ⇄ 模拟硬件/outboard (analog console + 硬件，'mojo'/谐波染色 vs 召回噩梦)**; **人性化/groove/不完美 (humanize, push/pull, 'the feel') ⇄ 量化/网格/修音 (quantize to grid, pitch-correct, 'in the pocket' 靠编辑)**; (b) 核心工作流 / pipeline (最标准、最易蒸高质量+CLI 化) — 编曲制作 arrangement/production → 录音/编程 tracking/programming → 编辑 editing (comping 选段/quantize/pitch-correct/time-align) → 混音 mixing (gain staging → balance 平衡 → EQ → compression → 空间 reverb/delay → 自动化 automation → 总线/母线处理 bus/mix-bus) → 母带 mastering (响度/EQ/限制 limiting/dither/排序+间隔) → 交付 delivery (DDP/streaming spec/stems); (c) 工具栈 — DAW (Pro Tools 录音棚标准/Ableton Live 电子+现场/Logic Pro Mac 性价比/FL Studio beatmaker/Cubase/Studio One/Reaper); 插件 (EQ: FabFilter Pro-Q/SSL/API; 压缩: 1176/LA-2A/SSL bus comp 及其复刻 Waves/UAD/Plugin Alliance; 混响: Valhalla/Lexicon/Bricasti; 调音: Auto-Tune/Melodyne; 限制器 limiter: Pro-L 2/Ozone); 硬件 (监听音箱 monitors: Yamaha NS-10/Genelec; 声学处理 acoustic treatment; 转换器 converters: Apollo/RME; 话筒 mics: U47/SM7B/57); 采样/音色 (Splice/sample packs/Kontakt/Serum 合成器); (d) 知识正典 — Mixing Secrets for the Small Studio (Mike Senior)、The Mixing Engineer's Handbook / Recording Engineer's Handbook (Bobby Owsinski)、Zen and the Art of Mixing (Mixerman)、The Art of Mixing (David Gibson 可视化)、Modern Recording Techniques、Sound on Sound 杂志、Mix With The Masters 大师课、Pensado's Place; (e) figures/流派 — 混音大师 (Chris Lord-Alge CLA 摇滚/Andrew Scheps 'Stadium' 3-bus/Tony Maserati/Manny Marroquin/Serban Ghenea 流行隐形混音/Michael Brauer multing); 制作人 (Rick Rubin 减法/氛围、Quincy Jones、Dr. Dre 完美主义、Max Martin 流行结构、Jack Antonoff、Finneas bedroom→Grammy、Metro Boomin/trap、Timbaland、Pharrell); 母带 (Bob Katz K-system/响度战争批判、Bob Ludwig、Greg Calbi); 教育者 (Mike Senior、Pensado、Warren Huart Produce Like A Pro、Dan Worrall 技术深挖); (f) 行业话术/黑话 — gain staging/headroom/LUFS/true peak/comping/bouncing/printing/stems/DI/reamp/sidechain/parallel compression 并行压缩/mid-side/bus/aux/send-return/dry-wet/transient/sibilance/de-ess/pumping/mud 浑浊/harsh 刺耳/boxy/muddy/in the pocket/the pocket/quantize/swing/groove/vibe/mojo/reference track/A/B/recall/print/glue 胶水; (g) 争议/批判 — 响度战争 loudness war (Bob Katz/Loudness Penalty/streaming 归一化 LUFS 终结了吗)、修音/Auto-Tune 之争 (artistic vs cheating)、ITB vs 模拟玄学 (硬件 'warmth' 是否安慰剂、null test 盲测)、preset/AI 混音 (iZotope/LANDR/sample-based 是否毁了 craft)、bedroom producer 民主化 vs 录音棚消亡、'loudness'/over-compression、plugin 复刻 vs 真硬件、Spotify normalization 对母带的影响、过度依赖 reference/抄袭; (h) 创意 vs 技术张力是本行业 deep tacit 知识的核心 — 大量隐性 '听感' 知识难以言传，靠 reference/学徒/千小时积累。不含: 现场扩声 live sound/PA、音乐理论/作曲 composition (虽相关但聚焦录音棚后期制作)、配乐/film scoring (虽相关但聚焦歌曲制作)、纯硬件电子工程/合成器 DIY、音乐商业/版权/发行 (虽相关但聚焦制作技艺本身)。) Master OS — automated mastery of 音乐制作 / 混音 (Music Production & Mixing) — 录音棚与卧室工作室里把一首歌从编曲/录音/编程做到混音/母带成品的工程+艺术认知操作系统，面向制作人(producer)、混音师(mixing engineer)、母带工程师(mastering engineer)、beatmaker、唱作人/bedroom producer，以及想入行/服务这行(录音棚、plugin 厂商、sample 公司)的视角。覆盖: (a) 第一性张力 — **服务歌曲/情绪 (serve the song / emotion-first: 技术只为打动人，'if it sounds good it is good'，用耳朵不用眼睛) ⇄ 技术正确/工程纪律 (technical correctness: gain staging 增益结构、headroom 余量、相位 phase、监听校准、LUFS 响度规范)**; **黄金耳朵/直觉混音 (mix by ears, reference-driven, 不看分析仪) ⇄ 看表/分析仪/规则 (mix by metrics: EQ 曲线、频谱仪 spectrum analyzer、相关计 correlation meter)**; **少即是多/减法混音 (subtractive, 'less is more', 录好源头 = 混音成功一半) ⇄ 重度处理/'we'll fix it i

日本語の概要は準備中です。原文の説明を表示しています。

Query TikTok e-commerce product leaderboards via Kalodata and query detailed data for specific products. Supports viewing high-ranking/hot-selling products by region, currency, language, and date range, and using productId to retrieve price range, sales, revenue, commission rate, listing/delisting time, and owning shop. Trigger when users mention TikTok product ranking, TikTok bestseller chart, TikTok top products, kalodata product rank, TikTok product detail, TikTok product profile, product price, product sales, TikTok product ranking, TikTok bestseller chart, TikTok top products, kalodata product rank, TikTok product detail, kalodata product detail, product analytics. Even if the user does not explicitly mention "kalodata", trigger this skill whenever their need involves viewing TikTok product leaderboards or detailed data for a specific TikTok product.

日本語の概要は準備中です。原文の説明を表示しています。

Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a customer referral program (who may accept the reward, how the introduction is made), designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for an early-stage startup where the founder is still doing the selling — running founder-led sales, setting up a design-partner program, judging whether you have product-market fit, deciding what not to do yet, deciding when to hire the first AE or first marketer, and moving upmarket to larger buyers. Also use it when your company has just acquired another (or is about to), to plan the marketing integration: what you may and may not do between signing and close, the first letter to the acquired customers, whether to keep, endorse, fold in or retire the acquired brand, merging the two marketing databases without mailing people who opted out, when to start cross-selling, and announcing a product sunset. Also use it to design a demand-generation campaign and the channel plan it runs on: one campaign with one job, the offer for buyers who are and are not in market, what each channel is for, the kill and scale rules set before launch, the follow-up sales agrees to, the yearly calendar of always-on programs and tentpole campaigns, and which channels to keep, test or stop. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: founder-led sales, founder-led GTM, design partners, design partner agreement, first customers, first 10 customers, do we have product-market fit, PMF, Sean Ellis test, very disappointed survey, pre-seed, seed stage, when to hire our first AE, first sales hire, first marketing hire, moving upmarket, going upmarket, enterprise readiness, first enterprise deal, what do enterprise buyers need before they sign, positioning, product launch, beta program, early access program, design partners, private preview, public preview, general availability, GA launch, when can we call it GA, can sales sell a beta feature, selling the roadmap, launch tier, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, ideal customer profile, ICP, what is our real ICP, who actually buys from us, refresh our ICP from closed-won deals, ICP refresh before planning, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget. Also triggers on public-sector marketing: sell to government, government marketing, public sector go-to-market, federal marketing, state and local government, SLED, FedRAMP, FedRAMP marketing claims, can we say FedRAMP ready, GovRAMP, StateRAMP, VPAT, accessibility confor

日本語の概要は準備中です。原文の説明を表示しています。

Nexscope Ozon product report search: filters Ozon products by multi-dimensional metrics including sales, revenue, sales/revenue growth rate, cart conversion rate, order conversion rate, price, rating, review count, QA count, variant count, page views, gross margin, return/cancellation rate, ad spend share, weight/volume, listing time, brand, seller, fulfillment method, and labels. Returns each product's SKU, title, price (RUB), sales, revenue, lost revenue, conversion rate, rating, reviews, brand, seller, fulfillment method, listing days/months, and complete product report fields. Use for Ozon product selection, competitor product analysis, best-seller mining, price/conversion band filtering. Trigger when the user mentions Ozon product report, Ozon product selection, Ozon product filtering, Ozon product analysis, Ozon best-selling products, Ozon competitor product analysis, Ozon product report, Ozon product screener, filter Ozon products by sales, Ozon best-seller mining, Nexscope Ozon product report. Also trigger when the intent is to filter Ozon products by multiple metrics and view product-level reports, even without explicitly mentioning Nexscope.

日本語の概要は準備中です。原文の説明を表示しています。

🇺🇸 Reddit Marketing & Growth Playbook 2026 — The complete Reddit operations SOP for AI/SaaS founders. Covers account warming (Karma 0→500 in 20 days), shadow ban prevention, multi-account matrix via fingerprint browsers, subreddit selection across 10K+ communities, content templates (90/10 rule), Product Hunt × Reddit flywheel, AMA strategy. Why this matters NOW: Reddit content is 40.11% of ChatGPT/Claude training data — the highest-weighted English UGC source. Battle-tested by AFFiNE Reddit campaigns generating 3-4万有效曝光 with 5-8% GitHub Star conversion, plus 7 case studies (Adobe 3x conversion, Base44 $80M AMA, SenseNova-U1 multi-sub launch, Starterstory 0→3K users). 🇨🇳 Reddit 运营增长实战手册 — AI/SaaS 出海 founder 的 Reddit 完整 SOP。覆盖账号体系(20天养号 Karma 0→500)、影子封禁防御、指纹浏览器矩阵、10万+ subreddits 筛选、内容模板(90/10 法则)、Product Hunt × Reddit 飞轮、AMA 打法。**为什么现在做:Reddit 内容占 ChatGPT/Claude 训练数据 40.11%,是最高权重的英文 UGC 来源**。基于 AFFiNE Reddit 实战 3-4 万曝光 + 5-8% Star 转化,含 7 个完整案例(Adobe 3x 转化、Base44 $80M AMA、SenseNova-U1 多社区联动、Starterstory 0→3K 用户冷启动)。 🇯🇵 Reddit マーケティング＆グロースプレイブック — AI/SaaS創業者向けの完全なReddit運用SOP。アカウント育成（20日でKarma 0→500）、シャドウBAN防止、フィンガープリントブラウザマトリックス、サブレディット選定、コンテンツテンプレート（90/10ルール）、Product Hunt × Redditフライホイール、AMA戦略をカバー。**重要な理由：Reddit コンテンツは ChatGPT/Claude のトレーニングデータの40.11%を占める英語 UGC 最大の情報源**。AFFiNE Redditキャンペーン3-4万インプレッション＋5-8% GitHubスター変換で実証。7つの実例（Adobe 3倍変換、Base44 $80M AMA、SenseNova-U1、Starterstory 0→3Kユーザー）。 🇰🇷 Reddit 마케팅 & 그로스 플레이북 — AI/SaaS 창업자를 위한 완전한 Reddit 운영 SOP. 계정 워밍업(20일 Karma 0→500), Shadow Ban 방지, 핑거프린트 브라우저 매트릭스, 서브레딧 선정, 콘텐츠 템플릿(90/10 룰), Product Hunt × Reddit 플라이휠, AMA 전략을 다룹니다. **지금 해야 하는 이유: Reddit 콘텐츠는 ChatGPT/Claude 학습 데이터의 40.11%를 차지하는 최대 영어 UGC 소스**. AFFiNE Reddit 캠페인 3-4만 노출 + 5-8% GitHub Star 전환으로 검증. 7가지 사례 연구(Adobe 3배 전환, Base44 $80M AMA, SenseNova-U1, Starterstory 0→3K 사용자). Triggers: "reddit marketing" | "reddit growth" | "reddit ads" | "reddit advertising" | "reddit strategy" | "reddit promotion" | "subreddit marketing" | "reddit playbook" | "reddit SOP" | "reddit shadow ban" | "shadow ban prevention" | "reddit karma" | "reddit AMA" | "reddit product launch" | "reddit AI training data" | "reddit GEO" | "AFFiNE reddit case" | "Base44 AMA" | "SenseNova Reddit" | "subreddit selection" | "r/SaaS posting" | "r/MachineLearning self-promotion" | "fingerprint browser matrix" | "AdsPower reddit" | "reddit account farming" | "reddit 90/10 rule" | "reddit content strategy" | "reddit indie founder" | "reddit cold start" | "Reddit 运营" | "Reddit 营销" | "Reddit 防封" | "Reddit 矩阵号" | "Reddit 出海" | "Reddit 引流" | "Reddit 冷启动" | "影子封禁" | "Reddit Karma" | "Reddit 养号" | "Reddit AMA" | "Reddit マーケティング" | "Reddit グロース" | "Reddit 마케팅" | "Reddit 그로스"

🇺🇸 Product Launch & Product Hunt #1 Playbook — Multi-channel launch timing and sequencing. T-14 warm-up → T-0 launch day → T+7 momentum. Hunter selection, maker comment templates, comment cadence, anti-shadowban rules. Distilled from 30+ Product Hunt #1 daily launches across 150+ AI startups. **Supports 3 product paths: developer/maker (PH+GitHub), B2C consumer (Reddit/communities/TikTok, skip PH), B2B (LinkedIn+media).** 🇨🇳 产品发布与 Product Hunt 夺冠手册 — 多渠道发布的时序与节奏。T-14 预热 → T-0 发布日 → T+7 后续。Hunter 选择、maker comment 模板、评论节奏、防 shadowban。提炼自 30+ 次 Product Hunt 日冠、150+ AI 创业公司实战。**支持三种产品路径：开发者/maker（PH+GitHub）、2C 消费者（社区种子/TikTok，跳过 PH）、B2B（LinkedIn+媒体）。** 🇯🇵 プロダクトローンチ＆Product Hunt 1位プレイブック — マルチチャネルのローンチ時系列。T-14準備→T-0当日→T+7モメンタム。ハンター選定、メーカーコメント、コメントリズム、シャドウバン回避。**3つの製品パス対応：開発者/maker（PH+GitHub）、2C消費者（コミュニティ種・TikTok、PHスキップ）、B2B（LinkedIn+メディア）。** 🇰🇷 제품 출시 & Product Hunt 1위 플레이북 — 멀티채널 출시 타이밍과 시퀀싱. T-14 워밍업 → T-0 출시일 → T+7 모멘텀. 헌터 선정, 메이커 코멘트, 댓글 리듬, 섀도밴 방지. **3가지 제품 경로 지원: 개발자/maker(PH+GitHub), 2C 소비자(커뮤니티 씨드/TikTok, PH 건너뜀), B2B(LinkedIn+미디어).** Triggers: "product launch" | "launch strategy" | "Product Hunt" | "PH launch" | "how to launch" | "go to market" | "GTM" | "launch day" | "find a hunter" | "maker comment" | "launch sequencing" | "发布策略" | "产品发布" | "发 PH" | "Product Hunt 准备" | "找 hunter" | "ローンチ" | "출시 전략"

Evaluates and scores Claude prompts and system prompts using a six-dimension Scorecard with anchored 1-5 rubrics. Trigger on: "review my prompt," "score this prompt," "rate my prompt," "evaluate this prompt," "improve my prompt," "what's wrong with my prompt." Also trigger on: "why isn't my prompt working," "my prompt produces bad output," "help me fix this prompt," "is this prompt any good." Scorecard covers Objective Clarity, Context Specificity, Reasoning Fit, Output Precision, Behavioral Calibration, and Architectural Efficiency, plus a five-question Output Evaluation Rubric for assessing actual output. Also use when the user pastes a system prompt and asks for feedback. Activate whenever structured quality assessment of a single prompt is the primary need. Do NOT use for project-level audits involving Custom Instructions architecture, knowledge file organization, or multi-file Project structure (use rootnode-project-audit if available).

日本語の概要は準備中です。原文の説明を表示しています。