1.7万 件 ・ 関連度順
概要と使いどころ
Design AWS architectures for startups using serverless patterns and IaC templates. Use when asked to design serverless architecture, create CloudFormation templates, optimize AWS costs, set up CI/CD pipelines, or migrate to AWS. Covers Lambda, API Gateway, DynamoDB, ECS, Aurora, and cost optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
日本語の概要は準備中です。原文の説明を表示しています。
Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS/MP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or auditing an agentic AI system holistically. Activates the six-component harness framework (ℛ Reasoning, ℳ Memory, 𝒞 Context, 𝒮 Skills, 𝒪 Orchestration, 𝒢 Governance) from arXiv:2605.26112. Trigger phrases: "design an agent system", "why is my agent unreliable", "harness architecture", "system-level agent design", "beyond model scaling", "agentic infrastructure", "scale my agent system", "agent performance bottleneck".
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "model agent mental states", "implement BDI architecture", "create belief-desire-intention models", "transform RDF to beliefs", "build cognitive agent", or mentions BDI ontology, mental state modeling, rational agency, or neuro-symbolic AI integration.
日本語の概要は準備中です。原文の説明を表示しています。
Build AI-powered browser agents that autonomously navigate, scrape, fill forms, and extract data from dynamic websites using LLM reasoning + Playwright. Use when building a scraper that must survive site redesigns, an agent that completes multi-step web workflows, or a replacement for brittle Selenium/Puppeteer scripts.
日本語の概要は準備中です。原文の説明を表示しています。
Routes requests to the BMad Method (v6.12.4) agile framework: persona agents, planning skills (brief, PRFAQ, PRD, UX, spec, architecture, epics, sprint planning), shipping skills (build, code review, walkthrough, QA tests, retrospective), and core helpers (brainstorming, research, review, party mode). Use when the user mentions BMad or BMM, names a BMad agent such as Mary, John, Sally, Winston, or Amelia, or wants a structured flow from idea through PRD and architecture to built, reviewed code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing evaluation suites for agentic systems, choosing agent benchmarks, measuring multi-agent performance, or critiquing single-score evaluation of agents. Based on arXiv:2605.26112v1. Trigger phrases: "evaluate my agent", "benchmark agent", "measure agent reliability", "pass^k evaluation", "agent metrics beyond success rate", "trajectory quality", "memory hygiene metric", "longitudinal agent eval", "why my agent scores well on benchmarks but fails in production".
日本語の概要は準備中です。原文の説明を表示しています。
Use when turning expert materials, execution traces, repository evidence, or long-form documents into an inspectable, correctable, and empirically verified agent skill. Covers source governance, capability-vs-behavior separation, contrastive induction from successes and failures, intervention testing, versioning, rollback, and task-conditioned vs. reusable-library evaluation.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a complete AGENTS.md at the repository root following the agents.md format: setup, build, test, style, and PR conventions coding agents need. Use when a repo has no AGENTS.md, when onboarding coding agents to a codebase, or when the existing agent instructions are stale.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstraps and runs a multi-agent development team with roles (dev, QA, DevOps), parallel work, and sprint plans that survive context resets. Use when kicking off a project with parallel AI agents, writing brainstorm prompts that produce real debate, planning sprints across chats, or recovering from context overflow mid-sprint.
日本語の概要は準備中です。原文の説明を表示しています。
Refactor code by renaming variables, methods, classes, and concepts for clearer intent. Use when asked to improve names, clarify naming, perform a naming pass, or run `/refactor:names`.
日本語の概要は準備中です。原文の説明を表示しています。
Refactor Swift code toward declarative functional programming with immutability, value types, pure functions, transformations, and closure-based APIs. Use when asked for functional refactoring or `/refactor:functional`.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive, measurement-driven performance optimization for latency, throughput, memory/GC, and tail behavior. Use when the user asks to optimize/speed up, reduce latency (p95/p99), increase throughput/QPS, lower CPU/memory/allocations/GC pauses, profile hot paths, or run a benchmarked perf pass (including JSONL/query-heavy code). Requires before/after measurement on a runnable workload (or an explicit `UNMEASURED` plan) plus a correctness gate.
日本語の概要は準備中です。原文の説明を表示しています。
Mine a codebase for breakthrough, evidence-backed opportunities — features, additions, refactors, simplifications, DX, UX, reliability, performance, or architecture cleanup. Researches project reality first, then forces two escalation gates (reject the merely-adequate idea; expand ambition 10x then collapse to the smallest proof-bearing artifact). Outputs ranked opportunities, an escalation ledger, and one plan seed. Does not implement or create tickets.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive code review for quality, security, performance. Triggers on 'review code', 'code review', 'check this PR', 'audit code'.
日本語の概要は準備中です。原文の説明を表示しています。
Create and integrate the machine-level core of a new EMULATORS emulator, including Computer and Emulator derivatives, memory and port maps, chip ownership and wiring, clock coordination, model configuration, commands, formatters, executables, and Visual Studio projects. Use when scaffolding a machine namespace, adding a model or regional variant, assembling existing components into a computer, or making a new emulator build and start.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, scaffold, implement, and integrate a complete new emulated computer or console in the EMULATORS repository. Use when Codex creates a new machine, platform, hardware model, or emulator executable; decides which existing CPUs, chips, memory, I/O, video, sound, ROM, and framework classes to reuse or extend; or coordinates several emulator subsystems into a bootable tested system.
日本語の概要は準備中です。原文の説明を表示しています。
Validate and implement Sinclair ZX Spectrum 48K ROM-visible behavior in the EMULATORS repository, including reset and restart vectors, IM1/NMI handling, keyboard scanning and repeat, beeper and tape routines, screen/printer output, channels and streams, BASIC tokenization and execution, expression evaluation, memory movement, system variables, calculator stack, floating-point formats, ROM traps, localized ROM selection, and firmware/hardware timing contracts. Use when Codex reviews or edits ZX Spectrum ROM loading, KERNAL-style traps, keyboard, tape, screen, printer, BASIC files, tokens, system variables, startup, interrupts, or compatibility tests.
日本語の概要は準備中です。原文の説明を表示しています。
Design and implement unit, conformance, integration, timing, boot, trace, video, audio, and regression tests for EMULATORS processors, chips, peripherals, and complete machines. Use when creating a verification strategy for a new emulator, converting hardware documentation into tests, adding diagnostic programs or golden artifacts, measuring behavioral coverage, or proving that components interact correctly.
日本語の概要は準備中です。原文の説明を表示しています。
Crear, ampliar o actualizar documentación técnica de EMULATORS en formato DOCX usando la plantilla oficial del repositorio, con portada parametrizada, índice, prólogo, capítulos de contenido, anexos, listas de ilustraciones y ecuaciones, marca de agua del autor y pie Página X | Y. Usar cuando Codex deba documentar subsistemas, arquitecturas, dispositivos, modelos, herramientas, compilación, uso, pruebas o cualquier otro aspecto del emulador y el resultado deba conservar la identidad visual de docs/UserGuide.docx.
日本語の概要は準備中です。原文の説明を表示しています。
Validate Commodore 64 SID 6581/8580 sound emulation in EMULATORS, including $D400-$D7FF register decoding, voices, frequency, pulse width, control bits, ADSR/envelope behavior, oscillator sync/ring/noise/test, filters, volume DAC/sample clicks, paddles, read-only registers, mirrors, and reSID integration. Use when Codex reviews or edits SID, Sound, audio wrapper, register, filter, waveform, envelope, or mapped SID behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Trigger when auditing documentation, checking markdown link integrity, formatting tables, checking headers, or verifying absolute/relative paths.
日本語の概要は準備中です。原文の説明を表示しています。
Normative sufficiency conditions for Initial Boundary Conditions (IBCs) and the SOP for the cheap-tier boundary refinement loop (/boundary). Trigger when: - Crafting, auditing, or refining a prompt/IBC destined for an expensive (architect-class) model or an autonomous worker dispatch. - Evaluating whether a task frame is sufficient to bound an agent walk. - Prompt contains: /boundary, IBC, initial boundary condition, boundary contract, sufficiency conditions, worker prompt, prompt refinement.
日本語の概要は準備中です。原文の説明を表示しています。