1.5만건 · 관련도순
Diagnostic method for any bug, failure, regression, flake, or slowdown. Use before proposing a fix: something is broken, throwing, not saving, not showing, or 'worked yesterday'; on 'debug this' or 'find the root cause'; and immediately after a fix attempt did not work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Applies Anthropic brand colors and typography to artifacts that need a consistent look-and-feel. Use when brand colors, style guidelines, visual formatting, or company design standards apply.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide the user through starting a new web application project — elicit requirements (MoSCoW scoping), create architecture and requirements documents, break work into tasks, and register them as a GitHub Project kanban board. Use when the user says "新しいWebアプリを作りたい", "Webアプリの立ち上げを手伝って", "start a new web app project", "プロジェクトの要件を整理したい", or "GitHub Projectにタスクを登録したい".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "これらのIssueを全部実装して", "implement these issues autonomously", "Issue一覧を自動で片付けて", "これらのタスクを順番に実装してPRにして", or provides a list of GitHub Issue numbers/URLs for autonomous batch implementation. Fetches all specified Issues, resolves dependency order, then iterates through each — creating a worktree, implementing, and opening a PR — without user intervention.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "このエラーを直して", "help me debug this", "fix this stack trace", "なぜこのエラーが出るの", "CI が落ちた", or pastes an error message or stack trace and wants help diagnosing it. Classifies the error type, identifies related files, and proposes up to three root-cause hypotheses with concrete fix plans.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user wants to "stress-test a design", "challenge an idea", "red team a proposal", "get critical feedback on a design", "validate a design", "adversarial architecture review", "risk assessment", "設計を検証して", "反論をもらいたい", "設計を批判的にレビュー", "デビルズアドボケート", "ストレステスト", "弱点を指摘して", "穴を見つけて", "この設計で良いか", "リスク評価", "設計のアーキテクチャレビュー", or mentions structured adversarial review of a proposal or design. NOTE: Use this for validating PROPOSALS and DESIGNS through adversarial debate, NOT for generic code review, PR review, or normal review requests (use /codex:review or /codex:adversarial-review for those). Also NOT for investigating unknown bugs (use /agent-dialectics:strong-inference for that).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user wants to "test a claim against data", "validate an empirical hypothesis", "refine a model/theory with evidence", "characterize a pattern and verify it", "演繹と帰納で検証", "仮説をデータで検証して更新", "実例と反例で確かめる", "弁証法ループ", "主張を現物で裏取り", "傾向分析を検証して精緻化", or mentions iteratively updating a hypothesis by deriving predictions and testing them against a real corpus. NOTE: Use this for VALIDATING/REFINING an empirical claim or model against real data through a derive→test→update loop. Use strong-inference for debugging an UNKNOWN cause, and devils-advocate for adversarially stress-testing a DESIGN proposal.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of membership (medlemskap) domain in melosys-api. Use when: (1) Understanding pliktig vs frivillig membership determination, (2) Debugging medlemskapsperiode creation and updates, (3) Understanding trygdedekning combinations and rules, (4) Investigating MEDL synchronization issues, (5) Understanding membership status transitions and innvilgelsesresultat, (6) Working with UtledMedlemskapsperioder for proposal generation, (7) Understanding the relationship between bestemmelse, medlemskapstype, and trygdedekning. Triggers: medlemskapsperiode, pliktig, frivillig, trygdedekning, MEDL, innvilgelsesresultat, medlPeriodeID, bestemmelse.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the current agent's thin semantic consistency review after shared Keel Core gates and before task completion, sync, archive, or meaningful handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Align explicit requirements, implicit expectations, non-goals, observable acceptance, evidence, and decision authority before OpenSpec specs and executable tasks finalize. Use when authoring or updating a proposal, design, specs, or tasks, or when a request hides a material product choice. Do not use for routine implementation of an already-authorized task, unrelated conversation, or facts the repository can answer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, validate, or clear the optional keel-handoff/v1 pointer override when human intent cannot be inferred uniquely.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug Keel agent command or validation failures under Keel's selected OpenSpec task contract. Use when `/opsx:apply` or a selected task reports failed commands, failing tests, validation errors, stop decisions, or needs an evidence-bound failure report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive Keel agent test-first or evidence-first execution for a selected OpenSpec task. Use when a task needs software tests, hardware testbench, assertions, lint, new behavior proof, regression coverage, or red/green evidence before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding or repairing Spark regression tests for asynchronous ownership, cancellation, persistence, restart recovery, or cross-surface projections. Not a coverage campaign, performance benchmark, source-text policy check, or full delivery review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a running Spark or DSH web service needs real-browser verification — page load, client-plugin boot errors, console errors, failed requests, or onboarding/dialog rendering — with the repository's own Playwright chromium.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs, hardens and audits the system around an agent that runs on its own — bot, scheduled task, routine, automation — all but the prompt text. Trigger for guardrails, kill switches, cadence and loop pacing (cron, wake, /loop), retries and failures, output contracts, protected resources, handoffs between agents, or isolating untrusted email and web content; to emit a spec as a Cowork task, routine, scheduled task or CI job; or say agentwright (emit, audit, refresh); it never schedules or runs one. Prompt text is promptwright's; CLAUDE.md, rigwright's; skills, skillwright's; runtime grants and credentials, gatewarden's scan; code threats, a security harness's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Directs pixel art that must read at several zoom scales at once — per-scale palette and silhouette rules, terrain-versus-unit contrast, a one-scene look test, and briefs for an artist or image generator. Trigger when a game renders one world through zoom bands or levels of detail, a pixelated 3D or 2.5D band with billboards included; when a sprite, unit or icon vanishes against terrain zoomed out; for a cross-band look test or pixel-art style guide; or say pixelsmith (test, brief, audit, 3d). Works from a described scene. Drawing is an art tool's job; rendering and LOD code the game's engineering; a brand palette brandscribe's; game audio soundsmith's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proves a Godot 4.x build is actually green and holds its project conventions. Trigger when a GUT or GDScript result needs believing (a suite green while a script failed to parse, a one-file run that ran the whole suite, drifted CI guard counts, a coverage claim, a gate figure, a failing check someone wants softened); to review scenes, signals, awaits, threads, determinism, saves, imports or .uid files, or the upgrade rule (not the migration); to prove a simulation or balance rule; for import settings and the pixel-art render precondition; or say godotsmith (check, guard, gate, review, intake). API reference is the Godot docs'; art reads pixelsmith's; audio direction soundsmith's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drives OBS Studio through its WebSocket, read-only by default, and turns recordings into clips, VOD cuts and chapters with FFmpeg. Trigger to audit an OBS setup; when a stream drops frames or lags; to switch a scene, mark a moment or save the replay buffer; to cut clips, burn in captions, normalize loudness or write chapters; when OBS shares a GPU; or say obsrunner (audit, check, set, mark, post, sheet, status, hold, release, refresh). Live work needs the user-installed obsws-python package. Never goes live, uploads or moderates chat. Caption files are whisperrunner's; thumbnails comfyrunner's; titles commscribe's; analytics duckrunner's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.