「rop」の検索結果

Expert-level electrochemistry knowledge. Use when working with electrochemical cells, electrode potentials, Nernst equation, electrolysis, batteries, fuel cells, corrosion, electroplating, or electroanalytical methods. Also use when the user mentions 'galvanic cell', 'electrolytic cell', 'electrode potential', 'Nernst equation', 'overpotential', 'Butler-Volmer', 'battery', 'fuel cell', 'corrosion', 'electroplating', 'cyclic voltammetry', or 'impedance spectroscopy'.

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

Expert-level thermodynamics knowledge. Use when working with heat, temperature, entropy, thermodynamic laws, heat engines, refrigerators, phase transitions, statistical mechanics, or thermodynamic cycles. Also use when the user mentions 'entropy', 'enthalpy', 'Carnot', 'heat engine', 'thermodynamic cycle', 'ideal gas', 'phase transition', 'Gibbs free energy', 'specific heat', 'thermal equilibrium', or 'second law'.

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

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

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

Plan, write, and maintain automated tests in any language, with worked examples in Python and JavaScript/TypeScript. Use this skill whenever the user wants to write or plan tests, apply TDD (red-green-refactor), structure unit tests with arrange-act-assert and given-when-then naming, choose between fakes, stubs, and mocks, set up dependency injection for testability, build integration tests with testcontainers, database seeding, or transaction rollback, write Playwright or Cypress end-to-end tests, use property-based testing with Hypothesis or fast-check, create pytest fixtures or factory_boy factories, review coverage or mutation testing, or triage flaky tests in CI. Also trigger for "test pyramid", "test trophy", "test isolation", "mocking", "snapshot tests", "golden files", "parametrized tests", "make the tests pass".

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

Create and publish a recurring client-facing deliverable — SEO or analytics monthly, project status report, audit results — as a branded live page with view tracking. Use when the user says "client report", "monthly report for", "status update for the client", "send this to my client". Not for one-off research shares (use report-publisher) or proposals (use proposal-tracker).

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

Turn research, analysis, or any markdown the agent just produced into a live, beautifully designed web report with a shareable tracked URL via ReportRoom. Use when the user says "publish this", "make this shareable", "turn this into a report", "put this on a page", or wants findings to live beyond the chat. Not for recurring client deliverables (use client-reporter), slide decks (use deck-publisher), or proposals that need view alerts (use proposal-tracker).

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

Aplica as cores de marca oficiais e tipografia da Anthropic a qualquer tipo de artefato que possa se beneficiar de um visual e sentimento do padrão Anthropic. Use quando diretrizes de cores de marca, guias de estilo, normas de design visual ou padrões de design corporativo se aplicarem.

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

Aplica as cores oficiais da marca Anthropic e tipografia a qualquer tipo de artefato que possa se beneficiar da identidade visual da Anthropic. Use quando diretrizes de cores da marca ou padrões de design, formatação visual ou padrões de design corporativo se aplicarem.

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

Método da Anthropic para treinar IA inofensiva através de auto-aprimoramento. Abordagem em duas fases - aprendizado supervisionado com auto-crítica/revisão, depois RLAIF (RL from AI Feedback). Use para alinhamento de segurança, redução de outputs prejudiciais sem rótulos humanos. Alimenta o sistema de segurança do Claude.

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

Estenda janelas de contexto de modelos transformer usando RoPE, YaRN, ALiBi e técnicas de interpolação de posição. Use ao processar documentos longos (32k-128k+ tokens), estender modelos pré-treinados além dos limites de contexto originais ou implementar codificações posicionais eficientes. Cobre embeddings rotativos, vieses de atenção, métodos de interpolação e estratégias de extrapolação para LLMs.

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

Load this skill whenever the project contains navigation components — primary navigation menus, dropdown menus, mega menus, breadcrumbs, pagination, mobile hamburger menus, or in-page jump navigation. Under no circumstances create navigation without proper landmark roles, keyboard support, and accessible labels. Absolutely always wrap navigation in <nav> with a unique aria-label.

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

