🇺🇸 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" | "ローンチ" | "출시 전략"
「eq」の検索結果
1.3万 件 ・ 関連度順
概要と使いどころ
Conjecture generation, sequence analysis, and experimental mathematics for mathematical discovery. Covers sequence analysis (OEIS lookups, recurrence relations, generating functions), pattern detection methods (finite differences, ratio analysis, modular patterns), conjecture generation workflow, classical integer sequences (Fibonacci, Catalan, partition numbers, Bernoulli numbers), combinatorial identities, the probabilistic method (Erdos, expected value arguments, Lovasz Local Lemma), AI-assisted discovery (FunSearch, Ramanujan Machine), and confidence calibration with cautionary tales (Mertens conjecture, Polya conjecture). Use when discovering patterns, analyzing sequences, generating conjectures, or working with combinatorial identities.
日本語の概要は準備中です。原文の説明を表示しています。
> Formal oracle for behavioral equivalence via bisimulation games. Triggers: behavioral equivalence check, bisimulation game, are two systems equivalent, did a skill update preserve behavior, attacker-defender game, partition refinement, distinguishing trace. >>>>>>> origin/main
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting a new feature, gathering requirements for an unfamiliar domain, refining a vague idea into actionable scope, or when a user request is ambiguous or underspecified. Conducts SAM Stage 1 discovery — structured requirements gathering through user discussion, asking WHO/WHAT/WHEN/WHY and never HOW. Produces the ARTIFACT:DISCOVERY document containing feature requirements, NFRs, goals, anti-goals, references, and resolved questions. Supports backlog item self-initialization via a
日本語の概要は準備中です。原文の説明を表示しています。
Analyze git branches and generate structured MR/PR descriptions with domain-based change categorization — bug fixes, enhancements, technical debt, documentation, testing, build/CI, and non-functional changes. Use when preparing merge request descriptions, pull request bodies, writing changelogs from git diffs, documenting branch changes, or generating release notes. Works with GitHub and GitLab without requiring JIRA or issue tracker integration.
日本語の概要は準備中です。原文の説明を表示しています。
Construct and score Grand Slam Offers using the Value Equation — sourced pain mining, dream outcome articulation, problems→solutions→trim-and-stack offer construction, guarantee/scarcity/bonus design, 1-10 scoring on the four Value Equation variables, pricing sanity pass, and compliance check. Use when "build an offer", "grand slam offer", "value equation", "offer stack", "make this offer irresistible", "design a guarantee", "hormozi offer", "why isn't my offer selling", "pricing and packaging for my offer", or any request to design, score, or rework a commercial offer.
日本語の概要は準備中です。原文の説明を表示しています。
Builds growth equity return models with minority/majority economics, participation rights, and preference stack analysis. Use when modeling growth equity returns, projecting minority investment outcomes, or analyzing preference structures.
日本語の概要は準備中です。原文の説明を表示しています。
Processes LP interest transfer requests with GP consent evaluation, ROFR administration, and transfer documentation requirements. Use when managing LP transfers, evaluating transfer requests, or coordinating interest assignments.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses market receptivity for equity issuance with sector sentiment, volatility, and comparable recent offering performance. Use when timing equity offerings, analyzing market windows, or evaluating issuance conditions.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates convertible bond and mandatory convertible structures with equity sensitivity, credit floor, and Greeks analysis. Use when analyzing convertible offerings, pricing equity-linked instruments, or modeling conversion economics.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 1 of 5 — Socratic interview capturing WHAT and WHY; outputs a sprint-sized REQ doc for plan-architecture. Use only when the user asks to run Phase 1, plan requirements, or start the requirements interview — never trigger automatically from a feature description.
日本語の概要は準備中です。原文の説明を表示しています。
Guide requirement writing, user story creation, and feature specification. Use when: writing requirements, user stories, issues, feature planning. Keywords: requirement, user story, issue, feature, specification, 需求, 功能規劃, 規格.
日本語の概要は準備中です。原文の説明を表示しています。
Prevents premature execution on ambiguous requests. Analyzes request clarity using 5W1H decomposition, surfaces hidden assumptions, and generates structured clarifying questions before work begins. Use at the start of any non-trivial task, or when a request could be interpreted multiple ways. Triggers on "뭘 원하는건지", "요구사항 정리", "clarify", "what exactly", "scope", "requirements", "정확히 뭘", "before we start".
日本語の概要は準備中です。原文の説明を表示しています。
Drive a GitHub Copilot (or any bot reviewer) pull-request review to a clean pass without babysitting it: fix each finding in its own commit, reply to the review thread with the fix sha, resolve the thread, re-request the bot, and poll for the async re-review. Covers the thread node-id (PRRT_...) vs comment databaseId distinction, the resolveReviewThread GraphQL mutation, the copilot-pull-request-reviewer[bot] slug, and how to read the bot's verdict (COMMENTED plus a "human review recommended" banner is not a blocking finding). Use when Copilot has left review comments on your PR, when bot review threads must be closed out with an auditable fix-reply-resolve trail before merge, or when you need to verify that a re-review actually landed on the new HEAD rather than the old one.
日本語の概要は準備中です。原文の説明を表示しています。
Apply GitHub repository security protections tier by tier — rulesets, read-only Actions token, secret scanning + push protection, Dependabot, and (gated) required status checks / required PR with a GitHub App bypass for a CI auto-commit bot. Mutating and confirmation-gated: always assess first, apply the no-regret baseline, then decide required checks separately. Use when hardening a public user-owned repo after an audit, when a repo has no branch protection, when adding required checks without breaking a bot that pushes to the default branch, or when provisioning a GitHub App bypass actor for trusted automation.
日本語の概要は準備中です。原文の説明を表示しています。
Work with the full set of Maxwell's equations in integral and differential form to analyze electromagnetic fields, waves, and energy transport. Use when applying Gauss's law, Faraday's law, or the Ampere-Maxwell law to boundary value problems, deriving the electromagnetic wave equation, computing Poynting vector and radiation pressure, solving for fields at material interfaces, or connecting electrostatics and magnetostatics to the unified electromagnetic framework.
日本語の概要は準備中です。原文の説明を表示しています。
Design a GxP training programme covering training needs analysis by role, curriculum design (regulatory awareness, system-specific, data integrity), competency assessment criteria, training record retention, and retraining triggers for SOP revisions and incidents. Use when a new validated system requires user training before go-live, an audit finding cites inadequate training, organisational changes introduce new roles, a periodic programme review is due, or inspection preparation requires demonstrating training adequacy.
日本語の概要は準備中です。原文の説明を表示しています。
Create and manage pull requests using GitHub CLI. Covers branch preparation, writing PR titles and descriptions, creating PRs, handling review feedback, and merge/cleanup workflows. Use when proposing changes from a feature or fix branch for review, merging completed work into the main branch, requesting code review from collaborators, or documenting the purpose and scope of a set of changes.
日本語の概要は準備中です。原文の説明を表示しています。
Build sequential (stateful) logic circuits including latches, flip-flops, registers, counters, and finite state machines. Covers SR latch, D and JK flip-flops, binary/BCD/ring counters, and Mealy/Moore FSM design with clock signal and timing analysis. Use when a circuit must remember past inputs, count events, or implement a state-dependent control sequence.
日本語の概要は準備中です。原文の説明を表示しています。
Retrieve protein sequences, annotation, and structures from UniProtKB, the RCSB PDB, and AlphaFold DB. Use this skill to resolve a gene or protein name to a UniProt accession, pull sequences and FASTA files, find binding sites and domains, search the PDB by UniProt accession, sequence, ligand, or text, download mmCIF/PDB coordinates and biological assemblies, fetch AlphaFold models with their pLDDT confidence, and check whether a structure is actually usable before docking or simulating it. Also trigger on UniProt accessions, PDB ids, rest.uniprot.org, search.rcsb.org, files.rcsb.org, alphafold.ebi.ac.uk, id mapping, SEQRES, or missing residues.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze and engineer protein glycosylation. Scan sequences for canonical N-glycosylation sequons (N-X-S/T with X not proline, including overlapping sites), predict O-GalNAc hotspots, read glycan notation, and reach the curated external tooling (NetNGlyc, NetOGlyc, GlycoShield, GlycoWorkbench, GlyTouCan, GlyConnect). Use this skill for therapeutic antibody glycoengineering and afucosylation for ADCC, Fc glycan control, glycan shielding in vaccine immunogen design, sequon removal or insertion, and half-life engineering through sialylation. Also trigger on N-glycosylation, sequon, NXS/NXT, O-glycosylation, glycoform heterogeneity, afucosylation, high-mannose, GlyTouCan, or WURCS.
日本語の概要は準備中です。原文の説明を表示しています。
Build automated email flows that nurture, convert, and retain. Creates complete sequences for welcome, nurture, launch, re-engagement, and onboarding with subject lines, body copy, timing, and A/B test plans. Use when someone needs email automation, a drip campaign, welcome series, launch emails, post-purchase emails, abandoned cart recovery, or says 'email sequence', 'drip campaign', 'welcome series', 'onboarding emails', 'nurture flow', 'automated emails', 'email marketing', 'retention emails', or 'lifecycle emails'. Even if they just say 'set up emails' or 'email strategy' without specifying 'sequence', this is likely the right skill. Includes deliverability rules and spam avoidance.
日本語の概要は準備中です。原文の説明を表示しています。
GitHubでpull requestを作り、文章を書く時の心得。PRのタイトルと概要欄の書き方、リンクが壊れない書き方、親子PRの組み方、squash and mergeのcommit messageの書き方を定める。 pull requestを作成・更新・mergeする時、GitHubに載る文章を書く時に読み込む。
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
日本語の概要は準備中です。原文の説明を表示しています。