'observable' 검색 결과

Build and review ViewModels, objects that manage screen state and actions, with CommunityToolkit.Mvvm. Use attributes to generate change notifications and commands, add input validation, and handle asynchronous operations, cancellation, and command availability.

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

• Add properties that notify the screen when values change
• Create asynchronous commands with cancellation
• Validate registration forms and settings

Build charts from tables using Vega-Lite, Vega, or Observable Plot. Describe data, visual elements, and interactions in reusable definitions, choose a suitable tool, and assess mobile layout, performance, and when custom rendering becomes necessary.

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

• Writing a Vega-Lite chart specification from a dataset
• Choosing between Plot, Vega-Lite, and D3
• Building layered charts with panels and tooltips

Build and review SwiftUI interfaces for iOS and macOS with guidance on state management, reusable views, navigation, and rendering performance. Examples show how to organize data flow and reduce unnecessary screen updates.

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

• Choosing state management for SwiftUI views
• Designing navigation with NavigationStack
• Improving list rendering performance

Swift의 actor로 공유 데이터 접근을 관리하고 메모리 캐시와 JSON 파일 저장을 결합해 동시 접근 시 데이터 경쟁을 피하는 저장 계층을 설계합니다.

• iOS와 macOS 앱에 데이터를 저장합니다
• 오프라인 중심 앱의 저장 계층을 설계합니다
• 잠금 기반 동기화 처리를 대체합니다

Regenerate an iOS app's debug bridge, the code connecting it to debugging tools, using current gstack templates. Update Swift support files and typed state accessors after gstack upgrades or ViewModel and property additions.

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

• Updating the debug bridge after a gstack upgrade
• Adding accessor coverage for new ViewModels
• Regenerating accessors for added state properties

Guide an RxJS 7 project to RxJS Next by testing existing behavior, reviewing how subscriptions start and end, and validating small batches of changes. Record approved behavior choices, verification results, and unresolved blockers in migration reports.

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

• Assess RxJS usage and test coverage before migration
• Plan how subscriptions and cleanup should behave
• Migrate code and TestScheduler tests in small batches

Turn rough feature ideas into a clear SPEC.md through focused questions. Define target users, business rules, current scope, and acceptance criteria based on observable results, giving developers or AI agents concrete requirements to implement.

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

• Turning rough feature ideas into requirements
• Defining observable acceptance criteria
• Clarifying current scope and exclusions

Bridge Observables and Signals using toSignal and toObservable in Angular. Use when converting between RxJS Observables and Angular Signals.

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

State management for Angular 18-21: signals (signal/computed/effect), services-as-state, NgRx Store + Effects + Selectors, NgRx Component Store, NgRx Signals (newer signal-based store). RxJS essentials — operators, async pipe, takeUntilDestroyed, signal/observable interop. Use this skill to: - Pick the right state tool (signals / services / NgRx variant / vue-query equivalent). - Use signals correctly (signal/computed/effect — when each). - Build a Pinia-style service-as-state singleton. - Set up NgRx Store + Effects + Selectors. - Use RxJS without leaking subscriptions (async pipe, takeUntilDestroyed, Subject patterns). - Bridge signals ↔ observables via toSignal / toObservable. Do NOT use this skill for: - General Angular conventions (see angular-conventions). - Routing state (see angular-routing). - Form state (see angular-forms). - Testing state (see angular-testing).

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

Apply strict coding practices to Python, Rust, TypeScript, and Go projects. The skill guides typed errors, handling every variant, resource management, and tests that verify observable behavior, while prioritizing reuse and minimal changes.

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

• Implementing features with strict types
• Fixing bugs at their shared root cause
• Reviewing tests for observable behavior

Check that an actual app, API, or command-line tool works by exercising its real entry point with realistic inputs. Collect observable evidence such as outputs, logs, exit codes, or screenshots, and report remaining uncertainty.

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

• Checking app behavior through the actual interface
• Verifying API behavior with realistic inputs
• Collecting command-line outputs and exit codes

Connect ViewModels, objects that manage screen state and actions, through messages without direct references. The skill covers event broadcasts, requests for values, window-specific channels, and recipient registration and cleanup using CommunityToolkit.Mvvm.

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

• Share login or theme changes across ViewModels
• Request values from another ViewModel
• Keep messages within a specific window

