1.1万 件 ・ 関連度順
概要と使いどころ
Default to Firefox for browser automation and decide when Chrome is truly required. Use before any task that needs a browser: fetching a page, grabbing cookies, headless runs, logging into a site. Includes a matrix of which tasks must stay on Chromium and why. Triggers: /firefox, /ff, via firefox, need a browser, headless browser, which browser to use, browser automation.
日本語の概要は準備中です。原文の説明を表示しています。
- Craft advanced search-engine queries and Google dorks to surface hidden files, documents and mentions. Use when building a Google dork, hunting a leaked document, or searching paste sites and document repositories for a name, email or selector
日本語の概要は準備中です。原文の説明を表示しています。
Sell layer: raise the framing of an artifact to the scale it actually deserves without touching a single number. Use before anything goes outbound (post, pitch, README, CV, PR comment, landing page, application, DM) or before showing a finished artifact. Triggers: /fake-it, /fi, sell it, make it louder, strengthen the frame.
日本語の概要は準備中です。原文の説明を表示しています。
Show what the background agents across every machine are doing right now, what they have built or committed, and whether anything is stuck or burning tokens. Read-only diagnostic. Triggers: "/fleet", "what are my agents doing", "is anything stuck".
日本語の概要は準備中です。原文の説明を表示しています。
Fan one deep-research prompt out to several external LLMs at once through a logged-in browser, then collect the reports, archive the originals and synthesize a consensus. Use at the final stage of a research protocol, instead of hand-pasting one prompt into N sites. Triggers: "/dr-fanout", "fan out the DR", "distribute the research prompt".
日本語の概要は準備中です。原文の説明を表示しています。
- Find internet-exposed hosts, ports, services and devices using third-party internet-scan data instead of touching the target. Use when asked what a company has exposed to the internet, to check open ports on an IP or netblock, or to write a Shodan filter query
日本語の概要は準備中です。原文の説明を表示しています。
Read the system-architect map: a deterministic catalog of everything the setup is made of (vault, import scripts, scheduled tasks, MCP servers, SQLite databases, hooks, skills, dashboards), what is healthy and what fell off. Consult it before changing shared infrastructure and re-scan after. Triggers: "/arch", "/arch broken", "/arch scan", "what broke in the system".
日本語の概要は準備中です。原文の説明を表示しています。
Decision protocol for strategic work: recall the knowledge vault, run a gap analysis, emit a deep-research prompt for external tools, then synthesize the returned reports into a decision memo. Use before any new product, feature, market, pricing, GTM or architecture call, where local recall alone is not enough. Triggers: "/alfa-search-recall-deepresearch", "alpha protocol", "R+DR".
日本語の概要は準備中です。原文の説明を表示しています。
Read-only measurement of an agent's autonomy debt from its approvals log: how many times it asked the human for permission in a window, how many asks expired unanswered, and which classes they fall into (machine noise, login or 2FA, physical UAC, money). Use to find asks the agent should have decided itself and to cut needless interruptions. Triggers: /ask-debt, autonomy debt, how often do I ask, expired asks.
日本語の概要は準備中です。原文の説明を表示しています。
Recover a session after a hard crash (app died, machine rebooted, context lost mid-work): replay the turn-state ledger for the last requests, files and decisions, run a green/red health ping over the system map, file sync and MCP connectors, then rebuild the previous session history for pickup. Triggers: "/1", "resume after crash", "wake".
日本語の概要は準備中です。原文の説明を表示しています。
ЧИП ТОЛЬКО ПО ПРЯМОМУ ЗАПРОСУ ЮЗЕРА (anton 14.08): сделать ЧИПЫ (spawn_task), которые юзер нажмёт сам.
日本語の概要は準備中です。原文の説明を表示しています。
Rewrite machine-written text so it reads like a busy human wrote it: cut 50-70%, break the even rhythm, drop AI-tell words and filler, keep facts and protected terms. Use before publishing any post, reply or email drafted by a model. Triggers: /ai-slop, /slop, humanize, anti-slop, make it shorter and alive.
日本語の概要は準備中です。原文の説明を表示しています。
Implement Feature-First architecture with Riverpod state management and Flutter Hooks in Flutter applications
日本語の概要は準備中です。原文の説明を表示しています。
Research any open-source repository end to end and answer the core question — SHOULD YOU contribute to it? — with a GO / NO-GO / GO-IF verdict backed by evidence: snapshot, momentum, contribution landscape (PR acceptance rates, outside-contributor merge rates, first-timer outcomes), issue health, governance, community sentiment, and a final go/no-go recommendation. Use when the user asks 'should I contribute to X', wants a before-I-contribute due-diligence check on a project, asks whether a project accepts outside PRs, wants contribution-health numbers like PR merge rates or stale-PR counts, or asks for a deep dive on an open-source codebase's health and dynamics before investing time in it.
日本語の概要は準備中です。原文の説明を表示しています。
Use when converting a design direction into maintainable production frontend code, selecting architecture within the existing stack, implementing semantics, assets, loading behavior, CSS/layout, components, and progressive enhancement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a web project needs business goals, audience, information architecture, conversion priorities, content hierarchy, constraints, or design CTQs clarified before visual design begins.
日本語の概要は準備中です。原文の説明を表示しています。
Simulate a Nature-style reviewer assessment from the referee perspective rather than an author rebuttal. Use when the user wants a pre-submission review, reviewer report, peer-review style critique, novelty/significance/technical soundness assessment, reviewer-style manuscript evaluation, 审稿人视角评估, 预审稿意见, or Nature reviewer report. Return 3 reviewer reports plus a cross-review synthesis, grounded only in the local Nature reviewer source basis. Also trigger on general pre-submission review requests during academic writing even without the word "Nature", such as getting a mock peer review for any journal, critiquing a draft as a reviewer would, assessing novelty/rigor before submission, and Chinese phrasings like 审稿人视角、模拟审稿、预审、帮我审一下论文、投稿前自审、审稿意见模拟、找论文问题.
日本語の概要は準備中です。原文の説明を表示しています。
Submission-grade remote-sensing Nature/high-impact journal figure workflow for Python or R. Use whenever the user asks to create, revise, audit, or polish manuscript figures, multi-panel scientific plots, map-led composites, remote-sensing image plates, sensor/product workflow figures, validation/error/uncertainty panels, or journal-ready SVG/PDF/TIFF outputs, especially for Nature-family, Remote Sensing of Environment, ISPRS, IEEE TGRS, or other high-impact venues. Before plotting, define the figure's conclusion, evidence logic, export needs, and review risks. If the user has not chosen Python or R, ask "Python or R?" and stop. Use only the selected backend for figure generation, previewing, exporting, and QA. Supports matplotlib/seaborn and ggplot2/patchwork/ComplexHeatmap. Not for dashboards or Illustrator/Figma-first infographics. Also trigger on general academic-writing figure needs even without the word "Nature", such as making figures/plots for a paper, scientific/academic plotting, data visualization for a manuscript, and Chinese phrasings like 遥感论文配图、学术写作配图、科研绘图、科研作图、地图出图、论文图表、可视化.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for the NV oOS Dictation desktop companion app (Tauri v2 + Rust, examples/nvoos-dictate) — build/run on Windows/MSVC, the local-first engine track (parakeet/whisper/moonshine/silero-vad, all API-verified against pinned crate versions), the embedded remote-STT fallback against the Embedded addon's transcribe route, model registry + verification harnesses, the plugins.updater boot-crash config rule, and the full test/clippy gate matrix. Use when building, extending, or debugging the dictation app, adding an engine or model, touching the cleanup pipeline golden tests, or continuing the P2/P4/P5/distribution follow-up work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
日本語の概要は準備中です。原文の説明を表示しています。
**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) - Debugging MCP server issues or errors - Reviewing MCP server code for quality, security, or performance - Answering questions about MCP development or mcp-use patterns - Making ANY changes to server.tool(), server.resource(), server.prompt(), or widgets This skill contains critical architecture decisions, security patterns, and common pitfalls. Always consult the relevant reference files BEFORE implementing MCP features.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user provides a GitHub URL and the planner needs to converge that repo plus the user's goal into a concrete project blueprint for later execution. This skill handles GitHub-input project intake, Phase 1 intent convergence, and downstream project handoff structure. It does not generate teaching material packages.
日本語の概要は準備中です。原文の説明を表示しています。
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Register a custom WooCommerce payment gateway — extend WC_Payment_Gateway, declare $id / $title / $supports, implement process_payment returning array(result, redirect), optionally process_refund when refunds is in supports, register via the woocommerce_payment_gateways filter. The single most-confused thing AI gets wrong is payment_complete vs update_status — payment_complete runs the canonical paid-order state machine (status, transaction id, session flag, woocommerce_payment_complete action), update_status only changes the status string. Includes the always-forgotten WC cart empty_cart call after success. Use when integrating a payment provider, reviewing gateway code, or debugging "payment succeeded but cart didn't clear" / "order stuck in pending". Triggers on WC_Payment_Gateway, woocommerce_payment_gateways, process_payment, process_refund, payment_complete, get_return_url, woocommerce_payment_complete_order_status.
日本語の概要は準備中です。原文の説明を表示しています。