개발 스킬

Create, update, and review reusable instruction bundles for Unreal Engine agents. Get guidance on choosing a Python class or project asset, writing the description and instructions, registering the skill, and checking how it will appear to the agent.

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

• Creating an Unreal Engine Agent Skill for a workflow
• Updating or reviewing a skill’s instructions
• Choosing between a Python class and a UAsset

Diagnose Swift Concurrency errors and warnings, convert callback-based code to async/await, and plan Swift 6 migrations. Guidance accounts for actors, isolation boundaries, Sendable values, and project settings to help developers choose small, behavior-preserving fixes.

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

• Understanding a Swift concurrency compiler diagnostic
• Refactoring callback code to async/await
• Planning a Swift 6 concurrency migration

Use the `gh` command-line tool to manage GitHub repositories, issues, pull requests, releases, Actions workflows, and gists. The skill also includes commands for searching, installing, listing, and updating agent skills.

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

• Creating or reviewing a GitHub pull request
• Managing issues and repository settings
• Running or monitoring an Actions workflow

Diagnose Android WebView problems that appear only on certain devices, including slow startup, renderer process death, provider failures, lifecycle handling in Compose, and cookie issues. The skill points to practical patterns and ways to verify fixes.

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

• Investigating a WebView screen that freezes on low-memory phones
• Tracing an app that disappears when its WebView renderer is killed
• Handling WebView creation and cleanup in Compose AndroidView

Use this guide to diagnose Kotlin Multiplatform API issues involving Ktor clients, response parsing, authentication, retries, downloads, and WebSockets. It helps identify why a request can appear successful while data is lost or a connection never becomes usable.

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

• Debugging a successful API write whose data never appears
• Setting up or reviewing Ktor clients across platforms
• Diagnosing login callbacks, retries, or reconnect loops

Find practical guidance for Kotlin Multiplatform architecture and language pitfalls, from module boundaries and dependency injection to platform-specific compilation and formatting bugs. Each topic describes failure patterns and ways to verify them in a project.

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

• Planning module boundaries for a Kotlin Multiplatform app
• Debugging Koin or ViewModel lifetime and resolution issues
• Investigating code that compiles on one platform but fails on another

Consult nine practical debugging and engineering-method guides when a fix is not converging. They help choose a discriminating experiment, interpret build logs, check shared effects before removing a feature, and investigate repository history carefully.

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

• Choosing the next experiment after repeated failed fixes
• Finding the cause in a long build log
• Checking shared handles before removing a feature

Use this guide to investigate playback problems in Media3/ExoPlayer and desktop engines, including crossfades, audio focus, loudness, queues, shuffle, position restore, and shared listening. Each entry describes a failure pattern and a way to verify it.

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

• Debugging crossfades, fades, or volume changes
• Fixing queue order or shuffle display problems
• Investigating playback position restore after restart

Use this guide to diagnose Compose visual issues involving themes, color tokens, artwork palettes, gradients, shimmer, glass and particle effects, animation, image loading, charts, and statistics. It maps visible symptoms to implementation pitfalls and verification steps.

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

• Fixing visible seams or banding in gradients
• Debugging artwork based colors that flash or disappear
• Investigating animations or shimmer that freeze or pop

Use this skill to diagnose common layout, navigation, and interaction problems in Compose screens. It provides focused patterns and verification steps for areas such as adaptive layouts, lists, sheets, sliders, text fields, and one-shot effects.

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

• Fixing a screen that breaks in a resized window
• Debugging list selection, drag, or swipe behavior
• Checking pager, sheet, slider, or text field interactions

Scan added Kotlin or Compose Multiplatform lines for 32 known risky patterns. The skill directs the agent to inspect each matching trap and surrounding code, confirm whether it applies, and report confirmed issues with fixes and verification steps.

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

• Reviewing a Kotlin change before committing
• Checking a branch diff against its target
• Auditing selected source paths for risky patterns

Diagnose reactive state and background-work problems in Kotlin and Compose Multiplatform apps, including StateFlow timing, job lifecycles, WorkManager scheduling, backups, crash reporting, logging, and widgets. Topics explain common failure modes and how to check them.

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

