'state' 검색 결과

Extract property address, price, room count, and features from a listing document into structured JSON for MLS and property platforms.

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

Extract address, listing price, bedrooms, bathrooms, amenities, and agent contact details from a public listing page.

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

Extract property listing details from a real estate document, then generate a branded PDF brochure and a social media image for the listing.

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

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.

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

Reads a specific actor's live telemetry from a running CARLA server — location and rotation, velocity and speed, acceleration, angular velocity, and for vehicles the control input (throttle/steer/brake), front-wheel steer angle and mass. All kinematics come from one world snapshot so they are frame-consistent. Use when the user asks "how fast is it going", "where/what heading is the car", "show the ego's telemetry", or "stream a vehicle's state". Resolve ambiguous targets with the world-data skill.

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

Reads and changes a running CARLA server's WorldSettings via apply_settings — synchronous vs asynchronous mode, fixed_delta_seconds (fps), physics substepping, and no_rendering_mode — and keeps the Traffic Manager's sync state matched automatically. Use when the user asks to "enable/disable sync mode", "set synchronous mode", "run at a fixed fps/step", "turn off rendering", "make the sim deterministic", or "restore async mode", and as the prerequisite for keeping settings across a map load.

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

Listens to a CARLA sensor and either saves its data to files, shows it live in a window, prints a one-shot summary, or (ros-info) reports the native ROS 2 topics, QoS and enabled-for-ROS state so you can echo it from ROS instead. Cameras save as PNG (depth/semantic auto-colourised) and display in a pygame window; lidar saves as .ply and shows as a top-down scatter; IMU/GNSS/radar/collision stream to JSONL or the console. Use when the user asks to "show/view the camera", "display the lidar", "save the sensor data / capture a dataset", or "what is this sensor reading". Select the sensor by id, type, or the actor it's attached to.

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

Records a running CARLA simulation to a .log file via start_recorder/stop_recorder for later deterministic replay — capturing actor spawns, transforms, traffic-light states and animations (optionally velocities/controls). Use when the user asks to "record the simulation", "start/stop the recorder", "capture this run", or "save a scenario to replay later". Does NOT capture sensor images.

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

Windows アプリ開発 (WinUI 3 / XAML) の UI 基盤リファレンス。 Grid, StackPanel, Canvas, RelativePanel, SplitView, ScrollViewer、x:Bind, x:Name, x:Class, StaticResource, ThemeResource、添付プロパティ, 依存関係プロパティ、Style, ControlTemplate, DataTemplate, VisualStateManager, ResourceDictionary、Acrylic, Mica, SystemBackdrop, SystemBackdropElement、compact sizing、Binding, INotifyPropertyChanged, ObservableCollection, IValueConverter, DataContext, MVVM、 Storyboard, DoubleAnimation, EasingFunction, ThemeTransition, ConnectedAnimation, ImplicitAnimation、XamlOptionalChanges。

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

Windows アプリ開発 (DirectX / WinRT メディア) のグラフィックス・メディア API リファレンス。 Direct2D (ID2D1Factory, ID2D1DeviceContext, ID2D1Bitmap1, ID2D1Effect, D2D1 Effects, ID2D1PathGeometry), DirectWrite (IDWriteFactory, IDWriteTextLayout, DWriteCore), Direct3D 11/12 (D3D11CreateDevice, D3D11On12, DXGI SwapChain, HLSL, D3D12 PipelineState, D3D12 DRED), Microsoft.UI.Composition (Compositor, Visual, ExpressionAnimation, InteractionTracker, MicaController), カメラ・画面キャプチャ (MediaCapture, MediaFrameReader, GraphicsCaptureSession, Windows Studio Effects, OpenCV)、音声・動画再生 (MediaPlayer, MediaPlaybackSession, AudioGraph, MediaTranscoder, AdaptiveMediaSource, HLS, DASH, CastingDevicePicker, AudioPlaybackConnection)。

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

