Hideki Koike

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review local git changes or an architecture document against the Security, Privacy, and Compliance pillar of Google's Cloud Well-Architected Framework. Identifies gaps across 7 principles (security by design, zero trust, shift-left, preemptive defense, AI used securely, regulatory/privacy, shared responsibility), and for each non-trivial risk asks the user to decide Accept / Mitigate / Defer / Block — producing a documented risk register, not just a finding list. GCP-principle-based but cloud-agnostic. Use when the user asks for a security architecture review, Well-Architected security check, threat / risk review, or zero-trust assessment. Trigger phrases include "well architected security", "GCP security review", "security pillar review", "security risk review", "zero trust review", "セキュリティレビュー", "セキュリティリスクレビュー", "Well-Architected セキュリティ".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

チケットや要件から「HTML UIスペック (決定ログ D番号・未決Qカード・文言一覧)」と 「触って遷移を確認できるHTMLシミュレーター (カバレッジ自動チェック付き)」のペアを artifactとして作り、ユーザーレビューを何巡も回して確定させる設計レビューループ。 各巡で敵対的な整合検証 (スペック⇔シミュレーター⇔文言表) を行い、確定した内容だけを 実装Ticket/Confluenceに最低限のテキストで同期する。Figma納品はfigma-shot-boardに委譲。 Use when the user wants an interactive UI spec, a transition simulator, a decision-log driven design review, or to iterate a UI design with confirmable state transitions. Triggers: "ui-spec-sim", "/ui-spec-sim", "UIスペックとシミュレーター", "スペックシミュレーター", "設計レビューループ", "遷移を触って確認できるものを作って", "トランジションシミュレーター", "デザイン決定ログでレビュー", "interactive spec", "transition simulator", "spec with simulator".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate test outlines (living documentation) and test code from natural language feature descriptions. Supports .NET (xUnit/NUnit/MSTest), Python (pytest), TypeScript (Vitest/Jest). Strict mode: no internal module mocking, real DB, AAA pattern, Design by Contract (DbC). Use when the user asks to generate tests from a feature description, create test cases from requirements, write test outlines, scaffold test files, generate test code from spec, convert TODO tests to real tests, or create tests for a function. Trigger phrases include "test scenario", "テストシナリオ", "generate tests", "テスト生成", "テストケース作成", "write tests for", "scaffold tests", "tests from requirements", "テストアウトライン", "convert todo tests", "implement test outline", "test outline", "test cases from spec".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review local git changes or an architecture document against the Cost Optimization pillar of Google's Cloud Well-Architected Framework. Identifies gaps across 6 principles (spend aligned to value, cost-aware culture, utilization efficiency, continuous optimization, architectural cost drivers, workload-specific cost patterns), and for each non-trivial risk asks the user to decide Accept / Mitigate / Defer / Block — producing a documented risk register, not just a finding list. GCP-principle-based but cloud-agnostic. Use when the user asks for a cost review, cloud cost optimization check, rightsizing review, or spend efficiency review. Trigger phrases include "well architected cost", "GCP cost review", "cost optimization review", "cost pillar review", "FinOps review", "rightsizing review", "コストレビュー", "コスト最適化レビュー", "Well-Architected コスト".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review local git changes or an architecture document against the Reliability pillar of Google's Cloud Well-Architected Framework. Identifies gaps across 8 principles (SLOs aligned to UX, recovery targets, HA via redundancy, horizontal scalability, observability, graceful degradation, tested recovery, postmortems), and for each non-trivial risk asks the user to decide Accept / Mitigate / Defer / Block — producing a documented risk register, not just a finding list. GCP-principle-based but cloud-agnostic. Use when the user asks for a reliability review, resilience / SRE review, SLO assessment, failure-mode analysis, or recovery readiness check. Trigger phrases include "well architected reliability", "GCP reliability review", "reliability pillar review", "SLO review", "resilience review", "信頼性レビュー", "Well-Architected 信頼性", "可用性レビュー", "障害耐性レビュー".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use confluence-cli to read, search, create, update, move, and delete Confluence pages and attachments from the terminal. Prefer this skill over `mcp__claude_ai_Atlassian__*` MCP tools when you need: page export with attachments, copy-tree, attachment management, profile-based multi-instance access, read-only mode, CQL search, or shell pipelines. Trigger phrases include "confluence", "confluence-cli", "confluence page", "read confluence", "search confluence", "create confluence page", "update confluence page", "confluence attachment", "confluence spaces", "export confluence", "confluence comments", "confluence copy-tree".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run frontend E2E tests with video evidence. Generates a Playwright test from the scenario CSV and runs it via CLI with video recording. Supports Chrome profile reuse (--chrome-profile) for testing with existing cookies, sessions, and extensions via launchPersistentContext. Generates a test report with video, screenshots, and trace. Does NOT modify application code — only creates documents (markdown, CSV, test scripts). Supports --non-interactive for fork / CI use (fails fast on scenario gaps instead of asking). Use when the user asks to run E2E tests, verify frontend behavior, do end-to-end testing, check UI flows, or test a web app. Trigger phrases include "e2e", "E2E test", "end-to-end test", "e2e testing", "frontend test", "UI test", "playwright test", "browser test", "verify the UI", "test this page".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run OpenAI Codex via the Codex App Server (JSON-RPC-over-stdio) for streaming multi-turn chat sessions with persistent threads, structured output, image input, and rich event streams. Default entry point for ChatGPT/GPT/Codex-like conversations from the terminal. Uses the user's ChatGPT subscription (Plus / Pro / Team) exclusively via `codex login` — never consumes OPENAI_API_KEY billing, by design. Implementation: TypeScript on deno with npm:@openai/codex-sdk; spawns the existing system codex binary. Decoupled async invocation: every turn returns turn-id in <1 s; the actual SDK work runs in a detached worker that streams to per-turn files under ~/.codex-server/turns/<turn-id>/ — Bash's 2-min timeout never applies. Prefer this over codex-cli for streaming UX, multi-turn dialogues that need live state, structured (JSON schema) output, attaching images, or programmatic event handling. Use codex-cli only for one-shot batch invocations that pre-capture to an -o file. For OpenAI Platform API calls specifically (embeddings, image generation, audio, moderation, batches, files) — not open-ended chat — use openai-cli instead; that path bills OPENAI_API_KEY, this one uses the ChatGPT subscription. Trigger patterns (match any variation): codex / codex-server / codex app server / codex app-server / openai / open ai / OpenAI / chatgpt / chat gpt / ChatGPT / GPT / ask gpt / chat with gpt / gpt session / codex session / streaming chat / multi-turn chat / multi turn chat / second opinion / cross-check / cross check / ai pair programming / another AI / external AI / ask another model / get GPT's take / what does openai think / show me what gpt thinks / structured output from gpt / json schema gpt / resume codex thread / continue codex conversation / continue codex session / /codex-server

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

