4,070 件 ・ 関連度順
概要と使いどころ
Pre-implementation red-team analysis. Use when a plan is high-risk, critical path, or expensive to reverse. Challenges plans before code is written — finds edge cases, security holes, scalability bottlenecks, error propagation risks, and integration conflicts. Catches flaws at plan time (10x cheaper than post-implementation).
日本語の概要は準備中です。原文の説明を表示しています。
Fetch Bilibili (哔哩哔哩) video comments for UP主 self-analysis. Use when the user asks to collect, download, export, or analyze comments on a Bilibili video (BV号 / URL / UID). Produces JSONL + summary.json suitable for further Claude Code analysis (sentiment, keywords, audience trends). Read-only; does not post/edit/delete.
日本語の概要は準備中です。原文の説明を表示しています。
Authoritative reference and rules for developing for Obsidian — building TypeScript plugins (Plugin lifecycle, manifest.json, commands, settings, modals, views, ribbon/status bar), the Vault and Editor APIs, the event system, Markdown post-processing & code-block processors, CodeMirror 6 editor extensions, building CSS themes (CSS variables, theme.css/manifest), and submitting plugins/themes to the community directory. Use whenever the user asks to build, debug, or review an Obsidian plugin or theme, work with the Obsidian API (Vault/Editor/Workspace/Plugin), register commands/views/events, process Markdown, or release/submit to the Obsidian community.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever the user mentions Zenodo, depositing or publishing research artifacts (datasets, software, papers, posters) to Zenodo, minting a DOI for a dataset/code release, uploading files to a Zenodo record, creating a new version of a Zenodo deposit, or searching Zenodo records. Covers the full Zenodo REST API workflow — create deposition, upload files via the bucket API, set metadata, publish, version, and search — for both production (zenodo.org) and sandbox (sandbox.zenodo.org).
日本語の概要は準備中です。原文の説明を表示しています。
Craft Cloud — Pixel & Tonic's serverless hosting platform for Craft CMS. Covers craft-cloud.yaml configuration, the Build → Migrate → Release deploy pipeline, the craftcms/cloud extension package, edge image transforms via Cloudflare, edge static caching with cache.rules + ESI, Cloud-managed S3 filesystem, MySQL 8 / Postgres 15 databases (no MariaDB, no tablePrefix), Console-based command runner and scheduled cron (once-per-hour minimum), auto-handled queue jobs, custom domains and SSL, preview environments per branch, Cloud limitations (ephemeral filesystem, no SSH, no .htaccess, no built-in mail), plugin development requirements for Cloud compatibility, and self-hosted → Cloud migration.
日本語の概要は準備中です。原文の説明を表示しています。
It's 11pm before your launch. Your PH page is ready but you have no idea what actually moves the ranking algorithm. Upvotes? Comments? Time-of-day? This is the hour-by-hour operations manual from someone who's coached 30+ #1 finishes. What's inside: • Ranking algorithm deep-dive (it's not just upvotes — weighted factors decoded) • Launch day minute-by-minute checklist (PST timing, first 3 hours are critical) • Voter mobilization strategies (ethical, anti-spam-safe approaches) • Asset preparation templates (gallery, tagline ≤60 chars, maker comments) • Post-launch 72h momentum plan (convert PH traffic → retained users) Built from: 30+ PH #1 daily wins, 10+ weekly top 3, 2 monthly top 5. 3,000-5,000+ upvotes per launch. Triggers: "Product Hunt" | "PH launch" | "Product Hunt #1" | "PH ranking" | "Product Hunt strategy" | "PH upvotes" | "launch day" | "PH打榜" | "Product Hunt攻略" | "PH ranking algorithm"
日本語の概要は準備中です。原文の説明を表示しています。
Startup Launch Day Playbook — Hour-by-hour execution checklist for your big launch day. Covers timezone timing, channel sequencing, real-time crisis management, and post-launch momentum. By @WeiYipei.
日本語の概要は準備中です。原文の説明を表示しています。
Gingiris growth toolkit 主入口。当用户问"怎么做增长"、"怎么发 PH"、"SEO 掉了"、"写篇博客"、"分析对手"等出海增长问题时调用。 根据问题类型自动路由到对应子 skill（gr-seo-patrol / gr-blog-post / gr-ph-launch 等）。
日本語の概要は準備中です。原文の説明を表示しています。
Gingiris growth toolkit 主入口。当用户问"怎么做增长"、"怎么发 PH"、"SEO 掉了"、"写篇博客"、"分析对手"等出海增长问题时调用。 根据问题类型自动路由到对应子 skill（gr-seo-patrol / gr-blog-post / gr-ph-launch 等）。
日本語の概要は準備中です。原文の説明を表示しています。
SEO/GEO Agent Operations SOP v2 — Rebuilt from real-world operations (analook.com 0→launch, GSC incident, DataForSEO monitoring, gingiris.tools post-migration recovery). What's new in v2: • Step-by-step onboarding (Q1→Q6), multiple choice wherever possible — no big forms • Mandatory daily SEO log — first item is always GSC token status check • Data cross-validation rule: any external metric must come from ≥2 sources before use • Backlink progress tracking (6-week wait → check → alert if not indexed) • New vs. established site strategy matrix (new site <6mo: KD≤20; mature: KD up to 35+) Real incidents baked in: GSC token expired silently for 2 weeks (analook.com), P0 keywords dropped out of Top 100 after domain migration (gingiris.tools), traffic data off by 17× from single-source DataForSEO. Triggers: "SEO agent" | "SEO daily report" | "GSC monitoring" | "DataForSEO" | "GEO agent" | "backlink tracking" | "IndexNow" | "competitor comparison page" | "SEO SOP" | "autonomous SEO" | "GEO triple combo" 🇨🇳 SEO/GEO Agent 运营 SOP v2 — 基于真实运营经验重写（analook.com 从零建站 + GSC 断档 2 周 + DataForSEO 监控 + gingiris.tools 迁移权重恢复）。 对话式开局、强制日报（GSC token 是第一项）、数据交叉验证铁律、外链进度追踪、新老站区分策略。
日本語の概要は準備中です。原文の説明を表示しています。
Reconstruct an open-source project's growth channels, key content, and stage-by-stage attribution from GitHub history and public web evidence. Use this skill when asked to research GitHub star growth, identify launch and amplification channels, explain viral milestones, find representative posts or videos, compare Product Hunt/Show HN/Reddit/KOL impact, or produce an evidence-backed OSS growth attribution report.
日本語の概要は準備中です。原文の説明を表示しています。
Product Hunt 发布剧本。从 30x 日冠经验提炼的完整 GTM 流程：T-14 预热 → T-0 发布日 → T+7 post-launch。 覆盖 hunter 选择、maker comment、community seeding、评论节奏、防踩雷。当用户说"我要发 PH"、 "Product Hunt 准备"、"找 hunter"、"写 maker comment"时调用。
日本語の概要は準備中です。原文の説明を表示しています。
Jekyll 博客发布流水线：按 Iris 文风（时间锚定开场、括号旁白、em-dash 转折、Key Stats 表格）生成文章， 附带 frontmatter（title / date / canonical_url / hreflang_ja / hreflang_ko / FAQ schema）、 多语言同步（en/ja/ko）、自动建内链。当用户说"写一篇博客"、"发新文章"、"同步日韩版本"时调用。 默认 dev/B2B 读者；2C 教育/医疗/金融（YMYL）内容的 E-E-A-T 与分发渠道不同，见 gingiris-seo-geo/references/2c-adaptation.md。
日本語の概要は準備中です。原文の説明を表示しています。
The complete first-timer's guide to launching on Product Hunt. Covers timing, hunter selection, asset prep, launch-day engagement, and post-launch follow-up. Follow @WeiYipei on X for more launch strategies.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews sqlx database code for compile-time query checking, connection pool management, migration patterns, and PostgreSQL-specific usage. Use when reviewing Rust code that uses sqlx, database queries, connection pools, or migrations. Covers offline mode, type mapping, and transaction patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Kolu's project-wide default for filesystem monitoring is `@parcel/watcher`. Reach for this skill when adding or modifying any code that watches files or directories — recursive subtree watching, single-file observation, fs.watch alternatives, chokidar replacement, inotify/FSEvents/watchman backend selection, ignore globs, watcher debouncing, or refcounted shared subscriptions. Covers backend dispatch, the watchman invocation path, ignore handling, post-install reconciliation, and the failure modes Kolu's logger surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
日本語の概要は準備中です。原文の説明を表示しています。
Write essays, articles, and blog posts in Paul Graham's voice — plain, spoken prose that reasons out loud and lands surprising true claims, not AI filler. Use when asked to write or rewrite something "like Paul Graham", "in PG's style", or to make a piece read like a person thinking on the page rather than generated text. Built from a stylistic model of 18 of his essays (see SOURCES.md).
日本語の概要は準備中です。原文の説明を表示しています。
Semi-automated fact-checking, source credibility evaluation, misinformation detection, prebunking, and evidence-ledger based claim verification. Use when a user asks to verify a claim, article, social post, screenshot, URL, quote, data point, compare sources, detect manipulation, evaluate source reliability, or generate an HTML fact-check card/share-safe correction. Supports text, URLs, screenshots/images, two-source comparison, and topic-level prebunking in Bulgarian, English, Russian, EU policy, health, science, and geopolitical contexts. Trigger phrases: "is this true?", "is this fake?", "fact check this", "compare these sources", "проверка на факти", "истина ли е", "дезинформация ли е", "сравни тези източници".
日本語の概要は準備中です。原文の説明を表示しています。
E-Mail-Entwürfe auf die Merkmale prüfen, mit denen Spamfilter Werbepost erkennen, und empfangene Nachrichten auswerten, die im Junk gelandet sind. Nutze diesen Skill, wenn eine Mail vor dem Versand geprüft werden soll, wenn jemand wissen will, warum eine Nachricht im Spam- oder Junk-Ordner gelandet ist, oder wenn Betreff, Text, HTML und Kopfzeilen einer Mail auf Aufbau- und Inhaltsfehler durchgesehen werden. Prüft unter anderem Linktext gegen Linkziel, defekte Abmeldewege nach RFC 8058, erfundene Thread-Bezüge, sichtbare Seriendruckreste, versteckte Zählpixel, Domainstreuung sowie unbelegte Zahlen und Superlative. Sagt keine Zustellung voraus und ist kein Werkzeug, um Filter zu umgehen. Für die Frage, ob eine Kaltakquise-Mail überhaupt versendet werden darf, ist cold-email zuständig.
日本語の概要は準備中です。原文の説明を表示しています。
Organische Social-Media-Inhalte für Deutschland und den DACH-Raum planen, verfassen, wiederverwenden, prüfen und messen. Nutze diesen Skill, wenn Posts, Redaktionspläne, Content-Serien oder Kanalstrategien für LinkedIn, X, Instagram, TikTok, Facebook, YouTube oder Mastodon entstehen sollen, wenn vorhandene Inhalte für Social wiederverwendet werden, oder wenn ein Beitrag auf Werbekennzeichnung, Persönlichkeits- und Markenrechte, Alt-Texte und aktuelle Plattformregeln geprüft werden soll. Deckt Briefing, Evidenz, Formatwahl, Interaktion und Messung ab. Nicht für bezahlte Kampagnen und nicht für das tatsächliche Veröffentlichen.
日本語の概要は準備中です。原文の説明を表示しています。
Generate hook script from template. Use when adding a new hook, wiring a PreToolUse/PostToolUse/Stop/Notification hook, or scaffolding hook config for settings.json.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect and explain bmad-loop run artifacts under `.bmad-loop/runs/`. Use for live health checks ("is it stuck?", "is the loop alive?", "what is the agent doing?") and post-run forensics ("what happened?", "why did story X fail?", "where did the tokens go?"). Also triggers on "monitor/check/summarize the loop", "why did the run pause?", Vietnamese "theo dõi bmad loop", "phân tích run", "đọc log của run", and equivalent requests in other languages. Use only for bmad-loop's own run artifacts, not application runtime logs or CI-provider build logs.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose problems before solving them: turn "X is broken and we don't know why" into a precise problem statement, verified root causes, solutions traced to those causes, and a rollout plan. Use whenever the user reports something failing, breaking, slowing, or recurring without a known cause: "sales dropped and we don't know why", "this keeps happening", "why does X keep failing", "find the root cause", "run a post-mortem", "5 whys"; Vietnamese "sao cứ bị vậy hoài", "tìm nguyên nhân gốc", "X đang hỏng mà không rõ vì sao". Trigger even when the user asks for solutions directly: "give me ideas to fix falling sales" is a diagnosis request. Not for open-ended ideation when nothing is broken (brainstorm-coach), understanding user needs (design-thinking), or company-level strategic bets (strategy-board).
日本語の概要は準備中です。原文の説明を表示しています。