「ros」の検索結果

Cross-compile Cadmus for Kobo e-reader devices (ARM Linux). Use this when asked to build a Kobo release, cross-compile for ARM, or prepare a device binary.

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

Structured retrospective after completing a delivery increment or diamond. Captures learning for continuous improvement.

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

Build .NET AI agents and multi-agent workflows with Microsoft Agent Framework using the right agent type, threads, tools, workflows, hosting protocols, and enterprise guardrails.

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

Use the open-source free `Roslynator` analyzer packages and optional CLI for .NET. Use when a repo wants broad C# static analysis, auto-fix flows, dead-code detection, optional CLI checks, or extra rules beyond the SDK analyzers.

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

Builds currency hedging models with rolling forward programs, option-based strategies, and cross-hedge analysis for international portfolios. Use when designing hedge programs, analyzing hedge ratios, or evaluating FX protection costs.

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

Coordinates fund regulatory requirements across SEC, AIFMD, and local jurisdiction registration, reporting, and compliance obligations. Use when managing fund compliance, navigating regulatory registration, or ensuring cross-border compliance.

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

Evaluates trade finance structures with letters of credit, supply chain financing, and receivables factoring for cross-border commerce. Use when analyzing trade finance, evaluating LC structures, or assessing supply chain financing.

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

Evaluates regulatory differences across jurisdictions with comparative framework analysis and optimal domicile selection. Use when analyzing regulatory environments, comparing jurisdiction frameworks, or selecting fund domiciles.

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

Evaluates multi-jurisdictional restructuring with Chapter 15 recognition, COMI analysis, and parallel proceeding coordination. Use when analyzing cross-border insolvency, assessing jurisdiction selection, or coordinating multi-country restructurings.

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

Design a rifle-scope reticle from a plain-language description and emit it as a BallisticCalculator `.reticle` file (BXml) plus a rendered SVG preview. Covers the complete `.reticle` element/attribute specification, reticle design principles (mrad vs MOA subtension, FFP/SFP, stroke-weight hierarchy, hash-mark ladders, christmas-tree wind holds, clutter budget, BDC anchors) and worked, verified patterns for duplex, mil-dot, hash-ladder, christmas-tree, chevron, circle-dot, dense-grid and rangefinding-stadia reticles. Also covers reproducing an existing commercial reticle from its manufacturer's technical data sheet. Use this skill whenever the user wants to create, modify, review or render a scope reticle, crosshair, mil-dot / MOA grid, holdover ladder, christmas tree, BDC ladder or rangefinding stadia — including any mention of a `.reticle` file, `ReticleDefinition`, `ReticleDrawController`, `SvgCanvasFactory`, or "draw me a reticle", and including requests to clone or model a named commercial reticle (Horus H58/H59, TReMoR, Mil-C, MOAR, Tremor3, EBR, and the like). Trigger it even when the user only says something like "make a crosshair with 0.2 mil hashes out to 5 mils" or "turn this reticle picture into a file", and trigger it before hand-writing reticle XML or hand-rolling reticle geometry, because the file format silently ignores misspelled attributes and mis-cased booleans.

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

Turn a raw product idea into build-ready docs — one doc per EPIC with locked decisions, exact API contracts, a story-by-story priority plan, and an execute.md handoff Claude can build from across sessions. Gets the clarity by interrogating the user through a roster of expert personas that grill, counter, and refuse to flatter. Use to ideate, validate, scope, architect, or plan a product, feature, startup, or app before any code is written. Invoke by persona name or acronym to summon one expert, or with no argument to run the full lifecycle end to end.

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

Session-start lifecycle hooks for cross-plugin dependency resolution. Creates symlinks so cross-package references work in cached plugin environments.

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

Hunt Insecure Direct Object Reference (IDOR) — test horizontal and vertical privilege escalation across user IDs, org IDs, tenant boundaries, and unguessable identifiers. Use when the user has an API endpoint with an identifier in the path/body that may be tested for unauthorized cross-user access.

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

Find and fix broken internal links, dead external URLs, stale imports, missing cross-references, and orphaned files. Ensures all project references remain valid and up-to-date. Use when documentation contains broken internal links, external URLs return 404 errors, import statements reference moved or deleted modules, cross-references between files are out of sync, or files exist but are never referenced anywhere in the project. Also use in index mode for a directory of markdown notes with a designated index, such as an agent-memory store, where an orphan is a file the index does not link to.

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

