「repo」の検索結果

Use when designing or reviewing Vue 3 + TypeScript project structure, SFC/component boundaries, composables organization, route composition, Pinia ownership, API/error/styling defaults, directives, or repository-wide Vue conventions. Prefer narrower skills for forms, data fetching, tests, accessibility, virtualization, animation, or security deep dives; Chinese triggers include Vue 3 project specification, Vue component architecture.

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

Use when designing or reviewing React + TypeScript project structure, feature/module boundaries, component architecture, hooks organization, routing composition, state/API/error/styling defaults, or repository-wide React conventions. Prefer narrower skills for forms, data fetching, tests, accessibility, virtualization, animation, or security deep dives; Chinese triggers include React project specification, React component architecture.

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

Use when diagnosing frontend build failures, runtime errors, UI anomalies, API/data problems, white screens, request failures, or unexplained production exceptions; Chinese triggers include debugging, debug, troubleshooting, positioning, error reporting, exceptions, white screens, request failures.

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

Use when creating, configuring, reviewing, or debugging TypeScript project standards across frontend apps, libraries, SDKs, CLIs, monorepo packages, tsconfig, strictness, module/moduleResolution, path aliases, project references, declaration files, package exports, public API types, DTOs, advanced generics, discriminated unions, type guards, type narrowing, or type-level regressions. Prefer framework project skills for React/Vue/Next/Nuxt component architecture; Chinese triggers include TypeScript project specification, TS project specification, TypeScript type safety, type modeling, generics, discriminative unions, type narrowing, tsconfig, declaration files.

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

Upgrade the vendored NeMo-Skills slice to a newer upstream commit. Use when the user asks to "bump vendored", "sync NeMo-Skills", "update vendored sha", "upgrade NS", or wants to pull a specific upstream fix. Inside the sgl-eval repo.

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

Add a new benchmark to sgl-eval by vendoring its NeMo-Skills dataset module and registering it in `_TABLE`. Use when the user asks to "add <benchmark>" / "support <benchmark>" / "register <benchmark>" inside the sgl-eval repo.

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

Use OpenClaw Manager (OCM) safely and correctly for OpenClaw environment lifecycle work, runtime installation/builds, release-shaped local builds, upgrades, migration/adoption, cloning existing user state, service supervision, gateway logs, dev worktrees, plugin testing, model/provider smoke tests, TUI/dashboard checks, cleanup, and concise reporting. Use whenever Codex is asked to use OCM, manage OpenClaw envs/runtimes/services, test OpenClaw with OCM, reproduce existing-user or new-user flows, or avoid breaking user state while working with OpenClaw.

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

Validate OpenClaw release candidates through OCM using the built OpenClaw artifact, a broad reusable scenario matrix, copied existing-user state, clean new-user state, concise pass/fail reporting, and focused failure notes. Use when asked to test OpenClaw origin/main, release readiness, upgrade behavior, plugins, services, channels, doctor recovery, packaging, or broad release risk.

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

Use when a task needs the judgment of an Emergency Management Director — activating and staffing an EOC for a developing hazard, sequencing a disaster declaration and FEMA Public Assistance/Individual Assistance request, sizing shelter and resource needs against real population and capacity numbers, designing or critiquing a tabletop exercise, or writing an after-action report and improvement plan.

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

Use when a task needs the judgment of an Environmental Compliance Inspector — reviewing discharge monitoring reports or emissions data against permit limits, classifying a facility's hazardous waste generator status, calculating a penalty for a documented violation, deciding whether an exceedance warrants a Notice of Violation versus informal correction, or scoping a multimedia (air/water/waste) inspection.

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

Use when a task needs the judgment of an executive administrative assistant — triaging a stacked calendar against competing priorities, deciding what reaches an executive versus what gets redirected, reconciling a multi-city travel itinerary or expense report, drafting on an executive's behalf within a delegated-authority boundary, or handling a scheduling conflict across time zones.

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

Use when a task needs the judgment of a Document Management Specialist — designing or auditing a records retention schedule, planning a content migration between DMS platforms (SharePoint, OpenText, Documentum, M-Files), reconciling migrated vs. source document counts, resolving a version-control or legal-hold conflict, or scoping a defensible-disposal (ROT) cleanup.

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

