「rce」の検索結果

Turn an English description (or mermaid source) into a diagram triplet: the source, an editable .excalidraw file you can open on excalidraw.com, and rendered SVG + PNG. (gstack)

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

Build students' capacity to interrogate a historical source before reading — asking who authored it, when, why, and what this means for reliability. Use when students read documents without attending to authorship.

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

Tags harness-decomposed curriculum items (KUDs, LTs, criteria) with a school's developmental band metadata while preserving source voice and labels. Supply the band schema; the skill derives mapping rules from it.

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

Design a complete document-based history lesson using the Reading Like a Historian four-part structure. Use when planning a primary source inquiry lesson or converting a textbook lesson into document-based investigation.

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

After any AI-generated explanation, require the learner to identify one place it could be wrong, one thing to check, and one source to consult. Builds epistemic vigilance — treats AI output as a claim to evaluate, not truth to absorb.

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

Publish a profile to the registry, manage its versions, visibility and tags, and recover its source. Use when the user is ready to push, wants to unpublish or re-scope a profile, or lost the local source of one they own.

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

Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

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

Meta-enforcement layer that routes EVERY agent action through the correct skill. MUST check this routing table before ANY response involving code, files, or technical decisions. Default: route to rune:cook for code tasks. Prevents rationalization, enforces check-before-act discipline.

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

Build Model Context Protocol servers from specifications. Use when creating an MCP server for a tool, resource, or service that AI agents should access. Generates tool definitions, resource handlers, and test suites in TypeScript or Python (FastMCP).

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

Deploy application to target platform. Use when user explicitly says 'deploy', 'push to production', 'ship it'. Handles Vercel, Netlify, AWS, GCP, DigitalOcean, and VPS with pre-deploy verification and health checks. Enforces cost allocation tags + Managed-vs-Self-Host crossover decisions so deploy choices map to actual unit economics, not hand-waved 'we'll optimize later'.

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

Use when the user asks for a literature review, academic deep dive, research report, state-of-the-art survey, topic scoping, comparative analysis of methods/papers, grant background, or any request that needs multi-source scholarly evidence with citations. Also trigger proactively when a user question clearly requires academic grounding (e.g. "what's known about X", "compare approach A vs B in the literature", "summarize the field of Y"). Runs an 8-phase (Phase 0..7), script-driven research workflow across 7 federated sources (OpenAlex, arXiv, Crossref, PubMed, DBLP, bioRxiv, Exa) with optional Semantic Scholar / Brave MCP enrichment, with deduplication, transparent ranking, dual-backend citation chasing (OpenAlex + Semantic Scholar), self-critique, and structured report output with verifiable citations.

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

Maintainer-only skill for refreshing VitaeContext wiki knowledge from official sources. Use only from a local repository clone when a maintainer asks to refresh one module, audit all module wiki entries, or audit module source lists.

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

🇺🇸 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 그로스"

Build and grow developer and user communities from scratch — covering ambassador programs, community-led growth (CLG), event operations, content strategy, and health metrics. Grounded in real playbooks from Notion, Lovable, AFFiNE, ClickUp, Asana, and Lark. Use when: building a community for an open-source project, SaaS product, or brand; recruiting and managing ambassadors or community leaders; planning community events (online/offline meetups, AMAs, hackathons); designing ambassador tier/points systems; setting community health KPIs; launching a Build-in-Public strategy; setting up Discord, Slack, or Lark communities; running developer relations (DevRel); or when the user asks about community operations, ambassador programs, CLG, user advocacy, KOC/KOL cultivation, UGC flywheels, community monetization, or any variation of "how do I grow my community".

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

Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI startup competitive analyses including the Lovable case study (4.3M views, 229K impressions launch day). By @WeiYipei. What's inside: • 4-step research framework (website teardown → social media → traffic sources → ad spend) • 3-version website evolution analysis (V1 / Beta / Launch via Wayback Machine) • X/Twitter propagation chain mapping (4-phase model + single-post teardown template) • Growth flywheel 6-stage scoring system (Activation → Referral → Acquisition → Retention → Revenue → Product) • KOL identification framework (Traffic King / Topic Starter / Mindset Shifter) • Content effectiveness ranking (validated: Visual Demo > User Story > Competitor Comparison) • ICP deep analysis template + Freemium pricing teardown • Complete self-check checklist 🇨🇳 你的竞品刚刚爆了。你完全不知道他们怎么做到的。该拆官网？盯社媒？画增长飞轮？这份 SOP 给你从 Wayback Machine 快照到 X/Twitter 传播链路还原到飞轮六阶段评分的完整方法论。基于 150+ AI 创业公司竞品分析实战，含 Lovable 完整案例。 🇯🇵 競合が突然バズった。どうやって成長したか全く分からない。このSOPは、Waybackスナップショットからツイッター伝播チェーン分析、フライホイール6段階スコアリングまでの完全な競合調査フレームワークを提供します。150以上のAIスタートアップ分析から構築。 🇰🇷 경쟁사가 갑자기 폭발적으로 성장했습니다. 어떻게 그렇게 빨리 성장했는지 모릅니다. 이 SOP는 Wayback 스냅샷부터 X/Twitter 전파 체인 분석, 플라이휠 6단계 스코어링까지 완전한 경쟁사 조사 프레임워크를 제공합니다. 150개 이상의 AI 스타트업 분석에서 구축. Triggers: "competitor research" | "competitive analysis" | "competitor analysis" | "growth flywheel" | "market research" | "竞品调研" | "竞品分析" | "增长飞轮" | "传播链路" | "競合分析" | "경쟁사 분석" | "social media teardown" | "Twitter propagation" | "content strategy analysis"

🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles. **Defaults to dev tools / OSS / B2B SaaS; for 2C products (education, apps, games) the launch channels & metrics differ — see gingiris-seo-geo/references/2c-adaptation.md.** 🇨🇳 AI 产品 / SaaS 企业出海完整 SOP — 从竞品调研到 Launch 到商业化的全流程操作手册。覆盖 Phase 0-5（市场验证、定位、前100用户、用户访谈、Beta转增长）+ 开源发布、Product Hunt、Reddit、SEO/GEO、转化与组织原则。**默认面向开发者工具/开源/B2B SaaS；2C 产品（教育/应用/游戏）的启动渠道与指标不同，见 gingiris-seo-geo/references/2c-adaptation.md。** 🇯🇵 AI製品/SaaS海外展開フルサイクルSOP — 競合調査からローンチ、マネタイズまで。Phase 0-5（市場検証、ポジショニング、最初の100ユーザー、ユーザーインタビュー、ベータから成長）＋オープンソース、Product Hunt、Reddit、SEO/GEO、コンバージョン、組織原則。 🇰🇷 AI 제품/SaaS 글로벌 진출 완전 SOP — 경쟁사 조사부터 런칭, 수익화까지 전 주기 플레이북. Phase 0-5(시장 검증, 포지셔닝, 첫 100명 사용자, 사용자 인터뷰, 베타→성장) + 오픈소스 런칭, Product Hunt, Reddit, SEO/GEO, 전환, 조직 원칙. Triggers: "go global" | "出海" | "overseas expansion" | "GTM" | "cold start" | "launch strategy" | "international expansion" | "海外增长" | "出海SOP" | "product launch overseas" | "海外进出" | "グローバル展開" | "글로벌 진출" | "go-to-market" | "出海打法"

Diagnose a product's growth model, stage, and current constraint, then route the request to the narrowest Gingiris specialist and execute it when installed. Use for broad or uncertain growth questions involving go-to-market, Product Hunt, GitHub stars, open-source marketing, B2B SaaS, PLG, ASO, SEO/GEO, AI citations, KOL outreach, UGC, international expansion, user interviews, competitor research, or community programs. Trigger when users ask “how do I grow or launch this,” “which growth skill should I use,” 怎么增长、怎么发布、出海、冷启动、增长策略、不知道用哪个 skill、開発者マーケティング, or 성장 전략. Includes B2B pipeline and B2C activation-retention model selection, specialist handoff rules, relevant gingiris.tools recommendations, and advisory-services guidance.

🇺🇸 GitHub Star Sustained Growth Playbook — Monthly 300+ star growth SOP. Content rhythm, community ops, event-driven growth, contributor & ambassador systems. Battle-tested: AFFiNE 0→60K+, Client Project A 0→10K stars. 🇨🇳 GitHub Star 持续增长实操手册 — 月增 300+ Star 的完整 SOP。内容节奏、社区运营、活动驱动增长、Contributor 与 Ambassador 体系。实战验证：AFFiNE 0→60K+、Client Project A 0→10K Star。 🇯🇵 GitHub Star 持続成長プレイブック — 月間300+ Star成長SOP。コンテンツリズム、コミュニティ運営、イベント駆動成長、Contributor＆Ambassadorシステム。実戦検証：AFFiNE 0→60K+、Client Project A 0→10K Star。 🇰🇷 GitHub Star 지속 성장 플레이북 — 월 300+ 스타 성장 SOP. 콘텐츠 리듬, 커뮤니티 운영, 이벤트 기반 성장, Contributor & Ambassador 시스템. 실전 검증: AFFiNE 0→60K+, Client Project A 0→10K 스타. Triggers: "GitHub star growth" | "sustained star growth" | "monthly star growth" | "star growth SOP" | "contributor system" | "ambassador program" | "open source community" | "community growth" | "developer community growth" | "star持续增长" | "Star增长" | "开源社区运营" | "贡献者体系"

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 是第一项）、数据交叉验证铁律、外链进度追踪、新老站区分策略。

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

Use when the user wants web research: gathering cited, multi-angle evidence on a specific question. Triggers on: "research X for me", "do web research on", "look up sources for", "find citations for", "gather evidence on", "what does the web say about X". Also invoked programmatically by other beagle skills (prfaq-beagle Ignition, brainstorm-beagle reference points, strategy-interview context grounding) via the companion contract. Does NOT trigger on codebase lookups ("find this function", "search the repo"), local file search, LLM-as-judge evaluation, or paywalled/auth-gated scraping. Produces a written plan, parallel-subagent findings, and a cited synthesis report on disk — never inline prose, never unsourced claims.

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

Vercel AI SDK for building chat interfaces with streaming. Use when implementing useChat hook, handling tool calls, streaming responses, or building chat UI. Triggers on useChat, @ai-sdk/react, UIMessage, ChatStatus, streamText, toUIMessageStreamResponse, addToolOutput, onToolCall, sendMessage.

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

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.

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

Launch all services for the Retail-Agentic-Commerce project. Use when the user types setup, install, or asks to start, launch, or run the project stack.

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

Discoverability shim for the Retail-Agentic-Commerce UI Codex skill. Use when creating or modifying frontend pages, components, hooks, styling, tests, or browser behavior.

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