Theatre.js アニメーションツールキットリファレンス。 @theatre/core / @theatre/studio / @theatre/r3f / @theatre/dataverse。 getProject, Sheet, Sequence, Object, val, onChange, prop-types（number / rgba / compound / image）。 studio initialize / extend / transaction / scrub / createPane。 SheetProvider, editable, useCurrentSheet, useVal, usePrism, useAtom。 keyframe アニメーション、audio sync、state JSON、React Three Fiber 統合。

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

OpenAI API (developers.openai.com) の Responses API リファレンス。 text generation, embeddings, gpt-6-astra / gpt-6.1-sol / gpt-6-luna, structured outputs, streaming, function calling, programmatic / async tool calling, conversation state, prompt caching, prompt cache diagnostics, reasoning (configuration_update), background mode, compaction, multi-agent, WebSocket mode (mid-turn steering, stream_id), webhooks, error codes, rate limits, Realtime server controls, 公式 SDK (Python / JS / .NET / Java / Go / Ruby), openai CLI, Chat Completions / Assistants 移行, deprecations。

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

NVIDIA CUDA GPU 並列コンピューティングリファレンス。 CUDA C++ / CUDA Python, kernel, nvcc, Unified Memory, CUDA Graphs, Cooperative Groups, Green Contexts, Driver API, マルチ GPU。 PTX ISA 命令セット, state space, MMA 命令。 Blackwell チューニング, Streaming Multiprocessor, NVLink, Locality Domains, Compute Fabric Transport。 CUTLASS / CuTe DSL / CuTe C++ GEMM, Tensor Core, tcgen05, Task Scheduling, Operator API, nvMatmulHeuristics, nsight-compute, compute-sanitizer。

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

mssql (node-mssql, Node.js 向け Microsoft SQL Server クライアント) の API リファレンス。 tedious / msnodesqlv8 ドライバー、SQL Server / T-SQL / TDS 接続、ConnectionPool、 `sql.query` タグ付きテンプレート、bulk insert、Table-Valued Parameter (TVP)、 prepared statement、isolation level、Diagnostics Channel、Azure AD 認証、CLI。 Drizzle ORM 経由の SQL Server 利用 (drizzle-orm/mssql-core) は別スキル drizzle が対象。

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

Figma REST API / Plugin API / Widget API / Code Connect / MCP Server / Dev Mode リファレンス OAuth / PAT / Plan Access Token, files, folders, variables, VariableComposedColor, webhooks, SCIM, Dev Resources, activity-logs, library-analytics FrameNode, TextNode, ComponentNode, figma.variables, figma.codegen, figma.ui, textWrapStyle, variable fonts Widget useSyncedState, useSyncedMap, usePropertyMenu, AutoLayout Code Connect template files (.figma.ts) / legacy parser / custom parsers / register / Storybook (React / SwiftUI / Compose / HTML) MCP Code to Canvas, Write to Canvas, html_to_figma, generate_image, get_motion_context, generative plugins / shaders, Figma Weave

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

Android Jetpack Compose (Kotlin) のアニメーション・描画リファレンス。 androidx.compose.animation / graphics API。 AnimatedVisibility, AnimatedContent, animate*AsState, Animatable, AnimationSpec, Canvas, DrawScope, Brush, Path, Color, Image。

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

Apple SwiftUI 宣言的 UI フレームワークリファレンス。 View, VStack, HStack, ZStack, List, NavigationStack, TabView, toolbar, State, Binding, Bindable, Environment, EnvironmentObject, sheet, fullScreenCover, modifier, animation, Animation, withAnimation, Transition, matchedGeometryEffect, PhaseAnimator, KeyframeAnimator, swipeActions, reorderable, AsyncImage, DocumentGroup, Document, Liquid Glass, iPhone Duo 対応 (ArrangementView, ReservedRegion, DeviceHinge)。

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