Turn feature ideas into backlog items, a team's planned units of work, using Why, What, and Acceptance Criteria. Connect each item to business goals and define observable outcomes in independent pieces sized for one sprint.

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

• Breaking a feature into independent work items
• Explaining the business purpose behind development work
• Writing observable acceptance criteria

Refactor large SwiftUI screens into smaller views with clear inputs and state ownership. Organize actions, shared dependencies, and observable models while preserving existing layout and behavior, making the code easier to read and test.

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

• Split a large SwiftUI screen into smaller views
• Clarify state ownership and data flow
• Move business logic out of the view body

Turn agreed requirements or design documents into actionable development tasks grounded in existing code. Define observable acceptance criteria, scope, affected behavior, and unresolved decisions so builders can understand what to deliver and verify.

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

• Turning a requirements document into a task
• Checking a design against existing code
• Identifying missing behavior decisions

Organize substantial tasks into a cycle of creation, independent review, and revision while preserving the original request. Turn broad quality goals into observable checks, collect evidence, and finish with verified results or a clearly identified blocker.

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

• Turning vague quality goals into observable completion checks
• Coordinating independent workstreams and reviewers
• Comparing anonymous candidates against a shared benchmark

Guidance for .NET MAUI XAML and C# data bindings — compiled bindings, INotifyPropertyChanged / ObservableObject, value converters, binding modes, multi-binding, relative bindings, fallbacks, and MVVM best practices. USE FOR: setting up compiled bindings with x:DataType, implementing INotifyPropertyChanged or CommunityToolkit ObservableObject, creating IValueConverter / IMultiValueConverter, choosing binding modes, configuring BindingContext, relative bindings, binding fallbacks, StringFormat, code-behind SetBinding with lambdas, and enforcing XC0022/XC0025 warnings. DO NOT USE FOR: CollectionView item templates and layouts (use maui-collectionview), Shell navigation data passing (use maui-shell-navigation), dependency injection (use maui-dependency-injection), or animations triggered by property changes (use .NET MAUI animation APIs).

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

Use when the user wants to modernize iOS code to iOS 17/18 patterns, migrate from ObservableObject to @Observable, update @StateObject to @State, or adopt modern SwiftUI APIs.

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

Builds and reviews SwiftUI views with modern MV architecture, state, composition, isolated previews, and migration guidance. Covers @Observable ownership, @State/@Bindable/@Environment wiring, view decomposition, ViewModifiers, environment values, .task loading, iOS 26+ handoffs, Writing Tools, clipboard availability, and performance. Use when structuring SwiftUI state, managing @Observable, composing views, previewing meaningful UI states, or correcting SwiftUI patterns.

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

Author learning targets for a competency across developmental bands with precise, observable progression language. Use when writing 'I can' statements for competency-based programmes.

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

Migration guides for CoreData to SwiftData, UIKit to SwiftUI, ObservableObject to @Observable, XCTest to Swift Testing, Objective-C to Swift, and StoreKit 1 to StoreKit 2. Use when migrating between Apple framework generations.

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

Guidance for .NET MAUI XAML and C# data bindings — compiled bindings, INotifyPropertyChanged / ObservableObject, value converters, binding modes, multi-binding, relative bindings, fallbacks, and MVVM best practices. USE FOR: setting up compiled bindings with x:DataType, implementing INotifyPropertyChanged or CommunityToolkit ObservableObject, creating IValueConverter / IMultiValueConverter, choosing binding modes, configuring BindingContext, relative bindings, binding fallbacks, StringFormat, code-behind SetBinding with lambdas, and enforcing XC0022/XC0025 warnings. DO NOT USE FOR: CollectionView item templates and layouts (use maui-collectionview), Shell navigation data passing (use maui-shell-navigation), dependency injection (use maui-dependency-injection), or animations triggered by property changes (use .NET MAUI animation APIs).

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

Implement RxJS patterns for reactive programming in Angular. Use this skill when working with Observables, operators, subscriptions, async data flows, and error handling. Covers common patterns like combineLatest, switchMap, debounceTime, catchError, retry logic, and integration with Angular Signals using toSignal() and toObservable(). Ensures proper subscription cleanup with takeUntilDestroyed().

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

Author learning targets for a competency across developmental bands with precise, observable progression language. Use when writing 'I can' statements for competency-based programmes.

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