「support」の検索結果

Tells you what CARLA on UE 5.5 (branch ue5-dev) cannot do that UE 5.8 (ue58-dev) can, so you do not attempt an unsupported workflow there — no Autoware integration, no ROS 2 middleware choice (FastDDS only), no DLSS or ray-traced-lens camera, no OFPA large-map mount so Town12/13/15 load black, and a few missing World/Actor methods. Also states what is identical, so the ue58 skills can be used directly for everything else. Use when working against a 5.5 checkout, when a ue58 skill's step has no counterpart, or when deciding whether a feature request is possible on 5.5 at all.

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

Runs a single ScenarioRunner Python scenario (or a whole group) against a running CARLA server — FollowLeadingVehicle, ControlLoss, DynamicObjectCrossing, SignalizedJunctionLeftTurn and the rest of srunner/examples — in sync or async mode, with result output, recording and manual/agent control of the ego. Lists what is runnable on the checked-out branch and on the loaded map. Use when the user asks to "run a scenario", "test FollowLeadingVehicle", "list scenarios", "run a CARLA traffic scenario", or reports a scenario that is "not supported".

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

Adds a new ROS 2 message type to CARLA's native ROS 2 interface — the hand-written POD struct under LibCarla/source/carla/ros2/types/msg, its Fast-CDR serialize/deserialize pair, the RIHS01 type hash computed in Docker, the CdrTopicInfo registration and the type-hash test. Use when the user asks to "add a ROS message type", "support sensor_msgs/X in CARLA", "add a carla_msgs type", "why is my type hash warning appearing", or needs a message CARLA does not publish yet. There is no IDL codegen — every step is manual.

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

Builds CARLA (branch ue4-dev, Unreal Engine 4.26) from source on Linux end-to-end — UE4 fork, the Carla server (editor C++ modules), the LibCarla Python client wheel, and content — then verifies them against a from-source server. Optionally builds the native ROS 2 interface in (ROS2=1 → --ros2, Fast-DDS/CycloneDDS/Zenoh), which is compile-time only and cannot be enabled later. Use when the user asks to "build CARLA from source", "compile CARLA ue4-dev", "set up CARLA on Ubuntu (incl. 24.04)", "build CARLA with ROS2 support", or "produce a CARLA server + client wheel". Cooking a distributable Dist/ package is a separate skill (package-carla-ue4); running the build is run-carla-server.

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

Book reservations through Google Maps using browser automation. Searches for businesses, checks availability, and completes bookings via "Reserve with Google" or 3rd-party providers (OpenTable, Resy, Vagaro). Supports restaurants (primary), salons, fitness, healthcare. Use when user wants to book, reserve, or schedule at a business found on Google Maps.

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

Hermes Agent (Nous Research の AI CLI エージェント)。インストール、 CLI コマンド (chat, model, gateway, config, cron, webhook, mcp, skills, profile, hermes pm)、 Configuration (Terminal Backends, Memory, TTS / STT, Auxiliary Models, Compression, Display, Local Models llama.cpp, Egress / Secrets)、 Features (Tools, Skills, Hooks, Delegation, Kanban, Cron, Voice Mode, Personality, Context Files)、 Messaging Gateway (Platform Support, Bot Mode, Connectors)、Security、Architecture、 Hermes Desktop、Plugin Catalog、Profiles、Developer Guide、Nous Portal (Tool Gateway)。

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

Generate Skills from HTTP MCP servers with async job patterns (submit/status/result). Use when converting MCP specifications (.mcp.json) into reusable Skills using mcp_tool_catalog.yaml. Supports --lazy mode for context-saving generation. Also use for calling async MCP tools via JSON-RPC 2.0 with session-based polling.

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

Check, from the employer's side, what has been put in writing before a paid Otameshi Tenshoku assignment starts under gyomu-itaku: item by item whether the deliverable, delivery date, fee and how it is calculated, payment due date, who pays, out-of-scope work, revision limits, company support, rights, confidentiality and termination are stated in a contract, purchase order or email rather than in chat or by word of mouth, count the days from delivery to payment, and find pay tied to satisfaction or hiring, unpaid or unlimited revisions and one-sided termination. Use when a hiring manager, recruiter or small-business owner is about to offer terms to a candidate, has been asked by a candidate what is still unwritten, or needs the conditions written for a platform contract screen; do not use to judge whether the terms are lawful or the fee fair, to compute withholding or consumption tax, for employment contracts, or to sign, send or conclude the contract on the user's behalf.

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

Review and revise Japanese job-application documents (entry sheets, rirekisho, shokumu-keirekisho) by checking each answer against the question asked, the stated character limit, and the evidence the applicant can actually support, then propose concrete rewrites the applicant decides on. Use when a user wants an ES or resume answer critiqued, tightened, or drafted from their own experience; to assemble a whole shokumu-keirekisho from an experience inventory, use resume-draft instead; do not use to invent experience, to judge pass or fail probability, or to submit an application.

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

Draft or review an employer's Otameshi Tenshoku listing so a candidate can decide whether to apply: check item by item that the work, deliverable, out-of-scope tasks, required experience, support, hours, schedule, location, compensation, contract form and payment timing are stated, find open-ended, unpaid-company-work, guarantee, personal-attribute and unverifiable wording, and confirm that the hours, weekly availability, period, rate and budget hold together. Use when a hiring manager, recruiter or small-business owner wants a listing written from a plan, wants an existing draft or published listing reviewed before or after posting, or wants to know why applications are not coming; do not use to design the work itself (trial-work-design), to reply to applicants (applicant-reply), to state market rates, legal, tax or service conditions from memory, or to post or update the listing on the user's behalf.

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

