722건 · 관련도순
Three.js architecture: production-level scene/camera/renderer resize cleanup. Use when implementing, reviewing or testing three.js architecture for React, Vite, Next.js or Perfect_AI projects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Three.js + Anime.js scroll sync: production-level deterministic progress and camera choreography. Use when implementing, reviewing or testing three.js + anime.js scroll sync for React, Vite, Next.js or Perfect_AI projects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
3D game development principles. Rendering, shaders, physics, cameras.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
2D game development principles. Sprites, tilemaps, physics, camera.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
当使用者说"给照片加参数边框"、"加个相机参数水印"、"给这张照片加个信息带"、"照片下面印上光圈快门"时使用。Add a configurable information band to an existing photograph using embedded EXIF facts such as aperture, shutter speed, exposure compensation, ISO, capture time, and camera. Use when a user asks to frame, label, or export a photo with shooting metadata. Do not use for interpreting photographic intent, inventing missing metadata, or editing the photograph itself.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Programmatic untargeted LC-MS feature extraction in R with the modern xcms 4.x MsExperiment/XcmsExperiment API, taking raw mzML to a feature table via CentWave peak detection, retention-time alignment, peak-density correspondence, gap-filling, CAMERA redundancy collapse, and built-in QC feature filtering. Use when converting centroided LC-MS runs into a features-by-samples matrix and deciding centWave/grouping/alignment parameters. For drift correction and QC/CV filtering execution see metabolomics/normalization-qc; for metabolite identification see metabolomics/metabolite-annotation; for the MS-DIAL GUI alternative with MS2Dec deconvolution see metabolomics/msdial-preprocessing; for downstream statistics see metabolomics/statistical-analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Video and audio processing capabilities for Flutter applications
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs the Autoware autonomous-driving stack against CARLA on UE 5.8 over CARLA's native ROS 2 interface — no bridge process. Reports the DDS contract (rt/vehicle/status/* out, rt/control/command/* in), the Autoware-only sensor blueprints, generates the lanelet2 + point-cloud map artifacts Autoware needs instead of an .xodr, and drives the two shipped modes (classical NDT stack, or the camera-only VAD end-to-end model). Use when the user asks to "run Autoware on CARLA", "connect an AV stack", "drive the ego from Autoware", "generate a lanelet2 map", or asks which topics CARLA exchanges with Autoware.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tells you what CARLA on UE 5.5 (branch ue5-dev) cannot do that UE 5.8 (ue58-dev) can, so you do not attempt an unsupported workflow there — no Autoware integration, no ROS 2 middleware choice (FastDDS only), no DLSS or ray-traced-lens camera, no OFPA large-map mount so Town12/13/15 load black, and a few missing World/Actor methods. Also states what is identical, so the ue58 skills can be used directly for everything else. Use when working against a 5.5 checkout, when a ue58 skill's step has no counterpart, or when deciding whether a feature request is possible on 5.5 at all.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates and edits CARLA Leaderboard route files — placing waypoints and scenario trigger points interactively from the spectator camera (route_creator, scenario_creator), visualising an existing route in the simulator (route_displayer), summarising it as a table (route_summarizer), capturing the current weather in route format (weather_creator), sorting scenarios by route position (scenario_orderer) and converting 1.0-format routes to 2.x (route_bridge). Use when the user asks to "make a new route", "add a scenario to a route", "visualise/debug a route", "see what's in this route file", or "convert old leaderboard routes".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inspects and visualises a ROS-2-enabled CARLA server from Docker containers, with no local ROS 2 install — list/echo/rate-check topics (the "are the topics actually on the wire" check), run the bundled map-and-lidar demo stack (hero vehicle with camera/lidar/GNSS/IMU on autopilot), and open RViz2 with the lane-network preset. Use when the user asks to "check the ROS topics", "echo /carla/map", "is CARLA publishing to ROS", "visualise the lidar in RViz", "open rviz", or "run the ROS 2 demo".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cooks and packages CarlaUE4 into distributable tarballs under Dist/ — either the full simulator or a standalone asset package of selected maps and props for later import. ROS2=1 keeps the native ROS 2 interface in the cooked package (a plain cook silently drops it). Use when the user asks to "package CARLA", "make a Dist build", "cook the project", "export a map as a package", "package CARLA with ROS2", or needs a build with working camera and lidar sensors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
visionOS / iOS 空間コンピューティング。RealityKit、ARKit、visionOS SwiftUI、USDKit、Spatial Preview。 Entity, ModelEntity, AnchorEntity, Component, System, RealityView, MeshResource, Material, EntityAction, MeshDeformerComponent, GaussianSplatComponent, ComputeGraphComponent, ComputeNodeGraph, PhysicsJointsComponent, ForceEffectComponent, ClothBodyComponent, NavigationComponent, NavigationMeshComponent, NavigationController, USDStage, SpatialPreviewSession, ImmersiveSpace, ImmersionStyle, WindowGroup, VolumetricWindowStyle, Model3D, ARKitSession, ARSession, ARWorldTrackingConfiguration, WorldTrackingProvider, HandTrackingProvider, ImageTrackingProvider, AccessoryTrackingProvider, CameraFrameProvider, ObjectTrackingProvider, RoomTrackingProvider, SceneReconstructionProvider。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AVFoundation / AVKit / PhotoKit リファレンス。 AVPlayer, AVPlayerViewController, VideoPlayer, AVPlayerItem, AVMutableComposition, AVCaptureSession, AVCaptureDevice, AVCapturePhotoOutput, AVCaptureDeviceDirectionCoordinator, CameraCaptureAccessory (iPhone Duo), AVAudioEngine, AVAudioSession, AVAudioPlayer, AVSpeechSynthesizer, PHAsset, PHImageManager, PhotosPicker, PHPhotoLibrary。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Raycast from Camera.main through a Game View coordinate. Use when you need to check what a screenshot coordinate would hit in 3D physics before clicking or long-pressing with simulate-mouse-input.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Video and audio processing capabilities for Flutter applications
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Three.js interaction - raycasting, controls, mouse/touch input, object selection. Use when handling user input, implementing click detection, adding camera controls, or creating interactive 3D experiences.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
2D game development principles. Sprites, tilemaps, physics, camera.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
3D game development principles. Rendering, shaders, physics, cameras.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Develops iOS/iPhone applications with XcodeGen, SwiftUI, and SPM. Triggers on XcodeGen project.yml configuration, SPM dependency issues, device deployment problems, code signing errors, camera/AVFoundation capture debugging, iOS version compatibility, or "Library not loaded @rpath" framework errors. Use when building iOS apps, fixing Xcode build failures, or deploying to real devices. Not for AVPlayer playback issues (seek/scrub/frame stepping → avfoundation-reference skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Control Google Nest devices (thermostats, cameras, doorbells) via the Google Smart Device Management API using curl and jq.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture frames or clips from RTSP/ONVIF cameras.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Requires OFOX_API_KEY — create one at https://app.ofox.ai, plus a publicly reachable reference video the user is authorized to use. Use when a user has a rough 3D white-model, clay, wireframe, blockout, previs, or animatic clip and wants a finished visual treatment that preserves its shot order, cut timing, camera framing, spatial layout, and motion directions. Distinguishes that structure-preserving job from a continuation beginning at the reference's final state. Do not use for two still endpoints (keyframe-animation), for appending and locally joining a new ending (video-extend-edit), or when still-image references must be combined with the video in one request — first/last-frame anchors conflict with video references in the shipped core, while mixed image/video references are untested.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Requires OFOX_API_KEY — create one at https://app.ofox.ai. Generate a cinematic brand/product ad clip from a product description or photo using the Ofox video API (Seedance 2.5) — runs a short creative brief (product photo, brand tone, camera move, aspect ratio) when the request leaves them open, writes a timestamped shot-craft prompt (hook, showcase, slow-motion climax, hero close), shows a cost estimate, then calls ofox-video-core to submit, poll, download, and report the real cost. Use when a user asks for a commercial-style product or brand video, e.g. "give this perfume bottle a 10-second cinematic brand ad", "make a product ad for our new sneaker", "turn this product photo into a hero video for the landing page", or "I need a 15-second brand video with a slow orbit around the bottle". Do not use for dialogue-driven scenes with people talking (see seedance-short-drama).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.