「spring」の検索結果

把拉片数据和原片合成一条**能直接看的视频**：一边是画面，一边是这一镜的分镜信息 （镜号、起止、时长、景别、类别、运镜、画面描述、台词），**镜头切了信息跟着切**， 镜头表自动滚动并高亮当前这一镜。 版式只看原片的宽高比：**横版 / 方版 → 画面在上、信息在下；竖版 → 画面在左、信息在右**， 画面永远原样缩放，不裁不拉。 镜头表**随播放滚动**：切点处滚一小段把当前镜头带到锚点、随后停住，高亮条同步滑过去。 实现上只截三张图（底板 + 铺开的长图 ×2），滚动与高亮由 ffmpeg 按时间裁窗， **布局全在 scripts/panel.css 里，改它就能改版式**，不用碰脚本。 吃 video-shots 产出的 shots.json（有 frames/ 就把关键帧当缩略图用）。 零 npm 依赖，用 ffmpeg 合成、无头浏览器渲面板。 Use when asked to 导出视频、合成视频、分镜视频、带分镜信息的视频、解说版视频、 video with shot info、annotated shot video。

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

拉片：把一条成片拆成逐镜头的分析表——每个镜头的时长、景别、类别、运镜、画面。 分工刻在骨子里：**能量的都由代码量**（切点来自 ffmpeg 场景检测，时长是切点相减， 运动量是逐帧差分的中位数），模型只判断它真正该判断的那几件事（景别 / 类别 / 运镜 / 画面 / 节奏）， 然后每一条判断都被代码当场对账——**声称推拉摇移却实测几乎不动，门直接拦**。 看片走联系表（每镜起手帧 + 收尾帧各拼一张大图，一屏二十几个镜头，a/b 对照就是运镜）， 不是一张张翻。检测漏刀多刀用 recut 补刀并刀，自动重编号重算时长，手改边界过不了门。 产出 shots.json + Markdown 镜头表 + **单页交互式拉片报告**：内嵌播放器（播放时同步高亮镜头、 点镜头跳转）、镜头节奏带、可搜索可筛选可排序的镜头表（列表 / 卡片两种视图、首尾关键帧并排、 点图开大图）、景别类别运镜分布、出场人物、质量门、导出 JSON。单文件零依赖，离线双击能开。 15 道质量门全部由脚本确定性检查。 零依赖、零 API key，只要 node 和 ffmpeg。 Use when asked to 拉片、拆镜头、分析视频镜头、镜头时长、景别、运镜、镜头表、 video shot breakdown、shot list from video。

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

把一条视频重建成「只有画面和声音」的干净文件——**源片的元数据一概不搬**： GPS、设备型号、账号 ID、创建时间、章节、GoPro 的遥测轨，全部留在原地。 走的是白名单而不是黑名单：不列要删什么，只说带什么过去（画面一条流、声音一条流）， 隐私保证来自结构，不来自枚举。 难点不在容器 tag，在**看不见的那几层**：x264 把完整编码参数写成 SEI 塞在码流里、 AAC 把版本号写进 DSE、avc1 的 compressorname 里还有一份——`ffprobe` 一个都看不见。 五个藏身处逐一堵死，每一处都有实测。 默认 `--mode copy`：**画面逐字节照搬**（cmp 验证过），只重编音频，53 秒的片子 1.3 秒跑完； `--mode encode` 完整重编码，多杀掉码流域的东西。 验收不靠声称：把源片所有元数据字符串当「针」，在输出文件里做**字节级扫描**， 扎到一根就红。12 道门全部由脚本确定性检查。 零依赖、零 API key，只要 node 和 ffmpeg。 Use when asked to 清元数据、去元数据、抹掉视频信息、视频隐私、去水印信息、 strip video metadata、remove exif from video、scrub video。

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

A stack of cards springs and fans into place on view — a lively hero for a small set (3–5). One set per view. Shown flat/instant under prefers-reduced-motion.

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

Make a primary button feel alive by gently pulling it toward the cursor as it approaches, then springing back. Keep it subtle and reserve it for one or two primary actions. Disabled on touch and under prefers-reduced-motion. Do not use it on dense UIs full of buttons.

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

A pill slides under the active nav item with a springy merge — a smooth segmented control. One per view. Under prefers-reduced-motion the pill jumps without easing.

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

A soft gooey blob trails the cursor with a springy lag — a playful custom pointer for a hero section. One per page; can distract on content-heavy pages. Hidden on touch and under prefers-reduced-motion.

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

A button that springs down on press and pops back — tactile tap feedback. An App-UI micro-interaction (mobile component feedback). Honors prefers-reduced-motion. Keep it short and snappy; only on controls that actually change state.

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