Prefab / Scene / Asset を壊さず編集する。preflight 診断 → dry-run 差分 → confirm + change_reason 監査 → runtime 検証の 4 段ゲートを 1 経路で踏む。 トリガー: パッチ適用、Prefab Variant 編集、`set_property` / `patch_apply` / `revert_overrides` を伴う変更全般。

VRChat エコシステムツール（ModularAvatar / liltoon / VRCFury / AvatarOptimizer 等）の ナレッジを 4 フェーズで段階的に調査・検証し `knowledge/*.md` に再現可能な形で蓄積する。 ソースコード読解 → inspect 実測まで進めると confidence を `high` に昇格できる。 トリガー: 新しい VRChat コミュニティツールに初めて遭遇した、 既存ナレッジの confidence が low で作業に支障がある、 ユーザーから「このツールについて調べて」と依頼された場合。

医学证据等级排序与编排层 skill。当用户请求"证据等级 / GRADE / 证据排序 / 医学证据评估 / evidence grading / quality of evidence / 系统评价排序 / 临床证据排序 / 证据金字塔"时触发。本 skill 不直接调用 NCBI/Europe PMC/ClinicalTrials API,而是编排 6 个底层原子 skill(pubmed-eutils / europepmc-search / clinical-trials-v2 / aact-bulk-trials / bioc-fulltext-fetch / pubtator-entity-search)的召回结果,按 ChatGPT 推荐的证据金字塔(指南 > Meta > RCT > Cohort > Case-Control > Case Report)做 GRADE 自动评级,自动剔除 editorial / letter / comment。优先使用 BioMCP MCP server 做 fan-out(genomoncology/biomcp),无 BioMCP 时走自建 slow-path 兜底。

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

医学证据等级排序与编排层 skill - evidence grading orchestrator. 当用户请求"证据等级 / GRADE / 证据排序 / 医学证据评估 / 系统评价排序 / 临床证据排序 / 证据金字塔 / 给 PMID 打分 / Practice Guideline 优先 / Cochrane 优先 / 反向证据交叉验证 / evidence grading / quality of evidence / evidence pyramid / GRADE assessment / Cochrane review ranking / clinical evidence ranking"时,**调用本 skill 进行医学证据自动分级,自动选择最佳信息源**。本 skill 是编排层(L2)·不直接打 NCBI/Europe PMC/ClinicalTrials API,而是编排 6 个底层原子 skill(pubmed-eutils / europepmc-search / clinical-trials-v2 / aact-bulk-trials / bioc-fulltext-fetch / pubtator-entity-search)的召回结果,按证据金字塔(指南 > Meta > RCT > Cohort > Case-Control > Case Report)做 GRADE A/B/C/D 自动评级,自动剔除 editorial/letter/comment。优先使用 BioMCP MCP server 做 fan-out(genomoncology/biomcp);无 BioMCP 时走自建 slow-path 兜底。跨平台无锁(Claude Code / Codex / Gemini CLI)。

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

Create editable charts, diagrams, figures, posters, or slides from intent, data, or references.

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

Guidelines and strategies for constructing meaningful test suites, property-based tests, metamorphic relations, and fuzzing harnesses. Trigger when: - Designing verification bounds, writing tests, creating test invariants, or implementing validation gates. - Prompt contains: testing, test design, property-based testing, PBT, metamorphic testing, fuzzing, integration tests, E2E.

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

Structured Domain Modeling Architecture (SDMA) principles. Trigger when: - Designing domain models, building ologs (ontological graphs), verifying protocol equivalence, selecting schemas, or measuring architectural entropy. - Modeling structures using Category Theory, Coalgebra, or Information Theory. - Prompt contains keywords: sdma, olog, Category Theory, Coalgebra, Information Theory, entropy, schema, pullback, functor, monad.

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