Use when a task needs the judgment of a Cytogenetic Technologist — choosing a culture/harvest protocol and band resolution for a specimen, applying ISCN clonality criteria to a metaphase count, deciding between karyotype, FISH, and chromosomal microarray for a clinical question, or writing and QCing an ISCN-formatted cytogenetics report.

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

Use when a task needs the judgment of a detective/criminal investigator — developing and stress-testing a case theory against alternate explanations, reconciling conflicting timestamps (DVR, cell tower, witness-reported) into a defensible timeline, structuring a suspect/witness interview using a non-accusatorial method, drafting a probable-cause affidavit, or evaluating whether a confession or eyewitness identification is being treated with the right level of certainty.

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

Use when a task needs the judgment of a Crushing/Grinding Machine Operator — recognizing that classifier cut point, not mill residence time alone, determines what reports to finished product in a closed-circuit grinding operation, monitoring circulating load as a distinct diagnostic variable, matching grinding media size to the target size reduction, or verifying product size via actual sieve/laser analysis rather than mill parameters.

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

Use when a task needs the judgment of a Data Warehousing Specialist — defining the grain of a fact table before modeling it, choosing a slowly changing dimension (SCD) type for a dimension attribute, designing an incremental ETL/ELT load strategy against a full-refresh alternative, resolving a conformed-dimension conflict across source systems, or diagnosing why a BI report's numbers don't reconcile to the source system.

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

Use when a task needs the judgment of a professional dancer — preparing for a company audition, managing rehearsal load against injury risk, deciding whether to dance through pain or report it, negotiating a casting or return-to-dance plan with a rehearsal director, or critiquing a performance for technical and artistic fidelity to the choreography.

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

Use when a task needs the judgment of a cytotechnologist — screening a gynecologic (Pap test) slide and applying Bethesda System criteria, assessing non-gynecologic specimen adequacy (FNA rapid on-site evaluation, body fluid, brushing) against the relevant reporting system, deciding whether a finding can be signed out independently or must be referred to a pathologist, or auditing screening quality metrics (ASC:SIL ratio, rescreen concordance, workload compliance). A reasoning aid, not a substitute for a certified cytotechnologist or pathologist signing out an actual case.

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

Use when a task needs the judgment of a Clinical Nurse Specialist — diagnosing why a unit-level outcome metric (CLABSI, falls, pressure injury) is off benchmark, designing and scaling a practice-change pilot, appraising whether a new clinical guideline actually fits the local population, writing a quarterly outcomes report to nursing leadership, or coaching staff nurses through a new protocol without formal authority over them. US hospital/health-system default; state nurse practice acts vary. A reasoning aid, not clinical or legal advice.

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

Use when a task needs the judgment of a corrections sergeant or shift supervisor — mandating overtime to restore a post below minimum staffing, reviewing and countersigning a subordinate's use-of-force report, running progressive discipline for a line officer, assuming incident command during a multi-officer response, or handling a first-level inmate grievance.

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

Use when a task needs the judgment of a Coroner or medicolegal death investigator — determining whether a death is reportable/jurisdictional, distinguishing cause of death from manner of death, estimating a postmortem interval from scene findings, deciding whether an autopsy or toxicology screen is warranted, or completing a death certificate under scrutiny.

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

Use when a task needs the judgment of a Compliance Manager — sizing and defending a compliance program's headcount/budget, deciding build-vs-buy on monitoring or case-management technology, choosing a centralized-vs-embedded staffing model, translating a new regulatory obligation into a costed resourcing ask, or reporting program coverage to executives/the board.

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

Use when a task needs the judgment of a doctoral-level Clinical or Counseling Psychologist — building a psychological test battery to answer a referral question, interpreting a WAIS/MMPI/PAI profile against validity indices, working a differential diagnosis (e.g. ADHD vs. anxiety-driven inattention, depression vs. early dementia), or writing a feedback-session-ready diagnostic formulation report.

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

Use when a task needs the judgment of a Chief Data Officer — resolving conflicting metric definitions across dashboards, deciding whether a dataset should be retained or purged, assigning data ownership for a system feeding regulatory or board reporting, sizing a privacy/breach risk against a proposed data collection, or auditing data readiness before an AI/ML initiative kicks off.

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