5,226 件 ・ 関連度順
概要と使いどころ
Create and manage tickets — initiatives, epics, stories, bugs. Use when the user says "create a new initiative", "slice this initiative", "split this epic up", "break this into stories", "incept this epic", "make a ticket", "refine this ticket", "what's ready", "status of a story", "publish ticket changes", "validate these tickets", "set up the ticket store".
日本語の概要は準備中です。原文の説明を表示しています。
Use test-driven development for behavior-changing feature or fix work, and whenever the user mentions TDD, test-first, red-green-refactor, tracer bullets, integration tests, or public-interface behavior tests. Skip for docs-only, path-only rename, formatting-only, or purely mechanical chores unless explicitly requested.
日本語の概要は準備中です。原文の説明を表示しています。
Establish project context - foundation for all design work
日本語の概要は準備中です。原文の説明を表示しています。
LinkedIn-native long-form article and newsletter writing workflow for LinkedIn and Google-to-LinkedIn topic discovery, business-depth research, professional thought leadership, evidence-led drafting, final humanization, discussion design, SEO settings, auditing, and publish-ready packaging. Use when creating, outlining, researching, enriching, rewriting, humanizing, auditing, or packaging LinkedIn Articles, LinkedIn newsletters, LinkedIn long-form posts, LinkedIn thought leadership, LinkedIn B2B articles, LinkedIn 长文, LinkedIn 专栏, LinkedIn 话题调研, LinkedIn 商务内容, 去 AI 化编辑, or LinkedIn 发布包.
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
日本語の概要は準備中です。原文の説明を表示しています。
Author and run a durable AI chat agent with chat.agent from @trigger.dev/sdk/ai: the per-turn run loop, why you MUST spread ...chat.toStreamTextOptions() first, returning a StreamTextResult vs calling chat.pipe(), the two server actions (chat.createStartSessionAction + auth.createPublicToken), and wiring useChat to useTriggerChatTransport. Load this when building, modifying, or debugging a chat backend (the agent task or its lifecycle hooks) or its React transport, when declaring typed tools or custom data parts, or when migrating a plain AI SDK streamText route to chat.agent.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Muted Zine Poster v0.1 poetic paper-poster prompts and the matching generated image. Use when the user gives a theme, sentence, object, mood, article idea, photo, or content brief and wants a quiet Japanese/Korean zine-like editorial poster with large negative space, aged paper texture, experimental typography, and a restrained muted palette without high-chroma color blocks. This is the low-saturation sibling of gc-minimal-zine-poster-v0-1.
日本語の概要は準備中です。原文の説明を表示しています。
Universal context persistence across sessions. Auto-saves decisions, conventions, and progress to .rune/ files. Loads state at session start. Use when any skill makes architectural decisions or establishes patterns that must survive session boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Use when receiving external input that needs structured intake before action — PR review feedback, code review comments, OR issue tracker items (bug reports, feature requests). PR Review Mode (default) verifies suggestions before implementing. Issue Triage Mode classifies issues into a state machine (ready-for-agent / ready-for-human / needs-info / wontfix) and emits AGENT-BRIEFs for AFK execution. Prevents blind implementation, enforces verification-first discipline.
日本語の概要は準備中です。原文の説明を表示しています。
Audit designs against 19 rules across Figma files and code (HTML/CSS/React/Vue/Tailwind). Auto-detects framework and design system (MUI, Chakra, shadcn/ui, Ant Design, Radix, Bootstrap). Runs code superpowers across all 19 categories: aria, focus, contrast, tokens, responsive, motion, forms, navigation, spacing, states, microcopy, elevation, iconography/SVG. Flags color blindness risk. Audits dark patterns, ethical design, Nielsen's heuristics. Outputs before/after diffs, developer handoff reports, wireframe-to-spec. English and Korean. Triggers on: check my design, review my UI, audit my layout, is this accessible, design review, color contrast, WCAG, a11y, pixel perfect, Figma audit, CSS check, dark patterns, is this GDPR compliant, is this manipulative, is my form accessible, is my dark mode correct, wireframe to spec, heuristic review, Nielsen audit, usability heuristics, 디자인 검토, 접근성 확인, 색상 대비, 다크 패턴, 와이어프레임 스펙.
日本語の概要は準備中です。原文の説明を表示しています。
Run before writing or changing code for any feature, bug fix or refactor that touches data, jobs, money, outside services or user-facing behaviour. Finds where the change will break before it is built, by walking ten named failure classes (twice, halfway, outside call, failure-is-not-empty, neighbors, endings, money, hostile user, words, scale and time) against the code, and writes the answers into the plan. Use when planning a change, when asked to "think it through", "cover the gaps", "make sure it's bug free", or before any edit to payment, publishing, deletion, auth or background-job code.
日本語の概要は準備中です。原文の説明を表示しています。
Developer reference for building applications, tools, and agents on the Pi Durable agent harness (@earendil-works/pi-durable) and the pi-ai model layer. Use when writing or debugging code that imports @earendil-works/pi-durable or pi-ai: assembling a Harness over memory/SQLite/JSONL/Durable Object storage, submitting input and waiting for answers, defining tools with TypeBox schemas and structured output, calling tools from tools, hooks and guards, durable tasks with checkpoints and ownership, subagents and child tasks, documents and migrations, code mode, tool search, per-conversation environments, compaction, recovery after a crash, storage and environment conformance tests, or choosing models and providers. Also use when a durable/agent-runtime behavior question comes up: what survives a restart, why an input stayed queued, why a task is blocked or orphaned, how abort cascades, or what the Pico5 specification requires.
日本語の概要は準備中です。原文の説明を表示しています。
Use when looking up journal impact factors (JCR IF), checking a journal's impact factor by name, comparing IF across journals, or answering questions about "影响因子" / "impact factor" / "IF". Triggers on "impact factor", "journal IF", "影响因子", "JCR", "IF score", "journal rank", "which journal has higher IF", "what is the IF of". PROACTIVELY USE when user mentions journal prestige, publication venue quality, or manuscript submission target evaluation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants full metadata for a paper — from a DOI, PMID, arXiv id, OpenAlex id, or title. Returns title, author list, first author, corresponding author(s), publication date, journal name + ISO-4 abbreviation, impact factor, volume/issue/pages, DOI/PMID, citation count, and abstract in one record. Triggers on "paper metadata", "who is the corresponding author", "first author of", "what journal / impact factor for this DOI/PMID", "cite this paper", "文献元数据", "通讯作者", "第一作者", "影响因子". PROACTIVELY USE when the user pastes a DOI/PMID/arXiv id or paper title and asks about its authors, venue, or impact.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever the user wants to obtain, download, or fetch a paper's PDF — given a DOI, an arXiv id, a paper title, a citation, or a list of DOIs. Trigger on phrases like "download this paper", "find the PDF for [DOI]", "grab me the [Nature/bioRxiv/arXiv] paper on X", "get the open-access version", "I need this article", or any bulk/batch paper download request, even when the user doesn't explicitly say "PDF" or "DOI". Resolves via Unpaywall → Semantic Scholar → arXiv → PubMed Central → bioRxiv/medRxiv → publisher direct (institutional opt-in) → Sci-Hub mirrors as last-resort fallback.
日本語の概要は準備中です。原文の説明を表示しています。
Query the Semantic Scholar academic corpus through AI2's Asta MCP server: keyword or title search with venue and date filters, who-cited-a-paper traversal, author profiles and publications, DOI/arXiv/PMID lookup, and ~500-word full-text snippets for evidence, with citation counts and h-index. Use when the user asks for papers on a topic, who cited a paper, an author's work, recent literature since a date, or a venue-scoped paper list. Requires the Asta MCP server.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch and export public X (Twitter) data with a self-contained Python CLI (twikit; no API keys, uses the user's own login cookies): profiles, a user's tweets/replies/likes, threads, search, followers, timelines, JSON/JSONL/CSV/SQLite output, resumable pagination. Use to scrape, archive, monitor, or analyze tweets or accounts.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 是第一项）、数据交叉验证铁律、外链进度追踪、新老站区分策略。
日本語の概要は準備中です。原文の説明を表示しています。
Twitter/X Agent Operations SOP v2 — Rebuilt from real dual-account operations. Real data: • CN account: grew from 1,150 → 3,679 followers (~14 months), 1 tweet/day, OAuth1 direct post • EN account: Buffer API • Real incidents: cron silent-failed for 2 weeks unnoticed, analytics data off by 17×, thread performance worse than single posts What's new in v2: • Step-by-step onboarding (Q1→Q6), multiple choice wherever possible — no big forms • Mandatory daily log after every tweet + weekly report every Monday • Pre-publish safety checklist (agent must pass before posting) • Content pool tracker (used/unused) + alert when ≤3 items remain • Dual-account credential separation (CN: OAuth1 / EN: Buffer API) • MASTER-STATUS.md as the single source of truth — read + write every session 🇨🇳 Twitter/X Agent 运营 SOP v2 — 基于真实双账号运营经验重写。 开局对话式收集 context、强制日报+周报、发推前红线自检、素材库追踪、双账号凭证分离、MASTER-STATUS.md 单一真相来源。 真实数据：中文账号从 1,150 粉增长至 3,679 粉（约14个月），1条/天。 Triggers: "twitter运营" | "推特agent" | "发推SOP" | "AI代运营" | "推文日报" | "素材库" | "Buffer API" | "OAuth1发推" | "twitter automation" | "tweet sop" | "推特涨粉"
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Generate an /insights-style HTML report across MANY of your agent coding sessions (Claude Code and OpenAI Codex): what you work on, how you use the agent, your wins, your friction points, and concrete fixes to become more effective — precise goal-setting, not trusting output blindly, scoping, context hygiene, right-sizing models. Reads local session history and writes one self-contained report.html. Use when the user asks to "разбери мои сессии", "оцени как я работаю с агентом", "мой insights", "session insights report", "review how I work", "на что обратить внимание", or runs "/mentor", "/mentor claude", "/mentor codex", "/mentor both". Do NOT use for reviewing the CODE produced (that's code-review) or building the agent.
日本語の概要は準備中です。原文の説明を表示しています。
Servd (servd.host) — Craft-specialised managed hosting for Craft CMS. Covers git push-to-deploy with the optional servd.yaml build config, local → staging → production environments with uni-directional Project Config sync, the servd/craft-asset-storage plugin (S3-backed Flysystem volumes on the svdcdn.com CDN, off-server image transforms, Imager-X/ImageOptimize integrations), Servd's static caching (full vs tag-based purge, {% dynamicInclude %}, CSRF injection, cache-busting) and running Blitz alongside it in reverse-proxy mode, MariaDB/MySQL databases over an SSH tunnel, automatic + manual backups, the Dedicated Queue Runner, environment variables and secrets, the ephemeral load-balanced filesystem (Redis + remote volumes for runtime files), plugin/feature constraints, and Servd-vs-Craft-Cloud differences.
日本語の概要は準備中です。原文の説明を表示しています。
Cut a kolu release — tag master, promote the Unreleased changelog entry, publish a GitHub release. ONLY invoke when the user explicitly types `/release` or `$release`; never auto-select from a natural-language request.
日本語の概要は準備中です。原文の説明を表示しています。