英語の技術ドキュメント (Hugging Face docs / GitHub README / arXiv 論文 / 技術ブログ等) を、日本人が読んで AI 生成と気づかない自然な日本語の解説サイトに変換します。フェッチ → 構成 → HTML/CSS/JS 生成 → 多角レビュー → 修正 → ローカル配信、まで一気通貫。日本語自然さチェックは `@agent-naturalize-ja:naturalize-ja` subagent に委譲 (辞書本体・grep・質的レビューはそちら側に集約)。技術正確性は codex-cli、UX/レスポンシブは汎用 Agent が担当。Triggers: 「英語ドキュメントを日本語で解説するサイトを作って」「Japanese explainer for [URL]」「英語の技術ドキュメントをやさしく日本語にして」「Convert this English doc to a Japanese site」「AI っぽくない日本語で技術解説」「Hugging Face docs を日本語化」「arXiv を日本語で噛み砕いて」「en-to-ja explainer」「/en-to-ja-explainer」

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Place a set of local screenshots/images into Figma as a labeled, sectioned board (auto-layout, title + section rows, layer names = filenames) using the Figma MCP (upload_assets + use_figma). Works against a new file or an existing file/page, and encodes the non-obvious upload gotchas (default 400x300 FILL frames, first-page placement, natural-size resize, 2x capture scaling). Use when the user wants screenshots arranged in Figma, UI states delivered as a Figma page, or images moved/relocated between Figma files. Triggers: "figma-shot-board", "/figma-shot-board", "figma shot board", "スクショをFigmaに並べて", "FigmaにUIステートを起こして", "スクショをFigmaに起こして", "screenshots to figma", "figma board of screenshots", "put these images in figma", "Figmaに画像を配置".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Operate Google Drive from the terminal via `rclone` — list, upload, download, search, sync, mount, check quota, export Google Docs/Sheets/Slides, browse Shared Drives, and manage trash. Use whenever the user mentions Google Drive, Drive folders, or anything stored in Google Workspace files from the command line. Trigger phrases include "google drive", "g drive", "gdrive", "drive cli", "upload to drive", "download from drive", "list drive", "search drive", "sync to drive", "backup to drive", "mount google drive", "mount drive", "check drive quota", "drive storage", "drive space", "google docs export", "shared drive", "shared with me", "drive trash", "empty drive trash", "google workspace files", "drive folder", "rclone drive", "rclone gdrive".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate AGENTS.md (cross-tool agent context — Codex CLI, Aider, Cursor, etc.) and wire CLAUDE.md as a symlink so Claude Code reads the same file. Delegates content generation to Claude's built-in /init when needed, then renames + symlinks. Idempotent. Triggers — /agents-init, "generate agents.md", "create agents.md", "share claude and codex context", "set up agents file", "init agents", "agents-init", "cross-tool agent context", "wire claude and agents".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Senior-level .NET development guidance for architecture, code review, scaffolding, EF Core, ASP.NET Core, Blazor, and MAUI targeting .NET 8 and .NET 10. Provides opinionated best practices, modern C# idioms, security hardening, performance optimization, and testing strategies at a staff/senior engineer level. Trigger patterns (match any variation): .NET / dotnet / dot net / .net / C# / csharp / c sharp / c-sharp / ASP.NET / aspnet / asp.net core / Entity Framework / EF Core / ef core / Blazor / MAUI / maui / NuGet / nuget / Clean Architecture + .NET / CQRS + .NET / DDD + .NET / {review, scaffold, create, design, architect, optimize, migrate} + {C#, .NET, dotnet, csharp} / "dotnet new" / "dotnet build" / "dotnet test" / "dotnet publish" / ".NET best practices" / "C# patterns" / "senior .NET" / ".NET architecture"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run OpenAI Codex CLI from the terminal for batch / one-shot `codex exec` invocations with output captured to an `-o` file. Use for fire-and-forget runs, scripted CI, code review batches (`codex review`), and resuming a specific session by id (`codex exec resume`). Always use this skill instead of `mcp__codex__codex` and `mcp__codex__codex-reply` MCP tools — CLI is faster and more capable. For streaming UX, multi-turn dialogues that need live state, structured (JSON schema) output, attaching images, or programmatic event handling → **use codex-server instead**. codex-server uses the user's ChatGPT subscription via Codex App Server and decoupled async invocation that bypasses the Bash 2-minute timeout entirely. Trigger patterns (batch-only — chat/streaming triggers belong to codex-server): codex-cli / codex CLI / codex exec / codex review / codex resume / codex fork / batch + {codex, gpt} / one-shot + {codex, gpt} / non-interactive + codex / codex {to a file, -o, output file, captured output} / CI + {codex, gpt} / scripted + {codex, gpt} / fork codex session / resume codex session by id

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

