4,281 件 ・ 関連度順
概要と使いどころ
Form and maintain execution strategy when order, effort, evidence timing or recovery materially affects the outcome, even with a settled goal. Reuse durable task records when continuity needs them; keep clear work direct.
日本語の概要は準備中です。原文の説明を表示しています。
Use for hands-on repository work when a quiet, risk-scaled engineering method can improve design, execution strategy, implementation, material incorporation, debugging, review, delegation, workspace lifecycle, or verification. Keep clear local changes direct, preserve the complete requested outcome, and add method only where risk or uncertainty justifies it. Do not use for general technical explanations, simple file lookup, casual discussion, or non-engineering writing.
日本語の概要は準備中です。原文の説明を表示しています。
Design, run, and review fair performance, token, and cost comparisons across GitHub Copilot CLI, Codex CLI, and direct model APIs. Use for AI CLI benchmark, Copilot vs Codex, prompt-cache diagnosis, cache read/write analysis, fresh-process latency measurement, token-cost comparison, or when a benchmark must separate provider caching from local CLI caches.
日本語の概要は準備中です。原文の説明を表示しています。
Route Microsoft Graph work from VS Code. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, audit, and post-process PFC 5.0 asphalt calibration tests, including compression, diametral loading, direct tension, creep-recovery, test geometry, histories, peak metrics, stiffness, and fistPkg handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Design and audit PFC 5.0 asphalt dynamic loading and stress-wave studies with damping, timestep, rate, dispersion, source direction, boundary reflection, histories, and wheel-load handoff checks.
日本語の概要は準備中です。原文の説明を表示しています。
Writes expert academic paper summaries for social science research, particularly political science and applied statistics. Use when asked to summarize, review, or create a reading summary of an academic paper, PDF, or research article. Accepts a file (PDF or text format) or a directory of papers. Produces a structured markdown summary — approximately 400–600 words — covering primary contributions, major questions and answers with point estimates, methods and data, and limitations and robustness. Includes BibTeX citation retrieved from Google Scholar and keyword metadata.
日本語の概要は準備中です。原文の説明を表示しています。
Agent-agnostic long-term project memory through `.memory-bank/` + RULES (TDD/SOLID/Clean Architecture/FSD/Mobile) + dev-toolkit commands. Use when working in a project with a `.memory-bank/` directory or when the user explicitly asks for memory-bank workflow, code rules, or dev-toolkit commands (`/mb`, plan, spec, verify, done; «память проекта», «контекст проекта», «план», «продолжай по плану»).
日本語の概要は準備中です。原文の説明を表示しています。
Restrict file edits to a specific directory for the session. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Upper Echelons Theory (Hambrick and Mason, 1984) to analyze how top management team characteristics — demographics, experiences, values — shape strategic choices and organizational outcomes. Use this skill when the user needs to evaluate TMT composition effects on strategy, predict strategic direction from leadership profiles, assess whether managerial discretion enables or constrains executive influence, or when they ask 'does leadership background matter for strategy', 'how does TMT composition affect decisions', or 'why did this management team make that choice'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Full safety mode: destructive command warnings + directory-scoped edits. (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Dunning's OLI Paradigm (Eclectic Theory) to evaluate foreign direct investment decisions based on Ownership, Location, and Internalization advantages. Use this skill when the user needs to decide whether to invest abroad, choose between FDI modes (wholly-owned subsidiary, joint venture, licensing), or explain why a firm internationalizes through FDI rather than export or licensing.".
日本語の概要は準備中です。原文の説明を表示しています。
Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts. Use when creating brand-kit image prompts, identity boards, logo systems, or visual-world presentations.
日本語の概要は準備中です。原文の説明を表示しています。
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. Use when building landing pages, portfolios, redesigns, or frontend interfaces that need strong visual taste.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through creating a new plugin from scratch in a cowork session. Use when users want to create a plugin, build a plugin, make a new plugin, develop a plugin, scaffold a plugin, start a plugin from scratch, or design a plugin. This skill requires Cowork mode with access to the outputs directory for delivering the final .plugin file.
日本語の概要は準備中です。原文の説明を表示しています。
Final-mile orchestrator - commit + push + PR creation. Run after /pre-commit passes. Chains: commit -> push -> /pr-creator (artifact check + PR). Use --issue N to auto-close a GitHub issue on merge. Use --main to ship directly to main with no PR (closes issue + deletes branch).
日本語の概要は準備中です。原文の説明を表示しています。
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browser_use, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle hooks, MCP server setup, or monitoring/observability with Laminar or OpenLIT. Also trigger for questions about browser-use installation, prompting strategies, or sensitive data handling. Do NOT use this for Cloud API/SDK usage or pricing — use the cloud skill instead. Do NOT use this for directly automating a browser via CLI commands — use the browser-use skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
日本語の概要は準備中です。原文の説明を表示しています。
Browser Use — direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
日本語の概要は準備中です。原文の説明を表示しています。
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
日本語の概要は準備中です。原文の説明を表示しています。
Direct browser control via CDP — use for any task involving a website or web app: browsing, scraping and data extraction, filling forms, testing sites, taking screenshots, automating web workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A / design discussion / direct-team-contact to the Prisma Discord at pris.ly/discord. Use for bug, bug report, file an issue, report a bug, feature request, missing feature, this should be a feature, file this, this is a bug, this is broken, surprising behaviour, this doesn't work, file feedback, send feedback, capability gap, file via prisma-next-feedback, ask the team, talk to the team, talk to the Prisma team, talk to Prisma, Discord, Prisma Discord, Q&A, design feedback, is this the intended way, how should I do X, extension author question, extension author needs help.
日本語の概要は準備中です。原文の説明を表示しています。
Route a vague Prisma Next prompt to the right specific skill. Use for "help me with Prisma Next", "what is Prisma Next", "explain Prisma Next", "I'm new to PN", "where do I start", "what can I do with Prisma Next", "what can I do next with Prisma", "just ran createprisma", "tour of Prisma Next", "Prisma Next overview", and comparison questions like "Prisma Next vs Prisma 7", "PN vs Drizzle", "PN vs Kysely", "PN vs TypeORM". Do NOT use when the prompt clearly matches a workflow skill — adoption / quickstart / first-touch orientation / brownfield introspection, schema / contract editing, migration authoring (db update / migration plan / migrate), migration review on deploy / concurrent migrations, queries / db.orm / db.sql / TypedSQL, runtime / db.ts / middleware wiring, build / Vite plugin / Next.js plugin, debug / structured error envelopes / PN-* error codes, or feedback / bug report / feature request — load that sibling skill directly.
日本語の概要は準備中です。原文の説明を表示しています。