• Investigating stale or briefly incorrect screen state
• Debugging background work that runs twice or not at all
• Checking backup and WorkManager scheduling behavior

Use this guide when building or debugging a Kotlin app’s data layer with Room/SQLite, DataStore, repositories, caches, or paging. It covers query and migration traps that can silently return wrong or missing data, plus patterns for imports and local-time analytics.

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

• Checking a SQL query that unexpectedly returns no rows
• Planning a Room schema migration
• Debugging incorrect local-time analytics

Check skill directories against the agentskills.io specification and Claude Code best practices. The validation report identifies issues with names, descriptions, metadata, document length, reference links, and progressive disclosure so authors can revise their skills.

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

• Checking skill files before sharing them
• Finding naming or metadata issues
• Reviewing reference links and document structure

Plan and carry out a React Native upgrade by reviewing template changes, updating dependencies, and migrating iOS and Android configuration. The workflow also covers Expo SDK alignment, breaking API changes, and checks that both platforms build after the upgrade.

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

• Upgrade an app to a newer React Native version
• Review native configuration changes between versions
• Check dependency compatibility before upgrading

Build navigation interfaces with React Navigation 7 using patterns for stacks, tabs, drawers, and sheets. Get guidance on headers and safe areas, with API choices based on whether the app already has a navigation setup or is starting fresh.

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

• Adding stack-based screens and modals
• Building bottom tabs or swipeable top tabs
• Setting up drawers and sidebars

Review React Native apps built for TV platforms, from remote and D-pad focus behavior to readable layouts, playback and DRM issues, performance on limited hardware, and accessibility. Get guidance tailored to the app’s TV stack and platform constraints.

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

• Debugging focus movement with a TV remote
• Reviewing a TV screen for readability and safe areas
• Investigating playback or DRM failures

Integrate React Native or Expo into an existing native iOS or Android app in stages using `@callstack/react-native-brownfield`. Follow either the Expo or bare React Native path to package app artifacts and add React Native screens to the native host.

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

• Adding React Native screens to an existing iOS app
• Packaging an XCFramework for host integration
• Generating an Android AAR artifact

Create a starter structure for a standalone React Native library or a local library inside an existing app using `create-react-native-library`. Use it to begin JavaScript libraries, native modules that expose platform features, or native UI components rendered in React Native.

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

• Scaffold a standalone React Native library
• Add a local native module to an existing app
• Wrap a native SDK for use from JavaScript

Diagnose React Native performance issues by measuring frame rate, startup time, bundle and app size, memory use, and re-renders. The guide suggests targeted fixes across JavaScript, native code, animations, and bundling, then re-measure to confirm results.

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

• Investigate laggy screens or dropped animation frames
• Measure and improve app startup time
• Find causes of excessive re-renders or memory growth

Assess whether an existing mobile product should move to React Native and which path fits its evidence and constraints. The skill inventories client platforms, evaluates migration options, defines a representative checkpoint, and prepares baseline and ROI decision inputs before implementation.

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

• Assess migration readiness across iOS and Android codebases
• Compare brownfield, greenfield, checkpoint, defer, and stop paths
• Define representative flows for a migration trial

Audit an AI agent workspace and organize its shared rules, skill sources, names, and host-specific bridges. The workflow helps keep Claude Code, Codex, and Grok aligned while making the authoritative skill files clear and easier to maintain over time.

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

• Bringing project rules into a shared structure
• Migrating skills between Claude Code, Codex, and Grok
• Finding authoritative skill files among scattered documents

Build and test the multi-module Morphia project with Maven or its project wrapper. Compile the code, run all or selected tests, verify integration tests, or install build artifacts, including commands for working with a specific module.

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

• Compiling the Morphia project
• Running all tests or one selected test
• Verifying integration tests across the project

Diagnose failing tests in the Morphia project by running the test, examining the full error, and tracing behavior through source and generated code. Make a minimal fix, then rerun the failing and related tests to check the result.

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

• Finding the cause of a failing Morphia test
• Tracing an error into generated bytecode
• Checking whether an AOT or runtime generation path failed