1,630 件 ・ 関連度順
概要と使いどころ
Recommends against dexamethasone for glucocorticoid replacement in primary adrenal insufficiency (PAI) due to risk of Cushingoid side effects from difficult dose titration. Use when selecting a glucocorticoid for PAI management to avoid iatrogenic Cushing syndrome.
日本語の概要は準備中です。原文の説明を表示しています。
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level biomedical imaging covering X-ray, CT, MRI, ultrasound, nuclear medicine, optical imaging, and image processing for clinical and research applications.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level circuit analysis covering KVL, KCL, nodal and mesh analysis, Thevenin and Norton theorems, AC circuits, phasors, and frequency response.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level acoustics knowledge. Use when working with sound waves, acoustic propagation, resonance, standing waves, Doppler effect, room acoustics, ultrasound, noise control, musical acoustics, or architectural acoustics. Also use when the user mentions 'sound wave', 'decibel', 'frequency', 'resonance', 'standing wave', 'Doppler effect', 'acoustic impedance', 'reverberation', 'ultrasound', 'noise control', 'harmonics', or 'sound intensity'.
日本語の概要は準備中です。原文の説明を表示しています。
Use for multi-step / ambiguous / end-to-end work — refactor a whole module, drive a vague ticket to a verified result, plan+build+verify a migration; coordinates the reasoning chain across skills.
日本語の概要は準備中です。原文の説明を表示しています。
Prefab / Scene / Asset を壊さず編集する。preflight 診断 → dry-run 差分 → confirm + change_reason 監査 → runtime 検証の 4 段ゲートを 1 経路で踏む。 トリガー: パッチ適用、Prefab Variant 編集、`set_property` / `patch_apply` / `revert_overrides` を伴う変更全般。
Activates a structured decorator framework that modifies how Claude reasons, responds, and formats output. Trigger this skill whenever a prompt contains one or more markers prefixed with +++, such as +++Reasoning, +++StepByStep, +++Tone(style=formal), or any other +++ marker, regardless of what follows in the prompt. Also trigger when the user asks to activate, list, or clear decorators, references the prompt decorator framework, or uses phrases like "use decorator", "apply +++", or "what decorators are available". This skill must be active for any +++ marker to take effect.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my...
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my...
日本語の概要は準備中です。原文の説明を表示しています。
App Store and Google Play screenshot creation with exact platform specs. Covers iOS/Android dimensions, gallery ordering, device mockups, and preview videos. Use for: app store optimization, ASO, app screenshots, app preview, play store listing. Triggers: app store screenshots, aso, app st...
日本語の概要は準備中です。原文の説明を表示しています。
Use when simulating a technical interview to build confidence, expose reasoning gaps, and train structured communication under pressure.
日本語の概要は準備中です。原文の説明を表示しています。
Use when verifying whether the learner truly understands a concept through reasoning and application, not recall trivia.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the learner benefits from guided questioning to build reasoning and uncover misconceptions before receiving direct answers.
日本語の概要は準備中です。原文の説明を表示しています。
Run an offline ASO audit on canonical App Store metadata under `./metadata` and surface keyword gaps using Astro MCP. Use after pulling metadata with `asc metadata pull`.
日本語の概要は準備中です。原文の説明を表示しています。
Keep serialized build-in-public content continuous: read one canon file of season, arcs, beats and loops and say which narrative beat to advance next, so episodes chain into a series. Pairs with the episode adapter, which does the writing. Triggers: "/reality-show", "season state", "what arcs are open".
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.
日本語の概要は準備中です。原文の説明を表示しています。
Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: positioning, product launch, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget.
日本語の概要は準備中です。原文の説明を表示しています。
Use OpenAI Codex CLI as a peer collaboration partner — same standing as Claude, not a one-shot tool. Bring Codex in EARLY (ideation, framing decisions, stuck moments), not only for late peer-review. Hand it strategic context (target, research, draft, reasoning), iterate conversationally over ~3-8 turns, converge before surfacing to the human. Invoke when the user says "check / iterate / ideate with Codex" or "ask Codex" — and proactively when stuck between two reasonable framings, pressure-testing a load-bearing claim or structure, or about to ask the human to pick between options two agents could resolve.
日本語の概要は準備中です。原文の説明を表示しています。
Use when running the dev Grafana stack and/or the Playwright e2e suite against a *packaged* plugin zip (a release/RC artifact like `hydrolix-hydrolix-datasource-<ver>.zip`) rather than the working-tree `dist/`. Unpacks the package into a timestamped `dist_<timestamp>/dist` sandbox alongside copies of the compose artifacts, so the run is reproducible and the folder stays available to experiment with afterwards. Delegates stack bring-up to `stack-run` (frozen mode: read-only mount + `DEV=false` so the mage-watcher can't rebuild the packaged Go binary), verifies signature/version, runs the suite, and treats cleanup as optional — the sandbox is deleted only with the user's approval. Apply whenever the task is "test this plugin package / zip" or "run e2e against the built artifact".
日本語の概要は準備中です。原文の説明を表示しています。
Use when validating a packaged build of this Hydrolix Grafana datasource plugin against Grafana's official plugin-validator — the pre-release gate that catches missing metadata, unsigned/mis-signed archives, non-executable backend binaries, and packaging errors. Builds the plugin, zips `dist/` under the plugin ID, and runs `@grafana/plugin-validator` (npx, or docker as fallback). Apply for "validate the plugin", "is this zip release-ready", or before publishing / submitting a release artifact.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, running, or debugging Playwright e2e tests in this Hydrolix Grafana datasource plugin. Covers the docker-compose `playwright` service invocation, locator patterns for Grafana's react-select / Monaco editor / panel chrome, state-dependent interactions in QueryEditor, and timeout/retry expectations. Apply whenever a task touches `tests/*.spec.ts`, `tests/helpers.ts`, the `playwright` service in `docker-compose.yaml`, or the test results under `test-results/`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting, stopping, or inspecting the dev stack for this Hydrolix Grafana datasource plugin — Grafana (with the plugin bind-mounted), ClickHouse, Keycloak (OAuth), and the on-demand playwright runner. Covers `docker compose up` semantics, the `dist/` prerequisite, serving plugin artifacts from an alternate folder (any path, live or frozen, via an ephemeral compose override), switching Grafana versions, hot-reload behaviour, delve attach, log streaming, OAuth/anonymous auth, and ClickHouse fixture access. Apply whenever a task needs the plugin running locally, needs to reset the stack, or needs to debug why Grafana won't come up.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building this Hydrolix Grafana datasource plugin — frontend webpack bundle (`dist/module.js*`) or Go backend binary (`dist/gpx_plugin_*`). Covers the split between host-built frontend and container-built Go, when each needs an explicit rebuild, watch vs one-shot, and the verification chain (typecheck / lint / unit tests). Apply for any task that edits `src/**`, `pkg/**`, `Magefile.go`, `webpack.config.ts`, or that needs to confirm `dist/` matches the working tree before running e2e or the dev stack.
日本語の概要は準備中です。原文の説明を表示しています。