'observable' 검색 결과

Time average of observable along trajectory

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

Verify after implementation that a feature achieved its required user/system outcomes. Use for goal-backward post-implementation verification that tests observable behavior rather than merely checking code existence.

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

SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices.

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

Angular Router (built-in `@angular/router`) — route configuration for standalone and NgModule projects, functional guards (Angular 14.1+), lazy loading, route resolvers, typed params via signals/observables, programmatic navigation, route data and meta. Use this skill to: - Configure routes (standalone-style or NgModule-style). - Use functional guards (canActivate as function, preferred over class-based in 17+). - Lazy-load components or feature modules. - Implement auth guards via route meta + functional guards. - Read params/queries via `inject(ActivatedRoute)` + signals or RxJS. Do NOT use this skill for: - General conventions (see angular-conventions). - State management (see angular-state-and-rx). - Forms (see angular-forms). - Testing routes (see angular-testing).

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

Fit hidden Markov models using the Baum-Welch (EM) algorithm with model selection, Viterbi decoding for state sequences, and forward-backward probabilities. Use when observations are generated by unobservable latent states, you need to segment a time series into latent regimes (market regimes, speech phonemes, biological sequences), compute sequence probabilities, decode the most likely hidden state path, or compare models with different numbers of hidden states.

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

Create interactive maps, elevation profiles, and spatial visualizations from GPX tracks, waypoints, or route data using R (sf, leaflet, tmap) or Observable (D3, deck.gl). Covers data import, coordinate system handling, map styling, and export to HTML or image formats. Use when visualizing a planned or completed tour route on an interactive map, creating elevation profiles for hiking or cycling routes, overlaying waypoints and POIs on a basemap, or building a web-based trip dashboard.

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

Audit one bounded Proto UI deployment or publication evidence slice against an exact revision and delivery surface. Use to verify revision identity, environment result, artifacts, and observable health. Do not deploy, promote, roll back, publish, release, or change environment protection.

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

Use when you need to query an OpenCTI instance — is this IOC already known, what entities/reports/campaigns exist for an actor — or push new intel into it — creating indicators/observables, labelling, TLP markings, relationships, or importing a STIX 2.1 bundle. Two-way integration. Commonly invoked by /ip-investigation and friends to check whether an indicator is already in your knowledge base, and by analytical skills that want to publish their findings back to OpenCTI. Reads $OPENCTI_URL and $OPENCTI_TOKEN.

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

Reactive programming with RxJS - Observables, operators, Subjects, error handling, and memory leak prevention

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

Use when restructuring existing frontend code while preserving observable behavior, including responsibility extraction, module movement, conditional simplification, API cleanup, or data organization. Do not use for new feature behavior, behavior-changing bug fixes, dependency or framework migrations, or proven dead-code cleanup.

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

Use when implementing new observable frontend behavior or fixing a behavior-changing bug where a failing test can describe the missing or incorrect behavior first. Apply to components, hooks/composables, utilities, API clients, route guards, or user workflows; pure behavior-preserving refactoring uses an already-green contract instead.

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

Delegate tasks to ANY CLI agent (claude, codex, aider, ...) running in a detached tmux session, with a race-safe done-signal protocol and multi-turn iteration. Use when delegating work to a non-Claude CLI agent, when the user says "tmux delegate", "run agent in tmux", "delegate to codex/aider", or when executor work should run in an observable background terminal instead of the Agent tool.

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

Implement HTTP data fetching in Angular v20+ using resource(), httpResource(), and HttpClient. Use for API calls, data loading with signals, request/response handling, and interceptors. Triggers on data fetching, API integration, loading states, error handling, or converting Observable-based HTTP to signal-based patterns.

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

Implement signal-based reactive state management in Angular v20+. Use for creating reactive state with signal(), derived state with computed(), dependent state with linkedSignal(), and side effects with effect(). Triggers on state management questions, converting from BehaviorSubject/Observable patterns to signals, or implementing reactive data flows.

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

Designs candidate-controlled mock interview practice across voice, text, code, and whiteboards. Use for session configuration, observable-evidence feedback, and adaptive practice plans. NOT for hiring decisions, emotion inference, gaze or integrity monitoring, or ranking candidates.

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

Verify that a requested bug fix changes observable behavior with a failing-before, passing-after reproduction and honest execution evidence.

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

Drive QA of a SwiftUI app on a real iPhone over USB - screenshot, read the accessibility tree, inspect @Observable state, tap, swipe, and type through an HTTP bridge embedded in the app under test. Use when asked to test an iOS app on a physical device, find bugs on the device, or expose a connected iPhone to a remote agent over Tailscale. Requires the ios-agent-qa runtime; not for simulator or XCTest work.

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

[Workflow] Restructure existing code while preserving observable behavior, proven by baseline and final tests plus change review.

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

Enforce traceability from natural-language intent to machine predicates, final observables, evidence, and owner-readable acceptance. Use when conducting any audit, review, QA pass, parity or compliance check, security assessment, code or architecture review, visual or behavioral comparison, data validation, system verification, completion gate, or claim that an implementation satisfies a human request.

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

Break an application or feature into thin vertical user-story slices with clear acceptance criteria and user-observable value. Use when planning a backlog, decomposing a feature, writing implementation-ready stories, or turning requirements into deliverable slices.

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

Author deterministic owner-correct tests that prove observable contracts through valid APIs.

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

Builds a DRAFT structured interview scorecard from a job description: five to eight competencies traced to it, past-behaviour and situational evidence questions with probes, four-level rating anchors written as observable behaviours, a blank scoring sheet, a panel plan and the items the hiring manager must confirm. Use when the user asks to "build an interview scorecard for this job description", "write competency questions for this role", "draft the interview guide for the panel", "set up a rating scale for the interviewers", "put together a structured interview kit" or "create a hiring rubric from the JD". Do not use for writing or fixing the job description itself, use job-description-drafter instead; for the new hire's first 90 days, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT course outline from a training need and audience: learning objectives with an observable verb, condition and standard, modules in a stated order with a duration basis and sources, activities and an assessment plan aligned objective by objective, and a coverage table showing what each objective still lacks. Never sets a pass mark, declares learners competent or invents content. Use when the user asks to "build a course outline", "design a training programme for", "turn this need into modules and objectives", "draft the curriculum for this workshop" or "what should this training cover". Do not use for quiz items from finished content, use training-quiz-builder instead; for needs from surveys and manager notes, use training-needs-synthesis; for a new starter's first weeks, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Converts TypeScript to idiomatic Dart 3 code, covering syntax mapping, type system translation, async patterns, and module migration. Activates when translating TypeScript interfaces, classes, enums, generics, union types, async/await patterns, or modules to Dart; migrating frontend or Node.js logic to Flutter/Dart; converting RxJS Observables to Dart Streams; adapting TypeScript utility types to Dart equivalents; or producing idiomatic Dart 3 output (sealed classes, records, pattern matching) from TypeScript source.

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