openjny

MCP tool reference — exec, benchmark_start, benchmark_status, note_write, etc. Use when: executing commands on VMs, running benchmarks, or recording findings

ISUCON13 contest manual — server topology, service management, benchmark execution, and rules. Use when: checking environment setup, running benchmarks, or understanding contest constraints

ISUPipe application manual — features, terms, constraints, and API specs. Use when: understanding the app domain, checking API behavior or MUST/MAY requirements

General strategy for identifying and adding missing database indexes in ISUCON web applications

General techniques for optimizing user icon/avatar image serving in ISUCON web applications

General techniques for identifying and fixing N+1 query problems in ISUCON web applications

Install and use alp (Access Log Profiler) to identify slow nginx endpoints and analyze request patterns

Tune Go database/sql connection pool settings for optimal MySQL performance under ISUCON load

Interface design for APIs (REST, GraphQL, gRPC, library/SDK, CLI) — consistency, evolvability, error design, versioning, backward compatibility. Use when: designing APIs, reviewing API contracts, versioning decisions, error response design, choosing between REST/GraphQL/gRPC. Triggers: API design, REST, GraphQL, gRPC, versioning, backward compatibility, error response, pagination, rate limiting, OpenAPI

Inject architectural thinking into technology selection, architecture decisions, and design judgments. Not a comparison table — a thinking framework that raises decision quality. Use when: technology stack selection, architecture pattern comparison, ADR creation, design review, non-trivial design decisions. Triggers: architecture selection, technology selection, design thinking, architecture decision, trade-off analysis

Data model selection, consistency trade-offs, data ownership, storage and processing decisions. Use when: choosing databases, designing data models, defining service data boundaries, replication/partitioning decisions, batch vs stream processing. Triggers: data model, database selection, consistency, replication, partitioning, CQRS, event sourcing, saga, aggregate design, transaction isolation

Code and module-level design judgment — complexity management, interface design, naming, abstraction depth, error handling philosophy, information hiding. Use when: writing new modules, reviewing code quality, refactoring decisions, API design, naming discussions. Triggers: design judgment, code quality, module design, complexity, naming, abstraction, error handling, code smell

Production reliability, deployment pipelines, release strategies, incident response, SLO design. Use when: designing for failure, planning releases, setting SLOs, incident response, postmortem review, deployment pipeline design. Triggers: resilience, reliability, SLO, circuit breaker, deployment strategy, canary, blue-green, incident, postmortem, DORA, rollback, bulkhead, timeout

When to refactor, what to refactor, how far to go. Technical debt classification, legacy code strategy, refactoring safety. Use when: deciding whether to refactor, scoping refactoring work, handling legacy code, classifying technical debt, choosing refactoring techniques. Triggers: refactoring, technical debt, code smell, legacy code, when to refactor, refactoring scope, debt payoff

Thinking like an attacker. Threat modeling, secure-by-default design, security trade-offs. Use when: designing authentication/authorization, reviewing code for vulnerabilities, making security vs usability trade-offs, threat modeling, handling secrets or user input. Triggers: security, threat model, STRIDE, OWASP, authentication, authorization, input validation, secrets, attack surface, vulnerability

Testing strategy and design decisions — what to test, how to test, when to mock, test classification, TDD rhythm. Use when: deciding test approach, choosing test scope, reviewing test quality, legacy code testing, mock vs real debate. Triggers: testing strategy, what to test, test design, mock, TDD, test pyramid, test doubles, legacy testing, characterization test

Microsoft Build 2026 でのアナウンス、セッション情報や関連リソース情報を提供するスキル。Triggers: Build 2026, アナウンス, セッション, 新機能, GA, Preview

Build 2026 の個別発表・新機能の content/announcements/*.md を作成・更新する。Use when: アナウンス作成、announcement、エントリ作成、製品まとめ、新機能追加、コンテンツ追加

Build 2026 セッションの一次素材（VTT字幕・スライド・メタデータ）を取得し、content/sessions/ 形式の Markdown を生成する。Use when: セッションまとめ、session summary、セッション追加、セッション作成、BRK/DEM/LTG/OD のコンテンツ化

Build 2026 コンテンツの調査方法論。ツールの使い分け、ソース探索の深さ基準、例外ハンドリング、バリデーションチェックリスト。Use when: 調査、リサーチ、ソース探索、ファクト検証、investigate、research

Retrieve Azure service pricing information using the Azure Retail Prices API. Get detailed pricing data including regions, SKUs, and pricing types (consumption, reservation, savings plans) without authentication. Use when estimating Azure costs, comparing prices across regions or SKUs, checking reservation or savings plan pricing, or collecting data for cost analysis and budget management.

Retrieve Azure Updates information using the Microsoft Release Communications API. Get the latest announcements about new features, previews, retirements, and general availability for Azure services without authentication. Use when tracking Azure product updates, monitoring service changes, checking retirement announcements, or following new feature releases.