「transition」の検索結果

Transition an Incan RFC from one status to the next. Use when the user asks to promote, advance, or finalize an RFC, or says /bump-rfc. Handles Draft → Planned, Planned → In Progress, and In Progress → Implemented transitions.

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

Read and manage Jira Cloud issues, projects, boards, sprints, comments, and transitions. Use this whenever the user wants to search issues with JQL, create or update a ticket, transition an issue (move to In Progress / Done), add a comment, check a sprint or board, look up a project, or ask "what's in my Jira queue" — even if they don't say "API". Also use it for any *.atlassian.net URL, an issue key like "PROJ-123", or a JQL string. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

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

Adds a purposeful animation layer to Stitch-generated components — CSS transitions, Framer Motion (React/Next.js), or Svelte transitions. Always respects prefers-reduced-motion.

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

Improve or implement purposeful motion systems, micro-interactions, gestures, and transition behavior for production-grade UI. Use when the user mentions animation, motion, transitions, micro-interactions, hover states, drawers, toasts, gestures, or making the UI feel more alive.

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

审视、设计、从零启动或改进 HarmonyOS、OpenHarmony 与 ArkUI 产品界面。用于检查 ArkTS UI、建立新项目设计基线、区分永恒原则与当前平台视觉语言、规划跨手机/平板/折叠屏/PC 的导航和布局、多输入控件状态、animateTo、transition、geometryTransition、springMotion、手势跟手与可打断动效、异步状态真实性、视觉分层参数、无障碍或动画性能，或建立鸿蒙 Motion Token 时。不要用于签名、构建、网络、存储、权限、数据库等纯工程问题，也不要用于通用视频剪辑或其他移动平台的设计规范评审。

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

Systematically interpret ultraviolet-visible absorption spectra to identify chromophores, classify electronic transitions, apply Woodward-Fieser rules for conjugated systems, and perform quantitative analysis using the Beer-Lambert law.

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

"Net-zero transition playbook: GHG inventory (ISO 14064-1, GHG Protocol Scope 1/2/3), science-based targets (SBTi), TCFD and ISSB S1/S2 climate disclosure, Taiwan carbon fee, decarbonization roadmap, internal carbon pricing, supply-chain carbon, product carbon footprint, green electricity and T-REC. Use for corporate decarbonization roadmap, carbon inventory, carbon-fee response, TCFD/ISSB reporting, supply-chain decarbonization, or responding to international customers (Apple, RE100). Triggers: 『碳盤查』『SBTi』『碳費』『TCFD』『淨零路徑』『範疇 3』『綠電』『CBAM』『ISO 14064』『ISSB』『T-REC』. For Taiwan EMBA ESG/sustainability/operations/strategy/finance cases. Focuses on Taiwan listed-company and supply-chain practice; sustainability strategy theory: use Asgard `grad-sustainability`; ERM 框架整合氣候風險: use `biz-erm`; 董事會 ESG 委員會結構設計: use `biz-corporate-governance`; 併購 ESG 盡職調查: use `fin-m-and-a`.".

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

Debug or validate Pulp animations / transitions / scroll behavior using in-process motion fixtures and offline visual analysis. TRIGGER on phrases like "animation is wrong", "transition timing off", "fade too late", "card slides too far", "scroll jumps on restore", "scroll offset wrong on restore", "frame jump in the timeline", "easing looks wonky", "imported Figma motion doesn't match source", "settle time / overshoot / drift / monotonic", "what value does the knob reach at frame N", "record this animation so I can replay it", "this animation is expensive — which one and why", "reduced-motion broken", "scrub a captured fixture". Captures fixtures (.motion.jsonl), and ships assertion helpers (is_monotonic / settling_time_seconds / overshoot / start_delay_seconds / final_value / local_step_outlier_ratio) and the `scroll_geometry` trace for `ScrollView` content-offset / visible-rect / content-size observability. Off by default in prod.

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

Interface-based state machine patterns for Unity game states, character controllers, and UI flows. Use when implementing game flow (menu -> gameplay -> game over), character states (idle -> run -> jump -> fall), AI behavior states, or UI screen transitions. Triggers on "state machine", "game states", "character states", "screen flow", "game flow", "add states to", "idle/run/jump", "menu flow", "AI states", "boss phases", or any task involving managing discrete states with transitions between them. Reads ProjectConfig.yaml -> architecture_pattern to adapt patterns for SO-first or DI-first.

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

Use when designing, implementing, or reviewing frontend interaction motion, page transitions, scroll animation, Framer Motion, GSAP, Lottie, CSS animation, motion intensity, animation performance, reduced-motion behavior, or cinematic but accessible UI motion. Do not use for SVG-only path drawing, Canvas/WebGL rendering, or ordinary hover states; Chinese triggers include motion design, interactive effects, page transitions, scroll animation, Framer Motion, GSAP.

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

