「elo」の検索結果

Work up Malignancy-Associated Hypercalcemia (MAH) — distinguish humoral hypercalcemia of malignancy (HHM, PTHrP-driven), local osteolytic hypercalcemia, 1,25(OH)2D-mediated lymphoma hypercalcemia, ectopic PTH secretion, and multiple myeloma — and pick the right confirmatory tests and therapy direction. Trigger when a clinician asks "is this hypercalcemia from cancer", "PTHrP positive what now", "hypercalcemia in lung cancer / breast cancer / lymphoma / myeloma", "humoral hypercalcemia of malignancy", "MAH workup", or any hypercalcemia case with suppressed PTH and a known or suspected malignancy.

日本語の概要は準備中です。原文の説明を表示しています。

This skill recommends lifelong follow-up tests for cardiac myxoma and associated disease (testicular tumors, acromegaly, thyroid lesions) in patients with Carney complex. Use when managing a Cushing’s syndrome patient with a confirmed or suspected Carney complex diagnosis (e.g., spotty skin lentigines, cardiac myxoma, endocrine tumors).

日本語の概要は準備中です。原文の説明を表示しています。

This skill recommends lifelong biochemical testing for recurrence in all patients with Cushing's syndrome after adrenalectomy, except those with resected adrenal adenoma showing CT density <10 Hounsfield units. Use when determining long‑term follow‑up strategy for a post‑adrenalectomy CS patient; triggers include “post‑adrenalectomy Cushing’s syndrome”, “CT density <10 HU”, and “adrenal adenoma resection”.

日本語の概要は準備中です。原文の説明を表示しています。

On-demand "what's new" generator. Main context (which knows the impending change) writes keepachangelog-style entries to a fragment file at `.claude/state/whatsnew/<slug>.json` (gitignored, transient). An optional per-project `project.json → whatsnew.route_workflow` names a routing workflow that consumes the fragment and renders it wherever the project wants (a site page, a release body, a docs page). Not a workflow phase — it never blocks a commit, and it never writes `CHANGELOG.md` (that file is owned solely by semantic-release in CI).

日本語の概要は準備中です。原文の説明を表示しています。

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

日本語の概要は準備中です。原文の説明を表示しています。

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

日本語の概要は準備中です。原文の説明を表示しています。

Multi-container Docker applications with docker-compose — define services, networks, volumes, and orchestrate local development environments

日本語の概要は準備中です。原文の説明を表示しています。

Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.

日本語の概要は準備中です。原文の説明を表示しています。

You are an API mocking expert specializing in realistic mock services for development, testing, and demos. Design mocks that simulate real API behavior and enable parallel development.

日本語の概要は準備中です。原文の説明を表示しています。

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals.

日本語の概要は準備中です。原文の説明を表示しています。

AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents.

日本語の概要は準備中です。原文の説明を表示しています。

Automate Accelo tasks via Rube MCP (Composio). Always search tools first for current schemas.

日本語の概要は準備中です。原文の説明を表示しています。

Premiere Pro 動画編集ワークフローを Claude Code で自動化するスキル集。/cut は Premiere Pro XML の無音・雑音区間をジェットカット、/srt は WAV+Premiere XML から日本語テロップ用 SRT を並列Whisper→LLM意味区切り→全体アライメントSRT の3ステップ(v6)で生成、/srt-fast は改行工程まで3チャンク並列化した高速版、/telop-check は書き出し済みMP4を全編スキャンしてテロップの数字表記・誤字脱字・い抜き・ら抜き・固有名詞ミスを検出する。faster-whisper / ffmpeg / Premiere Pro を要するローカル実行型。日本語トーク動画のショート / ロング編集向け。

Writes a lightweight Markdown concept handoff from existing decisions and evidence. Use when explicitly asked for a developer handoff, to transfer a prototype or concept to another team, or to prepare a brief for implementation. Not for ordinary prototype completion, building, reviewing or publishing.

日本語の概要は準備中です。原文の説明を表示しています。

