'transition' 검색 결과

Use when the user says "check Jira", "create ticket", "update issue", or needs JQL queries, ticket transitions, or branch-to-ticket linking.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Load Remotion best practices for React video creation, including animations, composition setup, assets, audio, captions, sequencing, transitions, media metadata, Three.js, Tailwind, and rendering patterns. Use when creating, editing, debugging, or reviewing Remotion code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, extend, or fix Eloquent business models and their state transitions. Use when moving business rules out of controllers or Actions, or explicitly migrating a model into a DDD capability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing or implementing states for AI agent tasks, background jobs, local model runs, queues, and notifications — one shared set of states, only legal transitions, and a recovery path out of every failure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate a self-contained HTML presentation with Magic Move transitions. Use when the user wants to create a slideshow, presentation, or slide deck from a topic or outline, or invokes magic-slide preview to start the preview server.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SOP for normative specification and behavioral contracts. Trigger when: - Defining invariants, permitted transitions, and forbidden states. - Navigating steps: Identify, Formalize, Verify, Record, Connect. - Prompt contains: /spec, spec workflow, normative constraint, invariant, BCP 14.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AID methodology phase gate enforcement. Ensures work follows correct 6-phase order (Discovery -> PRD -> Tech Spec -> Impl Plan -> Dev -> QA & Ship). Enforces gates, validates transitions. Use before any work to check the current phase and refuse work belonging to a later phase.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Track and correlate events across multiple timezones with automatic conversion. Use when analyzing distributed system incidents, coordinating cross-regional operations, or creating time-normalized reports from logs/events spanning PST/CST/EST/JST or other timezones. Handles daylight saving transitions automatically.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reconstructed reference notes on US FAA approval guidance for airborne software and airborne electronic hardware, built from four public-domain sources (FAA Order 8110.49A, AC 20-115D, AC 20-152A, AC 00-69; documents dated 2017-07-21 to 2022-10-07, pinned 2026-10-12). Use for how FAA certification staff plan and conduct software reviews (certification liaison, desk versus on-site review, review planning agreements), how the level of FAA involvement (LOI) is picked and scored with the Appendix A worksheets, how software conformity inspection works (software part and installation conformity, ASE and ASI tasks, Form 8120-10), what AC 20-115D recognizes and how DO-178B processes and tool qualification transition to DO-178C/DO-330 (supplements, FLS, UMS, legacy software changes), and what AC 20-152A adds for airborne electronic hardware (simple versus complex custom devices, robustness and HDL code coverage, tool assessment, previously developed hardware, COTS IP, COTS devices, circuit board assemblies), and what AC 00-69 adds as best practices for change impact analysis, data and control coupling, and design-level error handling (best practices, not guidance and not a means of compliance). SCOPE LIMITS: FAA guidance only, and guidance is not regulation (ACs are acceptable means, not the only means); no RTCA DO-178C or DO-254, EUROCAE ED-12C or ED-80, supplement, or SAE ARP text, which are copyrighted and named only (see the avionics-signpost pack); no AC 00-72 (named, not packed); no DO-178C software-level objective tables; no EASA AMC 20-115D or AMC 20-152A content (use easa-rules); reflects the pinned source dates, not later FAA actions; synthesized reference notes, not legal advice and not a substitute for the source documents. LICENCE: Public Domain (US Government work, 17 U.S.C. 105).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Load when the user asks to create, find, update, assign, label, prioritize, transition, or organize ISLAMU Event issues/cycles/modules in Plane via MCP; not for local todo lists or implementation-plan markdown.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Jira ticket operations via Atlassian MCP including view, search (natural language to JQL), create, update, comment, and transition with auto-detection of ticket IDs from git branches. Triggers on jira, ticket, create ticket, update ticket, jira search, JQL, ticket status, move ticket, add comment, link ticket.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Edit, extend, transition, and combine existing video while preserving an explicit parent asset and audio decision.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Knowledge base from the Expanded Guidance for NASA Systems Engineering (NASA/SP-2016-6105-SUPPL, Volume 1, March 2016) — the practitioner-depth supplement to the NASA SE Handbook. Use for the load-bearing mechanics the handbook compresses: the SE Engine's per-phase cadence and the iterative-vs-recursive distinction, the AS9100 crosswalk, life-cycle tailoring vs. customization and the Compliance Matrix, the recursive system-design consistency loop (ConOps vs. Operations Concept, requirement flow/type/ownership, successive refinement), product realization (verify/qualify/accept/certify cardinality, protoflight, 'test the way we fly' coverage, two-form transition), and the crosscutting technical-management procedures (six-step scheduling, cost-estimating method selection, JCL, interface document family, RIDM/CRM, CM baselines, EVM arithmetic, MOE/MOP/KPP/TPM, the three required leading indicators, and the decision-analysis method catalog). This is the DEPTH layer — it deliberately does NOT restate the base definitions; pair it with the nasa-se-handbook pack. Scope: NASA space-flight SE practice (Vol 1 Practices); thin on the Vol 2 process-appendix detail, on non-NASA/commercial life cycles, and on software-engineering methodology.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Operate Jira Cloud via its REST v3 API — issues, projects, sprints, boards, comments, transitions, JQL search. Use when the user wants to triage, bulk-update, report on, or otherwise interact with Jira programmatically without the MCP server installed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a web project needs animation or motion-tool selection across native CSS/WAAPI/View Transitions, Motion, Anime.js, GSAP, Lenis, scroll choreography, SVG/text animation, or synchronized motion systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing interface states, feedback, hover/focus/press, gestures, direct manipulation, navigation transitions, loading/error/empty behavior, or deciding where interaction should carry the design concept.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Curated WooCommerce Memberships hook and extension-point map for plugins that build on user memberships, membership plans, status transitions, purchase/free-signup grants, profile fields, REST API, webhooks, members-area templates, CSV import/export, and Woo Subscriptions-linked memberships. Use when the user asks for a Memberships hook list, "where should I hook", membership created/saved, status changed, grant access from order, user membership API, profile fields, member directory, or code contains wc_memberships_, WC_Memberships_User_Membership, WC_Memberships_Membership_Plan, wc_user_membership, wc_membership_plan, wcm-, _subscription_id, wc_memberships_rules, or woocommerce-memberships.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.