「transit」の検索結果

Use when completing a plan, finishing a development branch, wrapping up a session, or at any natural transition between work phases — reviews skill-bus telemetry to identify subscription gaps and suggest improvements

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

Format, create, and update concise XQUIC pull request bodies and review-state transitions. Use when asked to prepare or edit an alibaba/xquic PR body, create a draft PR from an already-pushed branch, update a PR after code changes pushed a new head, or move a validated draft toward review.

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

Assist in designing optimal DP states and transitions

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

Conditional edge routing and state-based transitions for LangGraph workflows

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

Migrate Java EE javax.* imports to Jakarta EE jakarta.* namespace. Use when upgrading to Spring Boot 3.x, migrating javax.persistence, javax.validation, javax.servlet imports, or fixing compilation errors after Jakarta EE transition. Covers package mappings, batch sed commands, and verification steps.

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

Model OR-Tools paired pickup-and-delivery routing problems, including PDPTW, dial-a-ride, paratransit, patient transport, and courier jobs with same-vehicle pairing, precedence, capacity, optional connected service, rider time windows, and vehicle shifts.

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

Build OR-Tools RoutingModel vehicle-routing models with transit matrices, dimensions, capacity constraints, time windows, optional visits, invalid-arc handling, search parameters, and route extraction.

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

Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes.

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

You are a code migration expert specializing in transitioning codebases between frameworks, languages, versions, and platforms. Generate comprehensive migration plans, automated migration scripts, and

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

Read-only audit of `.tex`, `.qmd`, or `.md` text for AI-voice tells — boilerplate transitions ("Moreover", "Furthermore", "It is important to note that"), AI-cliché lexicon ("delve", "navigate the complexities", "tapestry", "robust framework"), em-dash overuse, symmetric paragraph shapes, tricolon abuse, hedging stacking, "not only X but also Y" frames, and formulaic openers. Produces a report; does NOT rewrite. Use when user says "humanize", "does this sound like AI?", "check for AI tells", "de-AI this draft", "remove AI voice", "audit my prose for sycophancy", or before journal submission / posting a working paper.

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

Character creation, protagonist/antagonist design and dramatic conflict for scripts (人物/对手/冲突) — merged from Lajos Egri (three-dimensional character, orchestration, unity of opposites, pivotal character, rising vs static vs jumping conflict, transition), William Indick's Psychology for Screenwriters (Freud, Erikson, Jung archetypes, Campbell/Murdock hero journeys, Adler, Rollo May), Robert McKee (characterization vs true character, dimensions, gap, antagonism principle), Neill Hicks (character invocation, self-concept, cognitive dissonance, five conflict focuses, Maslow), Lisa Cron (desire vs misbelief), and Lu Jun (人物要活八要, 对手要强, 给对手一把刀, 最强的对手是自己, 不许请祥云). Use when building a protagonist, an antagonist or a cast, when a character feels flat or acts out of character, when conflict stalls or jumps, when a villain is too weak, when designing an arc or motive, or when diagnosing melodrama.

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

Scene and sequence craft (场景/段落/细节/道具/悬念/情趣) — merged from Robert McKee's scene design and five-step scene analysis (value turn, beats, text/subtext, turning points, pacing, image systems), McKee's Dialogue scene types (balanced, comic, asymmetric, indirect, reflexive, minimal), Syd Field's sequence and scene elements, Neill Hicks (less is more, enter late leave early, energy), Richard Walter (action over talk, small gestures, avoid phones/cars/restaurants, list twelve alternative locations), Wendy Henson (action paragraphs, transitions, story-doing), Julian Hoxter (scene beats, objectives and tactics), Mei Feng's value test, and Lu Jun's chapters 意趣要足 (suspense, delay, wit), 细节要妙, 道具要精, 场景要当. Use when writing or fixing a single scene, choosing a location, building a sequence, planting a prop or detail, designing suspense and delay, cutting a scene that "nothing happens" in, or turning talk into action.

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

Analyze a public or local reference video, isolate a time range, deconstruct its layout, motion, timing, and transitions, then build an original verified motion replica with reusable templates and final MP4 QC. Use when the user says 复刻这个视频效果, 参考这个视频做同款动效, 拆解前 N 秒, 还原方框/连线/卡片动画, or provides a video or URL as a motion reference rather than asking to copy its footage or script.

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

Create dark cinematic SaaS/product motion videos in the Presenton-like "magic UI" style: black starfield stage, bottom purple glow, large kinetic type, cyan-to-magenta CTA buttons, prompt cards, floating UI templates, integration badges, model rings, export objects, speed-blur transitions, and short product capability arcs. Use when the user asks for "这种风格", "同款风格", dark SaaS promo, AI product demo, magic UI product video, or a style-level creation inspired by a reference video. Do not use for pixel-level or frame-accurate replication; use rn-replica-qc first for that.

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

Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding. Use when the user asks about quality gates, milestone checks, phase transitions, approval steps, go/no-go decision points, or preventing cascading errors across a multi-step workflow. Produces acceptance criteria checklists, automated CI gate configurations, manual sign-off requirements, and conditional review rules for scenarios such as security changes, API changes, or database migrations.

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

State, resume, reconstruction, job-lifecycle, transition, and flow-state mechanics for the Data Science and Engineering Coach. Loaded by the coach; not a user entry point.

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

Assemble ordered frames or clips with narration and optional synchronized scene transitions into an MP4 via FFmpeg

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

Jira issue workflows for search, issue updates, transitions, comments, field discovery, and interactive credential setup via the Jira REST API. Use when you need to configure Jira access, search with JQL, inspect an issue, create or update work items, move an issue between statuses, post comments, or discover required fields for issue creation.

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

Drive Unity 6.3 LTS character animation with Animator Controllers: states, transitions, parameters, blend trees, animation layers, and humanoid Avatar IK. Use when wiring an Animator, setting parameters from script (SetFloat/SetBool/SetTrigger), building blend trees, or when the user mentions Animator, Mecanim, state machine, blend tree, or .controller.

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

Set up and debug a Phaser 4 game: the Game config, the Scene lifecycle (init/preload/create/update), the asset loader, cameras, and cross-scene communication. Use when building or debugging a Phaser game — when the user mentions Phaser, Phaser.Game, Phaser.Scene, preload/create/update, this.load, this.add, or scene transitions. For Arcade Physics movement/collisions use phaser-arcade-physics.

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

Help users transition from a pure self-serve model to a hybrid motion that uses human sales to capture large enterprise deals while maintaining a frictionless product entry point.

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

Help users master the transition from sales-led to product-led growth by leveraging the product itself as the primary vehicle for customer education and revenue generation.

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

Help users build sustainable growth engines by transitioning from accidental word-of-mouth to structured referral programs and viral product loops.

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

Help users decide where to apply AI effectively, manage the transition from deterministic to probabilistic software, and build long-term defensibility through verticalization and proprietary data.

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