日本語の技術文書（書籍の章、記事、解説文）を新規に書く、既存の下書きを推敲する、公開前に規範違反を洗い出す、の3モードで支援します。k16shikano氏のGist「日本語技術文書の文章規範」(Unlicense) をベースにした段落構成、論証の厳密さ、読み手の負荷管理、演出の抑制などの文章規範 (references/rules.md) と、BLOCKER/IMPORTANT/TASTEのseverity方式チェックリスト (references/checklist.md) を内蔵。技術書/APIリファレンス/技術ブログ/翻訳解説ごとの例外は references/style-profiles.md に分離。AIっぽい語彙そのものの検出と置換は行わず、既存スキル naturalize-ja に委譲します (疎結合)。Triggers: 「日本語の技術文書を書いて」「技術書の章を書いて」「この下書きを推敲して」「パラグラフライティングで整えて」「公開前にチェックして」「日本語技術文書の規範に沿って直して」「japanese tech writing」「japanese-tech-writing」「/japanese-tech-writing」

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use @pchuri/jira-cli to view, search, create, update, and delete Jira issues, comments, sprints, and projects from the terminal. Prefer this skill over `mcp__claude_ai_Atlassian__*` MCP tools when you need: JQL search, sprint/board management, markdown export, file-based descriptions, issue deletion, comment management, or shell pipelines. Trigger phrases include "jira", "jira-cli", "jira issue", "create jira issue", "search jira", "jira sprint", "jira board", "jira project", "jira comment", "jira JQL", "list jira issues", "view jira issue", "jira backlog".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create project-local Claude Code skills (.claude/commands/) in any project directory. Analyzes the project's tech stack, structure, and conventions, then generates tailored local skills (custom slash commands) scoped to that project. Like /my-skill-factory but output stays local — no marketplace installation. Trigger patterns: - local skill / local command / project skill / project command - create local skill / make local skill / add local command - "make a skill for this project" / "create command for this repo" - suggest skills / suggest commands / what skills would help - update local skill / edit local command / modify project skill - /local-skill-factory

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn an image into a grid of 16-20 minimalist logo marks (geometric, line art, negative space, emblem, badge, monogram) on a light background. Use for logo ideas or brand marks from a photo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Compact the current conversation into a handoff document for another agent to pick up.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.