Expert patterns for 2D/3D camera control including smooth following (lerp, position_smoothing), camera shake (trauma system), screen shake with frequency parameters, deadzone/drag for platformers, look-ahead prediction, and camera transitions. Use for player cameras, cinematic sequences, or multi-camera systems. Trigger keywords: Camera2D, Camera3D, SpringArm3D, position_smoothing, camera_shake, trauma_system, look_ahead, drag_margin, camera_limits, camera_transition.

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

SwiftUI animation patterns including springs, transitions, PhaseAnimator, KeyframeAnimator, SF Symbol effects, scroll-driven effects, mesh gradients, text renderers, and shader effects. Use when implementing, reviewing, or fixing animation or visual-effect code on iOS/macOS.

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

Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.

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

Turn a talking-head video and its transcript into motion-graphic B-roll timed to the speaker's words, in a continuous one-shape style (one element that morphs and never cuts, driven by a cursor, spring motion). Use when someone gives a video (and ideally a transcript) and asks for motion graphics, B-roll, animated cutaways or overlays.

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

指导如何通过自定义注解（如@Unicom）标识Dubbo接口，利用BeanDefinitionRegistryPostProcessor在启动时扫描并动态注册ReferenceBean，实现RPC调用的封装。

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

Configure Kotlin build and quality tooling, including Gradle Kotlin DSL, Version Catalogs, KMP, ktlint, Detekt, MockK, coverage, and quality plugins. Use for Kotlin-specific build, lint, test-tool, or coverage setup; defer Java-only tooling and Spring test behavior.

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

Testing standards using JUnit 5, AssertJ, Mockito, Cucumber, and Spring Boot integration tests for Java. Use when writing or reviewing Java test behavior, including parallel execution and BDD; defer Kotlin-only tests, virtual-thread test infrastructure, and coverage-report/tooling configuration.

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

Java coding standards for Spring Boot services: naming, immutability, Optional usage, streams, exceptions, generics, and project layout.

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

JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.

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

Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer — do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.

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

SwiftUI animation foundations - withAnimation, transitions, matchedGeometryEffect, PhaseAnimator, KeyframeAnimator, springs, gestures.

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

Use when you need framework-agnostic SQL guidance — schema naming, relational table design, query readability, indexes, transactions, database security, migrations, testing, and monitoring — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Review SQL schema or migrations; Improve SQL query performance and readability; Design relational tables and indexes; Review database transaction, security, or monitoring practices. Part of Plinth Toolkit

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

Use when you need framework-agnostic MongoDB and non-relational database query guidance — document schema design, collection modeling, JSON Schema validation, indexes, aggregation pipelines, query performance, consistency trade-offs, transactions, and operational safety — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Design MongoDB document schemas; Review MongoDB queries and indexes; Improve aggregation pipeline performance; Model non-relational data access patterns; Review NoSQL consistency and transaction trade-offs. Part of Plinth Toolkit

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

Use when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures, isolation and reset between tests, verification of calls, dynamic ports and base URLs, and avoiding flaky stubs — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Design or review WireMock stubs (JSON mappings or Java DSL); Improve request matching, isolation, or reset strategy for HTTP mocks; Add or fix verification of outbound HTTP calls to a WireMock server; Debug flaky tests involving WireMock or unmatched request journals. Part of Plinth Toolkit

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

Use when you need framework-agnostic OpenAPI 3.x guidance — spec structure, metadata and versioning, paths and operations, reusable schemas, security schemes, examples, documentation quality, contract validation (e.g. Spectral), breaking-change awareness, and handoffs to codegen — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Review an OpenAPI; Improve an OpenAPI; Improve API contract; Improve API schema design. Part of Plinth Toolkit

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

Use when you need data access with Quarkus Hibernate ORM Panache — including PanacheEntity / PanacheEntityBase, PanacheRepository, named queries, JPQL, native SQL, DTO projections (project(Class)), pagination (Page.of()), N+1 avoidance (JOIN FETCH), optimistic locking (@Version / OptimisticLockException), @NamedQuery for validated reusable queries, transactions, @TestTransaction for test isolation, and immutable-friendly patterns. This is the Quarkus analogue to Spring Data for relational persistence. This should trigger for requests such as Review Panache entities or repositories in Quarkus; Improve Hibernate ORM data access with Panache; Add DTO projections, JOIN FETCH, pagination, or optimistic locking to Panache queries; Fix N+1 query problems or add @Version concurrency control in Quarkus Panache; Improve Panache active record versus repository design. Part of Plinth Toolkit

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