Decompose an epic into atomic parallelizable tasks, route each to the right skill, and keep the four delivery records straight — issues, STATUS, ROADMAP, CHANGELOG. Use as a meta-router when several skills could apply, and as the baseline for how delivery state is recorded. Trigger at the start of any multi-track epic, when the skill count exceeds ~12, or when the records have drifted from reality.

日本語の概要は準備中です。原文の説明を表示しています。

Measure, root-cause, fix, verify and record performance contention on a developer machine: cloud-sync daemons (iCloud Drive, OneDrive, Dropbox, Google Drive), file indexers, AI-tool MCP server fleets, and automation browsers left behind by tests and browser skills. Trigger when the machine is slow, apps freeze, browser or MCP tool calls time out, load exceeds the core count, or before and after any UI/UX/performance test run. Includes the L0–L4 optimisation scale and the test-hygiene contract.

日本語の概要は準備中です。原文の説明を表示しています。

Govern the SemVer release process — versioning discipline, tag-based GitHub releases, changelog hygiene, and the ADR that confirms the release strategy is agreed. Trigger when setting up a release process, before a first public release, or when release practice has become inconsistent. Owned by delivery-orchestrator.

日本語の概要は準備中です。原文の説明を表示しています。

Google ADK (Agent Development Kit) orchestration patterns — boundaries, agent composition, and tool seams. Trigger when designing or reviewing multi-agent systems built on ADK. Authoritative source: adk.dev.

日本語の概要は準備中です。原文の説明を表示しています。

Draft release summaries, changelog summaries, version PR notes, and changeset-friendly package release notes for npm packages or monorepos. Use this whenever the user asks to write a release summary, 发版说明, release notes, changelog entry, version PR summary, package publish notes, or wants the agent to summarize what will be released from git history, diffs, or changesets, especially for ui libraries, design systems, and multi-package workspaces.

日本語の概要は準備中です。原文の説明を表示しています。

公開CLIツールのリリース作業(バージョン付け・利用者向けドキュメント・CHANGELOG・検証・PR・タグ)を、ツール公開手順の規約に従って進める。ツールをリリースするとき、バージョンを上げて公開するとき、リリースPRやタグを作るときに使用する。

Run the complete release workflow: changelog entry, version bump, git tag, and GitHub release. Invokes changelog-entry, tag-version, and publish in sequence. Use when releasing a new version of the project.

日本語の概要は準備中です。原文の説明を表示しています。

Use when balancing eng-team velocity vs quality vs burnout — on-call load, focus fragmentation, reorg shock. Triggers on 'team is burning out', 'why is velocity dropping'.

日本語の概要は準備中です。原文の説明を表示しています。

Turn a shipped changelog into a release narrative — value-not-feature framing, audience-segmented surfaces. Triggers on 'announce the release', 'write changelog post'.

日本語の概要は準備中です。原文の説明を表示しています。

[Process] Use when the developer wants something explained or taught, or wants to know HOW TO REVIEW a change — by default the current working tasks + changes in context, or whatever the prompt names (a plan, a subsystem, a decision, a concept, a bug). AI derives WHAT to explain from the prompt and ALWAYS delivers a teacher-and-coach review guide, high level first then detail: what was done, a VISUAL MAP (system flowchart, domain ERD, sequence diagrams), the user stories and business rules with their REAL test-case IDs, a REVIEW PATH naming which files to open first and in what order with an exit criterion per stage, the technical concepts needed to follow it, how it works, why THIS solution, every alternative option with pros/cons, the trade-offs accepted, the blast radius, HOW TO TEST AND DEMO the change, the developer's decision levers, and written challenge prompts that provoke the reader to pressure-test the work. Works at ANY scope — from one line of code to the whole project: it SIZES the target into a scope tier, DECOMPOSES a large one into understanding groups, BREAKS the work into tasks before the first deep read, and ACCUMULATES the report group by group on disk so a huge explanation stays complete instead of thinning out. Writes the full report to a single combined markdown file (plans/reports/understand-*.md) that opens with a detailed summary section — or delivers it in full in chat when Step 3 finds no git-ignored directory for it — and always summarizes it in chat. Regardless of coding level. Never interrogates, never quizzes, never blocks.

日本語の概要は準備中です。原文の説明を表示しています。