Android アプリ開発 (Kotlin) のバックグラウンド・非同期処理リファレンス。 Jetpack androidx WorkManager: Worker, CoroutineWorker, WorkRequest, Constraints, WorkInfo, WorkContinuation, expedited work, テスト。 Service: フォアグラウンドサービス, バウンドサービス, AIDL, Messenger。 AlarmManager, PendingIntent, BroadcastReceiver, JobScheduler, Doze。 Kotlin コルーチン, Flow, StateFlow, SharedFlow, Channel。

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

Generate ideas that don't sound logical, then validate them with cheap behavioural experiments — Rory Sutherland's 'the opposite of a good idea can be a good idea' plus revealed-preference testing. Use when the obvious/logical solution is saturated and the user wants genuinely different options, asks 'what's a creative/unconventional angle', 'how do we stand out', 'should we run a test/experiment', 'how do we know what people actually want', or is about to trust a survey/focus group. Covers deliberate inversion of the obvious move, why stated preferences lie, and designing small reversible experiments that watch behaviour. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「競合と同じ案しか出ない」「アンケートは好評なのに売れない」「思い切った案を安く試したい」）にも使う。中文咨询（“只能想出和竞品一样的方案”“问卷好评却卖不动”）也适用。

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

Design what an employer will have a candidate do during an Otameshi Tenshoku trial: turn a business problem into a bounded paid assignment or an unpaid learning visit, with scope, completion criteria, candidate hours, company staff hours, duration, compensation and change conditions, and check the planned cost against the budget. Use when a hiring manager, recruiter or small-business owner wants to decide what work to offer, how much time it takes, what it costs, or how to adjust a plan when materials are late or the scope grows; do not use to write the public listing (trial-listing-draft), to reply to applicants (applicant-reply), to state market rates, legal, tax or service conditions from memory, or to post, contact or contract on the user's behalf.

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

Help job seekers use Otameshi Tenshoku to prepare profiles and applications, clarify trial conditions, plan learning visits or paid trial work, and reflect on the experience. Use when a candidate wants to apply for, prepare for, negotiate the scope of, or review an otameshi work experience; do not use to predict whether they will be hired or to judge their aptitude, to state fees, contract terms, or service conditions from memory, or to submit an application, update a profile, or send a message on their behalf. Employer-side requests belong to the employer skills (trial-work-design, trial-listing-draft, applicant-reply and others).

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

Debrief a finished Otameshi Tenshoku trial from the employer's side: set the observed facts against the completion criteria agreed before the start, keep expectations added afterwards, second-hand or off-the-job observations and the company's own late or missing support apart, settle the hours actually worked separately from any evaluation, and draft feedback to the candidate that states facts, support gaps and what happens next without promising a hire or continuation the company has not decided. Use when a hiring manager, recruiter or small-business owner wants to review a trial, decide what to tell the candidate, or work out the settlement after a shortfall; do not use to judge the candidate's aptitude or predict a hire, to cut pay or demand unpaid rework because of dissatisfaction, to compare candidates, or to send the feedback, pay, or update records on the user's behalf.

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

Review and revise Japanese job-application documents (entry sheets, rirekisho, shokumu-keirekisho) by checking each answer against the question asked, the stated character limit, and the evidence the applicant can actually support, then propose concrete rewrites the applicant decides on. Use when a user wants an ES or resume answer critiqued, tightened, or drafted from their own experience; to assemble a whole shokumu-keirekisho from an experience inventory, use resume-draft instead; do not use to invent experience, to judge pass or fail probability, or to submit an application.

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

Reply to an applicant for an employer's Otameshi Tenshoku listing: match the application against the listed requirements item by item on what the applicant actually stated, list the questions still open, and draft an invitation, a request for clarification, a hold notice or a decline that sticks to the listed conditions, keeps other applicants and internal notes out, and presents any new work or dates as a proposal rather than an agreed term. Use when a hiring manager, recruiter or small-business owner has applications to answer, wants to know what to ask before inviting, or has to decline; do not use to judge an applicant's aptitude or predict hiring outcomes, to screen on personal attributes unrelated to the work, to design the work (trial-work-design) or the listing (trial-listing-draft), or to send the message or update applicant records on the user's behalf.

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