Transform review analysis into constructive feedback with actionable improvements. Mentor/shepherd mode - strict but supportive. Use for "give constructive feedback", "shepherd this paper". 旧名 review-shepherd。

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

Detects focal chromatin loops (point interactions / corner-dots) in balanced Hi-C and Micro-C contact maps and aggregates/validates a loop set. Covers de-novo calling with cooltools dots (HiCCUPS-style 4-background local enrichment with lambda-chunked FDR), chromosight (template-correlation), and Mustache (scale-space blob detection); aggregate peak analysis (APA) via cooltools pileup for confirmation; the depth/resolution prerequisite (de-novo needs ~5-10kb resolution = hundreds of millions to billions of valid pairs); consensus across callers and convergent-CTCF support as validation; and differential loops via union anchors plus chromosight quantify. Use when calling chromatin loops or dots from a cooler, deciding whether a map is deep enough to call de-novo vs running APA on known CTCF/cohesin anchors, building an aggregate peak pileup, comparing loops across conditions, or validating loop calls. For HiChIP/PLAC-seq/PCHi-C protein-anchored data use FitHiChIP/MAPS, not dots.

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

Analyzes alternative splicing at single-cell resolution. The first decision is library chemistry — 10X 3' is fundamentally limited (RT primes from poly-A, R2 falls in 3' UTR, <0.1 junction read per cell per AS event). Plate-based full-length methods (Smart-seq3, FLASH-seq, VASA-seq, STORM-seq) and single-cell long-read (MAS-Iso-seq, scISOr-Seq2) are the chemistries that give per-cell isoform structure. Tools include MARVEL (R, Smart-seq integrated), BRIE2 (Bayesian PSI with regulatory features and ELBO_gain test), scQuint (junction-cluster, plate-based; not for 10X), SpliZ (annotation-free Z-score), Psix (graph-smoothness regulated AS), and Sierra (alternative polyadenylation, often confused with AS). Use when analyzing isoform usage in scRNA-seq, identifying cell-type-specific splicing, or determining whether scRNA-seq chemistry supports splicing analysis at all.

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

Quantifies alternative splicing as PSI (percent spliced in) from RNA-seq using rMATS-turbo (BAM-based event), SUPPA2 (TPM-based event), MAJIQ V3 (LSV-based Bayesian), leafcutter (annotation-free intron clusters), VAST-TOOLS (cross-species with microexon support), Shiba (junction-imbalance-corrected, 2025 SOTA at low coverage), or IRFinder-S (intron retention coverage-aware). Distinguishes the five canonical event classes (SE, A5SS, A3SS, MXE, RI), special classes (microexons, exitrons, AFE/ALE), intron retention subtypes (canonical RI vs detained introns), and applies effective-length normalization. Use when measuring splice-site usage or isoform inclusion ratios from short-read RNA-seq.

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

Read, write, and convert multiple sequence alignment files using Biopython Bio.AlignIO. Supports Clustal, PHYLIP, Stockholm, FASTA, Nexus, and other alignment formats for phylogenetics and conservation analysis. Use when reading, writing, or converting alignment file formats.

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

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

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

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.

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

Genera tickets profesionales de soporte para Meta Business Suite / WhatsApp Business API optimizados para recibir prioridad URGENTE 24hr resolution. Úsala SIEMPRE que el usuario mencione crear un ticket a Meta, escalar un caso WABA, apelar un ban o restricción, reportar un false positive, abrir caso de soporte WhatsApp Business, problema de onboarding, rechazo de template, errores de Cloud API, OTP delivery, verification stuck, BM restricted, display name rejection, o cualquier issue de una WhatsApp Business Account. También activa cuando el usuario dice frases como "ayúdame a redactar un caso para Meta", "necesito reportar esto a soporte", "hay que escalar esto a WhatsApp", "ticket para Meta", o describe un problema de una cuenta de cliente de Vambe sin pedir ticket explícitamente pero claramente necesita uno. También activa ante preguntas del tipo "¿cómo apelar esto?" o "¿qué hago si Meta dice X?" relacionadas con WABA, BM o verificación.

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

Migrate supported instruction files, skills, agents, and MCP config into Codex project and global files.

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

Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns.

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

Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.

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

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has been paged at 3am for a factory class that wrapped one function: question whether the task needs to exist at all, reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full, ultra. The default is full. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests such as general knowledge, prose, translation, summaries, recipes.

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

Targeted deep research to fill a specific gap in an existing thesis. Use when user says "deepen", "flesh out", "expand on", "fill in", or specifies a thesis section to improve. Also supports --sync-metrics mode — detects stale financial metrics across every in-scope analytical section of a thesis (not just Key Metrics or Summary) and coherently updates every sentence that depends on them, using a Key-Metrics-table / FMP / web-search waterfall. Use when user says "sync metrics", "update the numbers throughout the note", or "fix stale figures across the whole thesis". The batch form `--sync-metrics --all-flagged` syncs every thesis flagged by the latest `/numbers --all-open` in one operation — detection fanned out to capped READ-ONLY agents, one consolidated confirmation gate, direct sequential writes (agents never write).

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

Targeted deep research to fill a specific gap in an existing thesis. Use when user says "deepen", "flesh out", "expand on", "fill in", or specifies a thesis section to improve. Also supports --sync-metrics mode — detects stale financial metrics across every in-scope analytical section of a thesis (not just Key Metrics or Summary) and coherently updates every sentence that depends on them, using a Key-Metrics-table / FMP / web-search waterfall. Use when user says "sync metrics", "update the numbers throughout the note", or "fix stale figures across the whole thesis". The batch form `--sync-metrics --all-flagged` syncs every thesis flagged by the latest `$numbers --all-open` in one operation — detection fanned out to capped READ-ONLY agents, one consolidated confirmation gate, direct sequential writes (agents never write).

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