Research the etymology of a word by tracing proto-language roots, identifying cognates across language families, documenting semantic drift with dated attestations, and flagging folk etymologies. Use when investigating word origins, comparing cognate sets across related languages, charting historical meaning changes, or debunking popular but unsupported origin stories.

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

Cross-session shared memory for agents. Use at session start to load the persistent bias-log via `mcp__memex__recent_observations`, mid-session to search prior context with `mcp__memex__search`, and immediately when a bias surfaces to log a new `observation` via `mcp__memex__add`. The six-layer reconstruction trail (raw → embedded → indexed → graphed → curated → reflexive) means memex stores facts AND the agent's own reasoning patterns across sessions. Prefer querying memex before re-deriving prior architectural decisions; re-derivation is itself evidence that the trail is incomplete.

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

Field identification of minerals and ores using hardness, streak, luster, cleavage, crystal habit, and simple chemical tests. Covers the systematic elimination methodology, Mohs scale application, and common ore indicators for precious metals, gemstones, and industrial minerals. Use when encountering an unknown rock or mineral specimen, when prospecting and assessing whether a site shows valuable mineral indicators, when distinguishing ore-bearing rock from barren rock in the field, or when building geological literacy through systematic observation.

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

Establish and maintain longitudinal baselines of CLI binary contents across versions. Covers marker selection by category (API / identity / config / telemetry / flag / function), weighted scoring, threshold-based system-presence detection, and per-version baseline records. Use when tracking a feature's lifecycle across releases, when probing for dark-launched or removed capabilities, or when verifying that a scanning tool itself still catches known-good markers on old binaries.

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

Instrument applications with OpenTelemetry for distributed tracing, including auto and manual instrumentation, context propagation, sampling strategies, and integration with Jaeger or Tempo. Use when debugging latency issues in distributed systems, understanding request flow across microservices, correlating traces with logs and metrics for root cause analysis, measuring end-to-end latency, or migrating from legacy tracing systems to OpenTelemetry.

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

Alluvial gold recovery using panning, sluicing, and classification. Covers site reading (geological indicators, stream dynamics, pay streak location), panning technique, sluice box operation, and responsible extraction practices. Use when prospecting in an area with known or suspected alluvial gold deposits, sampling a stream to test for gold presence, maximizing recovery during recreational panning, or assessing a site's gold potential before investing more effort.

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

Evolve an existing team composition by refining its structure in-place or creating a specialized variant. Covers assessing the current team against template and coordination patterns, gathering evolution requirements, choosing scope (adjust members, change coordination pattern, split/merge teams), applying changes to the team file and CONFIG block, updating version metadata, and synchronizing the registry and cross-references. Use when a team's member roster is outdated, coordination pattern no longer fits, user feedback reveals workflow gaps, a specialized variant is needed alongside the original, or agents have been added or removed from the library affecting team composition.

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

Evolve an existing skill by refining its content in-place or creating an advanced variant. Covers assessing the current skill, gathering evolution requirements, choosing scope (refinement vs. variant), applying changes, updating version metadata, and synchronizing the registry and cross-references. Use when a skill's procedure steps are outdated, user feedback reveals gaps, a skill needs a complexity upgrade, an advanced variant is needed alongside the original, or related skills are added and cross-references are stale.

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

Evaluate and compare levitation mechanisms for a given application through a structured trade study. Covers magnetic (passive diamagnetic, active feedback, superconducting), acoustic (standing wave, phased array), aerodynamic (hovercraft, air bearings, Coanda effect), and electrostatic (Coulomb suspension, ion traps) mechanisms. Use when selecting the most appropriate levitation approach for transport, sample handling, display, bearings, or precision measurement applications.

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

Design terminal output for a CLI tool with chalk colors, Unicode glyphs, multiple verbosity levels (human, verbose, quiet, JSON), and consistent voice rules. Covers color palette selection, status indicator design, reporter function architecture, ceremony/narrative output variants, and cross-terminal compatibility. Use when building a new CLI reporter module, adding warm narrative output to an existing tool, standardizing output across multiple commands, or designing machine-readable JSON alongside human-readable text.

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