1,227 件 ・ 関連度順
概要と使いどころ
Use for analytical thinking, or when a question needs breaking down and evidence: "why did metric X drop?", "what drives this?", "break this down", "what data do we need?". Builds a tree, hypotheses and evidence, ends with an answer and key uncertainty. Skip for quick verdicts.
日本語の概要は準備中です。原文の説明を表示しています。
Use for the 5 Whys, or when the user wants the root cause of a failure: "why did this happen?", "this keeps breaking", "write the postmortem", "find the real cause". Asks why repeatedly with evidence at each step, then sets countermeasures. Skip for one-off typos or when the cause is already proven.
日本語の概要は準備中です。原文の説明を表示しています。
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
日本語の概要は準備中です。原文の説明を表示しています。
Builds the "Report Sources" child page for a finished Weekly Community Signal report — an evidence-backed defense of WHY every item landed in the column/section/rank it did. The agent argues each placement like a lawyer (claim → evidence → rule → rebuttal) but is under oath: it CANNOT invent, spin, or overstate — every claim ties to a verifiable fact (issue #, label, PR type, quoted comment, npm output, the front-door test). Not CYA — it's so Nathan can defend the report with facts and see the exact reasoning behind each call. Runs after the report (invoked by weekly-report, last steps) and on "report sources", "defend the report", "why is this here".
日本語の概要は準備中です。原文の説明を表示しています。
Scans CopilotKit's public product / pricing / Premium pages at the start of every weekly report to produce the authoritative list of COMMERCIAL surfaces (Premium · CopilotKit Enterprise · Intelligence Platform · paid tiers) and detect any newly-added or changed commercial feature since last week. This list defines what the report's 🏢 Enterprise section is about — CopilotKit's commercial/paid product, NOT "CopilotKit running inside an enterprise company." Emits the surface list + a free-vs-paid classifier the report uses to decide "does this issue hit a commercial surface?", plus a diff of what changed. Runs as a subagent (many web fetches) so the orchestrator's context stays small. Invoked by weekly-report (spawned at report start) and the enterprise skill; also triggers on "scan product surfaces", "what's premium", "commercial surfaces", "did we add a premium feature".
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level dark matter physics covering observational evidence, candidate particles, detection methods, structure formation, and alternative gravity theories.
日本語の概要は準備中です。原文の説明を表示しています。
Check GitHub Actions CI status for PRs and branches. Use when the user asks "did CI pass", "check status", "what failed", "are checks green", "PR checks", "CI status", "workflow status", "re-run jobs", or wants a quick summary of GitHub Actions runs for a PR or the current branch.
日本語の概要は準備中です。原文の説明を表示しています。
Stop. That last message did not land — re-pitch it.
日本語の概要は準備中です。原文の説明を表示しています。
Publish a proposal, offer, or pitch as a tracked link and report back whether it's getting read (view analytics after sending). Use when the user says "send the proposal", "did they open it", "track whether they read it", "share the offer". Not for recurring client reports (use client-reporter) or general research shares (use report-publisher).
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap or harden a project's operating model for mixed human and AI delivery teams. Use when starting a repository, adopting an agent harness, defining authority and risk tiers, coordinating parallel agents safely, binding evidence and review to an exact candidate, or correcting fragmented rules that prevent coherent, consistent, complete delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Use to audit a past architectural decision — did the chosen option hold up, what assumptions drifted, should the ADR be superseded? Backward review only; does not lock new choices.
日本語の概要は準備中です。原文の説明を表示しています。
Use when shaping a discovery slice — JTBD-framed interview guide, switch-event focus, verbatim quotes not summaries. Triggers on 'talk to users', 'why did they cancel', 'before we build X'.
日本語の概要は準備中です。原文の説明を表示しています。
Especialista em construir experiências 3D para a web - Three.js, React Three Fiber, Spline, WebGL e cenas 3D interativas. Cobre configuradores de produtos, portfólios 3D, websites imersivos e adição de profundidade às experiências web. Use quando: website 3D, three.js, WebGL, react three fiber, experiência 3D.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch transcripts from YouTube videos for summarization, analysis, or reference. Accepts video ID or full URL. No API key required. Triggers: YouTube transcript, video transcript, get subtitles, what did they say in the video, summarize YouTube, extract video text, caption from video.
日本語の概要は準備中です。原文の説明を表示しています。
[Research] Use when starting a web research task — discover, gather, and triage candidate sources on a topic to feed deeper investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Teach the user exactly ONE thing from the current session or project, in plain English, one or two short paragraphs. Use when the user types ;til or "til", asks "what did I learn", "explain one thing from this session", or at session close alongside other closing rituals. Also appropriate mid-session when a concept keeps recurring that the user clearly hasn't used themselves. One thing only — never a list, never a lecture.
日本語の概要は準備中です。原文の説明を表示しています。
Rewrite text that did not land, with clear context, plain language, and my writing preferences.
日本語の概要は準備中です。原文の説明を表示しています。
Stop. That last message did not land — re-pitch it.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working in the deepseek-harness repo to find non-obvious simplification candidates, write proposed Agent Notes or inline TODO/FIXME/XXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another PR; especially for dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-dependency-exists surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Evidence-grounded AI research workflow for turning supplied economics, finance, management, and social-science papers or structured records into versioned PaperReading artifacts. Use when Codex must ingest text, Markdown, or a text-based PDF; separate source-grounded claims from researcher analysis; bind findings to evidence IDs and locators; review extraction candidates; migrate v0.2 PaperRecord JSON; validate or verify a v0.3 PaperPackage; generate research extensions; export reviewable JSON or Markdown; or safely update a compatible 13-field literature workbook.
日本語の概要は準備中です。原文の説明を表示しています。
Compare model candidates using weighted metrics and deterministic ranking outputs. Use for benchmark leaderboards and model promotion decisions.
日本語の概要は準備中です。原文の説明を表示しています。
从配置的热点源（HN / Reddit / YouTube trending / B 站热门 / 等）抓今天的热门话题，去重 + 粗打分 + 写入 candidates.md。**绝大部分人没有候选池——这是让"我没素材"问题在 onboarding 第二步就消失的钥匙**。触发词："抓热点"/"fetch trends"/"今天有什么可做的"/"trending now"/"找选题"。
日本語の概要は準備中です。原文の説明を表示しています。
At the close of an epic (or a difficult issue), post a postmortem roundup comment — what went well, what was hard (backed by evidence), and 1–3 concrete proposals to improve the skills/flows — then offer to turn accepted proposals into their own `workflow`-labeled tasks, and end with a `🔭 Next` handoff (a paste-ready next-session prompt + the next epic to start). Use at epic close, after the "verify the whole thing" rollup, or when asked to "do a retro", "postmortem this epic", "what did we learn", "how do we improve the workflow".
日本語の概要は準備中です。原文の説明を表示しています。
System reference for the crouton layout engine (@fyit/crouton-layout) — the LayoutTree/layout_configs data model, the croutonLayoutBlocks registry and sizing contract, the viability metric, the deterministic placer (#709), and how layouts persist and seed. Use when reasoning about WHY a layout renders/composes/persists the way it does, when a question is shaped like "what is a LayoutTree / where do layouts live / why did the placer pick this arrangement / why won't this pane shrink / where does minWidth get read", or when a generated POC boots with the wrong (or no) default layout. Trigger phrases: "layout tree", "layout_configs", "viability check", "composeDefaultLayout", "block sizing contract", "why is my layout not viable". For authoring a block component, use the block-authoring skill instead.
日本語の概要は準備中です。原文の説明を表示しています。