Use this skill when mapping care coordination process requirements for Health Cloud: designing care team workflows, transition of care handoffs, social determinants of health (SDOH) barrier tracking, and care gap identification. NOT for building care plan templates, problems, and goals — use admin/care-plan-configuration. NOT for referral routing and provider networks — use admin/referral-management-health.

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

Run work as an explicit event-driven state machine executed by subagents. The orchestrator is the runtime from the canonical loop — `state, effects = init(machine); execute(effects); while state is active: event = nextEvent(); state, effects = transition(machine, state, event); execute(effects); return state.output`. All routing judgment is authored ONCE, at plan time, into a machine file (states, event alphabet, transition table, budgets, final states); at runtime the orchestrator does pure table lookups and dispatches effects — it never decides, never authors, never ingests artifacts. Subagent/sync protocol is the timeboxed-iterating one: role prompts scaffolded once to disk and dispatched BY PATH, an initialiser preamble every subagent reads first, a self-populating cheatsheet, per-unit files, tiny structured returns, independent measurement gate. Use when the user says "workmachine", "run this as a state machine", "state-machine this", or when a goal has a small number of clearly named phases with explicit outcomes (built / passed / failed / blocked) and you want the routing to be auditable rather than judged on the fly. For clock-driven loops use timeboxed-iterating; for wide graphs with judged edge criteria use workgraph.

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

Design, implement, and review XState v5 state machines and @xstate/react integrations in TypeScript. Use when modeling finite workflows, async actors, statecharts, guarded transitions, delayed transitions, actor systems, or machine-driven React behavior.

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

Drive JIRA workflow lifecycle via jira-as: transition, assign, resolve, reopen, versions, components. NOT issue CRUD (mk:jira-issue) or bulk transitions (mk:jira-bulk).

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

Build Sankey, alluvial, river, and CONSORT-style flow diagrams to visualize cohort transitions, cell-state changes, or pipeline filtering using ggalluvial, networkD3, plotly, and consort. Use when showing how entities move between categories across timepoints (cell states, drug response classes, patient flow through a trial) or filtering pipelines (variants filtered through QC stages).

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

Transition insulin pump to scheduled subcutaneous basal bolus insulin when anticipated hospital length of stay exceeds 1 to 2 days and pump expertise is unavailable. Triggers include: "Patient expected to stay >2 days, should we switch pump to scheduled insulin?

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

Recommends continuing insulin pump therapy in hospitals with pump expertise; otherwise transitioning to scheduled subcutaneous basal bolus insulin if anticipated length of stay exceeds 1–2 days before pump discontinuation. Consider this when anticipating a hospital stay >2 days, lacking pump expertise, or needing to conserve supplies.

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

Expert-level thermodynamics knowledge. Use when working with heat, temperature, entropy, thermodynamic laws, heat engines, refrigerators, phase transitions, statistical mechanics, or thermodynamic cycles. Also use when the user mentions 'entropy', 'enthalpy', 'Carnot', 'heat engine', 'thermodynamic cycle', 'ideal gas', 'phase transition', 'Gibbs free energy', 'specific heat', 'thermal equilibrium', or 'second law'.

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

Expert-level inorganic chemistry knowledge. Use when working with coordination chemistry, transition metals, crystal field theory, organometallics, main group chemistry, solid state chemistry, acid-base theory, or inorganic reaction mechanisms. Also use when the user mentions 'coordination complex', 'ligand', 'crystal field', 'transition metal', 'oxidation state', 'organometallic', 'Lewis acid', 'VSEPR', 'symmetry', 'point group', 'solid state', or 'catalysis'.

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

Expert-level condensed matter physics knowledge. Use when working with crystal structure, band theory, semiconductors, superconductivity, magnetism, phase transitions, Fermi liquids, topological materials, or strongly correlated systems. Also use when the user mentions 'band gap', 'Fermi energy', 'semiconductor', 'superconductor', 'phonon', 'crystal lattice', 'Brillouin zone', 'Bloch theorem', 'Hall effect', 'magnetism', 'phase transition', or 'topological insulator'.

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

Translate motion, interaction, and visual experience into implementable constraints while preserving accessibility and performance. Apply when working on animations, transitions, scroll effects, or micro-UX.

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

Best practices for Remotion - Video creation in React. 29 domain-specific rules covering 3D, animations, audio, captions, charts, transitions, and more. Use when building video in React with Remotion — animations, audio, captions, charts, or transitions.

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

Test or fix domain rules, state transitions, value objects, and domain services directly. Use for business-rule regression tests, rejected transitions, and model behavior without HTTP.

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

変更が波及する全モジュール・全フローを特定し、集計ルール、状態遷移、符号反転、 コピペ差分、表示/帳票/APIの整合性を監査するスキル。Impact Mapで変更核から 影響範囲を可視化し、Consistency Matrixで横断整合を検証し、Copy Propagation Review戦略でコピペ実装を効率的にレビューする。 Use when one change affects multiple modules, reports, flows, or copied implementations. Audits aggregation totals, state transitions, sign inversion, and cross-module consistency.