Propose a UI change for human sign-off before building it. The default path deploys a rough live staging preview (with NUXT_PUBLIC_CROUTON_REVIEW=true) so the reviewer pins comments on the real running page. Use --static for the offline HTML/CSS mockup fallback (no deploy available, or speed over fidelity). Invoke for any task that adds/changes a .vue component, a layout, a page, or a theme.

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

The case-law chronicle of this repo's major failures — symptom, root cause, evidence, status, and the rule each battle minted — so nobody re-fights a settled battle or re-proposes a rejected fix. Use when a bug/incident looks familiar ("didn't this happen before?"), when you're about to propose an approach that may have been tried and rejected (e.g. shipping a migration from a package), when someone asks "why does rule X exist" / "why is done-by-lgtm a thing" / "what was incident 988", or when a bug-archaeology run hits the shallow-clone wall and needs the pre-June-2026 history. Trigger phrases: "has this broken before", "why can't packages ship migrations", "why did graduation fail", "why is the green-build lesson a rule", "what did we learn from incident NN". (For a live "build is green but the app is broken" symptom, start at crouton-diagnostics-index. NB keep this description free of any space-then-hash sequence — an unquoted YAML scalar treats space-hash as a comment start and silently truncates.)

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

At the close of an epic (or a difficult issue), post a postmortem roundup comment — what went well, what was hard (backed by evidence), and 1–3 concrete proposals to improve the skills/flows — then offer to turn accepted proposals into their own `workflow`-labeled tasks, and end with a `🔭 Next` handoff (a paste-ready next-session prompt + the next epic to start). Use at epic close, after the "verify the whole thing" rollup, or when asked to "do a retro", "postmortem this epic", "what did we learn", "how do we improve the workflow".

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

トリアージで影響ありと判定された spec-drift issue の rubric/schema/template を同期したいとき、propose(read-only)で最小 Edit 差分と pre-image hash を提案し apply で監査 PASS と明示承認後に allowlist 対象だけを適用したいときに使う。

アプリケーションに LLM API(OpenAI / Anthropic / Gemini 等)を組み込む際のコスト最適化・セキュリティ・運用の必須パターン集。 「AI機能を付けて」「AIで読み取り」「画像認識」「PDFから抽出」「OCR」「自動分類」「レコメンド」「AI連携」「OpenAI APIを使う」 「チャットボット」「LLMを組み込む」などの文脈で、新規アプリ・既存アプリを問わず必ず使用する。 ユーザーが「AI」と明示しなくても、非構造データ(画像/PDF/自由文)からの情報抽出・分類・判別の要件が含まれるなら必ずこのスキルを読むこと。 AI機能のコスト見積・APIキー管理・利用量ダッシュボードの設計・レビューでもトリガーする。 実測グラウンディング付きの費用試算が必要な場合は Skill llm-cost-simulator を併用。 既定スタック(社内業務アプリ、mvp-first)の必須スキルではない optional 群。上記の AI 要件が要件定義で明示された場合、 または app-orchestrator の要件フラグ「AI機能あり」で指示された場合のみロードする。

Pre-share leak scanner for Claude Code skills (or any folder). Scans BEFORE you publish for secrets (API keys, tokens, private keys, .env values, high-entropy strings), PII (emails/phones), local machine paths (C:\Users\<name>, /home/<name>, /Users/<name>, UNC, internal hostnames), and client/proper-noun names from a LOCAL private dictionary; also flags service-specific code (jira/github/gitlab/slack/salesforce/notion/linear/ stripe/aws/google) that should be split into a dedicated service plugin. Use when the user says "sanitize this skill", "before sharing a skill", "check for leaks", "is this skill clean", "is this safe to commit/publish/ open-source", "scrub secrets", "redact before commit", or "pre-push leak check". Cross-platform, stdlib-only Python, fail-closed.

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