1.1万 件 ・ 関連度順
概要と使いどころ
Use when implementing or reviewing SVG animation, path drawing, icon motion, logo animation, illustration motion, micro-interactions, CSS/SMIL/Framer Motion/GSAP choices, motion accessibility, or fallback behavior; Chinese triggers include SVG animation, path stroke, animation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, implementing, or reviewing frontend-to-backend API integration, typed API clients, REST/tRPC/OpenAPI client choices, auth refresh, API error mapping, upload flows, SSE/WebSocket/polling choices, CORS-facing frontend behavior, or cross-boundary loading/error states. Do not use for backend-only service architecture or TanStack Query cache policy alone; Chinese triggers include API integration, front-end and back-end joint debugging, typed API client, Interface error handling, SSE, WebSocket.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating, maintaining, debugging, or reviewing real-browser end-to-end tests with Playwright or Cypress, including Page Object models, CI artifacts, traces, flaky tests, cross-page visual regression, and critical user journeys such as login, payment, permissions, or CRUD. For layer planning or tests close to UI components, choose the matching testing workflow first; Chinese triggers include E2E, end-to-end testing, Playwright, Cypress.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for general frontend code review, PR review, merge-readiness assessment, architecture maintainability, type-safety, rendering/state risks, style consistency, testability gaps, or a cross-cutting review summary. Delegate deep security, accessibility, E2E, or performance investigations to their specialized skills; Chinese triggers include code review, code review, review.
日本語の概要は準備中です。原文の説明を表示しています。
Generate fantasy character names in zh-TW with original spelling and etymology, across human, elf, dwarf, orc/beastfolk, and halfling naming traditions. Use when the user needs a name for a character, NPC, party member, villain, shopkeeper, or monster, asks to think of, suggest, or rename such a character, names entities for a MUD/TRPG/game world or worldbuilding document, or writes lore, quests, presets, or seed data that require in-world personal names.
日本語の概要は準備中です。原文の説明を表示しています。
Run a deep code review across the manifold-csg crates
日本語の概要は準備中です。原文の説明を表示しています。
Run a deep code review across the manifold-csg crates
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an emergency medicine physician — risk-stratifying an undifferentiated chief complaint against a can't-miss diagnosis, deciding an ED disposition (discharge/observation/admit/transfer) under time and bed pressure, reasoning through EMTALA screening-and-stabilization obligations, or triaging a department under crowding/boarding load.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Elementary School Teacher — interpreting a running record or fluency check against grade-level benchmarks, deciding whether a struggling reader needs a Tier 2 intervention, running a self-contained classroom's daily schedule across multiple subjects, implementing (not writing) an IEP/504 accommodation with fidelity, or writing a parent-conference summary grounded in assessment data.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Economist — estimating a demand elasticity or causal treatment effect from observational or experimental data, building a cost-benefit or welfare analysis for a policy or pricing decision, forecasting a macro or market aggregate under stated assumptions, or stress-testing whether a "the data shows X" claim survives a confounding-variable check.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Electrical and Electronics Drafter — sizing a conductor and conduit for a panel or feeder circuit against NEC ampacity and fill tables, building a schematic/elementary diagram or one-line diagram on IEEE 315/ANSI Y32.2 symbols, cross-referencing wire numbers between a schematic and a panel wiring diagram, sizing a PCB trace against IPC-2221 current tables, or QC-checking an electrical drawing set before issuance.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Environmental Science Professor — deciding whether a field exercise crosses a weather/safety cancel threshold, building an NSF/EPA proposal budget, normalizing an interdisciplinary tenure case against the right benchmark, checking whether a mixed-methods field project needs IRB review, or handling a politically charged classroom topic without losing academic-freedom footing.
日本語の概要は準備中です。原文の説明を表示しています。
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 Registered Dietitian Nutritionist — calculating caloric/macronutrient needs for a clinical case, designing a medical-nutrition-therapy plan for a disease-specific condition (renal, diabetic, oncology), setting an enteral or parenteral feeding prescription, or screening/triaging malnutrition risk.
日本語の概要は準備中です。原文の説明を表示しています。
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 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 Digital Forensics Analyst — capturing volatile evidence before it's lost, creating and hash-verifying a forensic disk image, documenting chain of custody from point of seizure, correcting for clock skew and timezone mismatches when building a cross-source timeline, or identifying anti-forensic activity (log wiping, timestomping) in an investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a dental assistant — sequencing instrument transfer during a procedure, troubleshooting a retake-worthy radiograph before re-exposing the patient, tracing a failed sterilization-cycle indicator back to the affected instrument batches, or timing a chairside material mix against its working-time window across multiple prepped teeth.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a dental hygienist — full-mouth periodontal charting and staging, sequencing scaling and root planing across quadrants, deciding whether a finding needs escalation back to the dentist, or building a home-care compliance plan for a patient with active periodontal disease.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a DevOps/Site Reliability Engineer — designing deployment pipelines, setting SLOs/error budgets, responding to or reviewing an incident, or making infrastructure/reliability tradeoffs. Distinct from a backend software engineer role — this one owns the system's operational health across all services, not one service's feature code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Customer Success Manager — driving product adoption after the sale, assessing renewal/churn risk, handling an at-risk account, or deciding how to prioritize limited attention across a book of accounts.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Coil Winder, Taper, or Finisher — cross-checking a mechanical turn counter against an independent method rather than trusting it blindly, maintaining wire tension within a specified range rather than by feel, avoiding wire handling that risks invisible insulation damage, or performing post-winding electrical testing rather than relying on visual/mechanical inspection alone.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Computer Numerically Controlled (CNC) Tool Programmer — calculating stepover from a scallop-height/surface-finish spec instead of picking one by feel, deciding whether a toolpath needs a dry run before cutting material on an unfamiliar post-processor/machine pairing, verifying datum consistency across multiple part setups, or diagnosing why cycle time jumped after a "minor" parameter change.
日本語の概要は準備中です。原文の説明を表示しています。