5,060 件 ・ 関連度順
概要と使いどころ
Use when the user explicitly asks to save, curate, or consolidate what was learned, or closes a meaningful knowledge-work session. Not for remote, publish, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when finding duplicate GitHub issues or checking for similar issues against a target issue. Not for closing, labeling, or modifying any duplicate issue.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a human asks to compare one closed or stale tracker issue with current reality and mark it done or update it. Don't use for bulk issue reconciliation or multi-issue sweeps.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a scheduled or watcher tick requests a repository-health pass. Not for source, label, merge, or close mutation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.
日本語の概要は準備中です。原文の説明を表示しています。
Apply one governed bounded Proto UI dependency update after pui-deps establishes the exact manifest, lockfile, consumers, compatibility evidence, and rollback boundary. Use for ordinary package or toolchain updates whose intended compatibility is already fixed. Route unresolved public compatibility, security disclosure, publication, release, or provenance exceptions to their dedicated decision path.
日本語の概要は準備中です。原文の説明を表示しています。
Independently attempt to falsify one Proto UI autonomous-maintenance finding in a fresh non-mutating context. Use after pui-observe produced a candidate finding and route the result directly to remediation or closure when authority is clear.
日本語の概要は準備中です。原文の説明を表示しています。
Route one eligible transition in Proto UI's governed autonomous-maintenance protocol. Use for maintenance missions, drift discovery, finding verification, accepted remediation, independent maintenance review, run-ledger closure, or residual-risk planning. Do not use for ordinary user-directed development.
日本語の概要は準備中です。原文の説明を表示しています。
Measure the active Agent model with pinned offline ModelTrace sampling and return an unsigned closed-set attribution record. Use before Agent-originated commits, Issue/PR creation or material updates, comments, reviews, and current collaboration writes in either execution mode. Do not treat a fingerprint, declared model label, or record reference as authenticated identity, permission, independent review, or acceptance.
日本語の概要は準備中です。原文の説明を表示しています。
Apply one exact-target Proto UI collaboration update through the ordinary governed primitive or an explicitly current-user connected-operation path for archive/ref recovery, Issue reopening/linking, additive carrier publication and service control. Do not manufacture review dispositions, merge, close, release or change privileged settings.
日本語の概要は準備中です。原文の説明を表示しています。
Archive completed plans and roadmap milestones. Moves finished plans to the archive directory and optionally trims closed milestones from ROADMAP.md. Use when user says "archive plans", "clean up plans", "archive completed", or "trim roadmap".
日本語の概要は準備中です。原文の説明を表示しています。
Design guide + benchmarked pitfalls for building Monte-Carlo / Simulated Annealing refinement layers on top of greedy hex-grid layouts for code visualization (packages/gui/src/store/hexLayout.ts, sandbox/hex-sandbox, future Rust ports). Use when: (1) planning to add MC/SA on top of an existing hex-grid pack, (2) deciding whether a simpler SA would match a hierarchical MC with force-directed + chain drag, (3) budgeting wall-clock for million-node cold-start, (4) debugging "blob turns Swiss-cheese" or "folders stop nucleating" during MC refinement, (5) choosing between folder cohesion and raw Σ-link-length as cost function. Contains four hard-won, quantified lessons and anti-patterns that would take a full day of experiments to rediscover.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and fix RFDB data disappearing after compaction, where rfdb-server reports a tiny node count (e.g. "15 nodes") on startup despite manifest_index.json showing hundreds of thousands of nodes and segment files existing on disk. Use when: (1) rfdb-server logs "Default database: N nodes" with N orders of magnitude smaller than recent analysis output, (2) /api/stats returns only the most recent commit's nodes, (3) the issue appears AFTER a compaction event (manifest with l1_node_segments populated and node_segments: []), (4) subsequent commits dropped L1 references. Root cause: ManifestStore::create_manifest() initializes l1_node_segments/l1_edge_segments to Vec::new() instead of cloning from current manifest, so any commit AFTER compaction silently orphans all L1 data even though segment .seg files still exist on disk. Compaction injects L1 fields explicitly after create_manifest, but regular commits do not.
日本語の概要は準備中です。原文の説明を表示しています。
Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.
日本語の概要は準備中です。原文の説明を表示しています。
Act as an interactive data analyst for ClickHouse-backed analytics. Use when the user asks questions about internal data, metrics, dashboards, telemetry, active users, revenue, funnels, trends, distributions, or wants an analyst-style conversation, ad hoc SQL, charts, or a data export against ClickHouse (local or ClickHouse Cloud).
日本語の概要は準備中です。原文の説明を表示しています。
Run an authorized task inside an Available Work Time (AWT) window with a shorter Closeout Grace Period (CGP), fixed deadlines, forecast checks, proportional convergence points, and a hard stop. Use when the user explicitly requests timeboxing, supplies an AWT/CGP pair, says AWT or CGP, or an applicable project policy requires the protocol. Do not invent durations or activate timeboxing merely because a task may take time.
日本語の概要は準備中です。原文の説明を表示しています。
Apply the Minimum Sufficient Language (MSL) principle through the MSL Kernel to write anything a reader must act on. Bind the reader and what they already know, partition facts from the machinery that produced them, emit each admitted fact as an action, a verification, a judgment, or a state, and stop when every claim is checkable and the reader can act. Use for status updates, work-in-progress reports to your own user, closeout and convergence comments, tickets, pull request and review write-ups, incident and postmortem notes, emails, memos, and any draft for readers outside the work. Also use when the user says MSL, Minimum Sufficient Language, write this for stakeholders, drop the jargon, make this readable, or asks for a paste-ready draft.
日本語の概要は準備中です。原文の説明を表示しています。
Execute governed implementation workflow with work items, RFC/ADR checks, phase gates, testing, and closure. Use when: (1) User invokes /gov, (2) A non-trivial change needs work item tracking, (3) Implementation may require RFC/ADR handling
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user has tabular data (pandas DataFrame, parquet, csv, Arrow, json) and wants to filter, group, aggregate, join, or speed up slow pandas. Provides chDB DataStore - same pandas API, ClickHouse engine underneath. Also handles reading from S3, MySQL, PostgreSQL, MongoDB, ClickHouse Cloud, Iceberg, Delta Lake as DataFrames and joining across sources. TRIGGER when: user mentions DataFrame, parquet, csv, "fast pandas", "speed up pandas", or cross-source DataFrame joins; user imports `chdb.datastore` or `from datastore import DataStore`. SKIP this skill for raw SQL syntax (use chdb-sql instead), ClickHouse server administration, or non-Python DataStore API work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to run SQL - especially analytical SQL - on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse Cloud, Iceberg, Delta Lake) without setting up a server. Provides chDB - embedded ClickHouse SQL in Python with 1000+ functions, Session for stateful multi-step pipelines, parametrized queries, and cross-source joins via `s3()`, `mysql()`, `postgresql()`, `iceberg()`, `deltaLake()`, `remoteSecure()` table functions. TRIGGER when: user wants SQL on parquet/csv/files or across remote analytical sources; uses ClickHouse SQL features (window functions, windowFunnel, geoToH3, JSON path ops, Session, parametrized queries); imports `chdb` or calls `chdb.query()`. SKIP this skill for pandas-style DataFrame method-chaining (use chdb-datastore instead) or ClickHouse server administration.
日本語の概要は準備中です。原文の説明を表示しています。
Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.
日本語の概要は準備中です。原文の説明を表示しています。
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
日本語の概要は準備中です。原文の説明を表示しています。
Act as an interactive data analyst for ClickHouse-backed analytics. Use when the user asks questions about internal data, metrics, dashboards, telemetry, active users, revenue, funnels, trends, distributions, or wants an analyst-style conversation, ad hoc SQL, charts, or a data export against ClickHouse (local or ClickHouse Cloud).
日本語の概要は準備中です。原文の説明を表示しています。
Archive completed plans and roadmap milestones. Moves finished plans to the archive directory and optionally trims closed milestones from ROADMAP.md. Use when user says "archive plans", "clean up plans", "archive completed", or "trim roadmap".
日本語の概要は準備中です。原文の説明を表示しています。