'resolution' 검색 결과

Reads an OpenAPI 3.0 specification and manually implements a type-safe Dart API layer using Dio for HTTP, Freezed or Equatable for models, and json_serializable for serialisation. Use when given an OpenAPI/Swagger file (JSON or YAML) and asked to implement the API in Flutter/Dart, create Dart models from an API schema, build a Dio API client, implement endpoints from a spec, convert openapi to dart, or set up a data/network layer from an API contract. Handles $ref resolution, oneOf union types, enums, query params, request bodies, and DioException error mapping.

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

Designs and reviews offline-first mobile data on every stack — Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers the local store, the outbox of pending mutations, idempotency keys, retry and backoff, conflict resolution, reconnection, and how to test a flaky network deterministically. Use when an app must work without connectivity, when writes are lost or duplicated after reconnecting, or when local and server data disagree.

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

Systematic ambiguity resolution through tiered information gathering. Use when facing unclear requirements, unknown context, uncertain implementation choices, or any situation where guessing would be risky.

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

Utility — fill the surface stack map in tech-stack.md and provision skills using intelligent resolution. Called by pipeline commands when tech stack info changes.

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

How to upgrade `alchemy` and the `effect` constellation across this repo and keep them consistent for consumers: which packages pin what, why `effect` and every `@effect/*` companion move as one set, what breaks in a typical upgrade, and how to verify a standalone `npm install` still resolves a single `effect`. Use when asked to upgrade or bump alchemy or effect, when a deploy dies inside an alchemy provider with a `TypeError` naming a missing combinator, when `check:npm-effect-resolution` fails, or when deciding whether the alchemy patch is still needed.

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

Use when working with Crates Io — crates.io Rust package registry management. Covers crate publishing, version management, dependency resolution, feature flags, build configurations, and crate metadata analysis. Use when managing Rust crates, publishing to crates.io, analyzing dependency trees, or configuring feature flags.

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

Use when working with Bind9 — bIND9 DNS server management covering zone files, named configuration, DNSSEC, RNDC controls, query logging, and server statistics. Use when managing BIND9 DNS servers, auditing zone configurations, troubleshooting DNS resolution, checking DNSSEC status, or monitoring BIND9 performance and query patterns.

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

Use when working with Cocoapods — cocoaPods dependency management for iOS/macOS. Covers Podfile configuration, pod publishing, dependency resolution, spec repositories, and pod analysis. Use when managing CocoaPods dependencies, publishing pod specs, resolving version conflicts, or analyzing pod dependency trees.

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

Use when working with Azure Dns — azure DNS management covering public and private DNS zones, record sets, virtual network links, DNSSEC, and alias records. Use when managing Azure DNS zones, configuring DNS records, setting up private DNS for VNets, managing alias records for Azure resources, or troubleshooting DNS resolution.

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

Recognize when disagreements reveal valuable context, preserve multiple valid approaches instead of forcing premature resolution

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

Bulk-create hundreds of AI agent skills for the Agency Roster repo — naming, conflict resolution, batch delegation, GitHub sync, and monetization prep.

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

Core Swift development workflows for Xcode and Swift tooling, including project setup, dependency management, concurrency guidance, language/runtime best practices, and troubleshooting build or package resolution issues. Use when working on Swift tasks across a codebase, especially package/tooling/runtime work and cross-cutting Swift conventions (mutation semantics, naming, enum/file rules, import hygiene), including in SwiftUI projects.

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

Implement, review, or improve CloudKit and iCloud sync in iOS/macOS apps. Use when working with CKContainer, CKRecord, CKQuery, CKSubscription, CKSyncEngine, CKShare, NSUbiquitousKeyValueStore, or iCloud Drive file coordination; when syncing SwiftData models via ModelConfiguration with cloudKitDatabase; when handling CKError codes for conflict resolution, network failures, or quota limits; or when checking iCloud account status before performing sync operations.

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

Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build plugin overhead, duplicate module builds from configuration drift, circular dependencies between modules, oversized modules needing splitting, or modularization best practices.

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

Set, review, and update the user's goals. Use when: goals, resolutions, track progress, what am I working toward, or holding me accountable.

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

Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance best practices. Use when: segment, analytics.js, customer data platform, cdp, tracking plan.

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

Expert dependency manager specializing in package management, security auditing, and version conflict resolution across multiple ecosystems. Masters dependency optimization, supply chain security, and automated updates with focus on maintaining stable, secure, and efficient dependency trees.

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

Complaint/ticket triage-and-dispatch App-in-Skill (Busabase App-in-Skill) for property managers, facilities teams, and helpdesk leads. Use when the user invokes $kelly-tickets or /kelly-tickets, or asks for complaint triage, ticket dispatch, 投诉, 工单, 派单, property management complaints, helpdesk queue, intake from WeChat exports/call logs/front-desk forms, crew assignment, SLA board, dispatch approval, or ticket resolution tracking.

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

TypeScript (tsc, 6.0 / 7.0 Go 製ネイティブ版) リファレンス。 tsconfig.json compilerOptions, strict, moduleResolution, project references (tsc -b), generics, conditional / mapped / template literal types, utility types, narrowing, .d.ts, checkJs, ESM / CJS interop, --checkers / --builders。

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

Improves the quality of images, especially screenshots, by enhancing resolution, sharpness, and clarity. Perfect for preparing images for presentations, documentation, or social media posts.

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

Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

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

Architectures and techniques for neural operators on discontinuous PDE solutions (shocks, contact discontinuities, steep gradients). Covers local-global spectral design (ShockFNO), reflection padding for non-periodic BCs, resolution scaling for shock width, and frequency-band error diagnostics. Use for low-viscosity Burgers, compressible Euler, Riemann problems, or any PDE where standard FNO produces Gibbs oscillations.

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

Mendelian randomization (MR) causal inference — does an exposure, risk factor, or biomarker CAUSALLY affect a disease/outcome, using genetic variants as instrumental variables (IEU OpenGWAS / EpiGraphDB MR-EvE). Use this whenever the user asks if X causes Y, whether an observational association is actually causal or just correlation, if a biomarker/trait is a causal risk factor, wants to triangulate epidemiology against genetic evidence, or mentions Mendelian randomization, instrumental-variable analysis, two-sample MR, or genetic causal evidence — even if they never say "MR" (e.g. "is LDL cholesterol actually causal for heart disease?", "does BMI cause type 2 diabetes or just correlate?", "is CRP a causal driver of stroke?"). Covers trait-label resolution, MR effect direction/magnitude, instrument quality (MOE score), method agreement (IVW vs MR-Egger vs weighted median), bidirectional MR for reverse causation, and distinguishing causation from genetic correlation. Not for plain GWAS association lookups (use the GWAS skills) or fitting your own instruments from raw summary statistics.

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

End-to-end Hi-C analysis workflow from FASTQ to compartments, TADs, and loops, with the decision of WHICH features the sequencing depth can support. Covers pairtools read-pair processing and library QC, cooler matrices, ICE balancing and distance-decay expected, A/B compartments, TAD boundaries, loop calling, and the routing of HiChIP/PLAC-seq/Capture Hi-C to protein-directed loop callers. Use when processing Hi-C data end to end, deciding a resolution for a given depth, or choosing between bulk-Hi-C and protein-directed loop calling.

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