개발 스킬

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

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

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

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

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

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

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

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

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

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

Guidelines for upgrading Expo SDK versions and fixing dependency issues

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

Implement and review React, React Native, and TypeScript UI for maximum practical render performance through leaf-local updates, stable identities, honest Hook semantics, and minimal effects. Use for components, hooks, callbacks, context, external stores, memoization, list rows, large dependency arrays, callback or state fanout, re-render reduction, and React Compiler-aware performance work.

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

Survey a whole React codebase as a senior React engineer, using React Doctor's scan as evidence, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the React code", "audit this codebase", "make this app faster / more robust", or wants a roadmap of fixes rather than a review of a single diff. For a regression check or a fix-it-now pass, use the `react-doctor` skill instead.

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

Inspect and profile React Native component trees from agent-device. Use for React Native performance, profiling, props, state, hooks, render causes, slow components, excessive rerenders, or questions like why a component rerendered.

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

Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.

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

Opt-in evidence-first causal diagnosis for bugs, browser or app/device failures, flaky behavior, and performance regressions. Activate only when the user explicitly invokes `$diagnose` or explicitly asks to use the named diagnose skill. Do not activate merely because the user mentions a bug, asks why something failed, requests debugging or a fix, or describes unexpected behavior. Once explicitly invoked, locate likely causes, instrument relevant boundaries with extensive structured logging, reproduce the issue, analyze the collected logs, rank causes with confidence scores, and pursue 100% operational confidence while probes can increase confidence.

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

Synchronize CS-Notes Git changes and material projections when the user says 同步笔记, sync笔记, or pull CS-Notes and push. Preserve unpublished intakes and require material-specific human completion evidence before archival.

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

Local speech-to-text with the Whisper CLI (no API key).

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

Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.

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

使用火山引擎 Ask-Echo 融合信息搜索 API 进行 web 搜索、web 搜索总结版和图片搜索。

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

Inspect and manage guarded Codex App-native or launchd heartbeats for Codex main control threads. Use when the user wants Codex to periodically continue a specific thread only when it is idle, avoid interrupting active work, keep App-visible interactions, inspect thread status, or enable/disable project autopilot heartbeats.

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

Locate and read a Codex thread by a codex thread link, thread id, or rollout path across all local CODEX_HOME directories (~/.codex, ~/.codex-gpt, ...). Use when the user pastes a codex:// link, asks to understand the 前因后果 of a Codex session, wants a timeline of what a long-running main thread did, or needs to search / export a past Codex conversation.

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

Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read/write commands, return stable JSON, manage auth, and pair with a companion skill.

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

Optimize code performance through iterative improvements (max 2 rounds). Benchmark execution time and memory usage, compare against baseline implementations, and generate detailed optimization reports. Supports C++, Python, Java, Rust, and other languages.

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

统一采集框架 - 支持 RSS/Web/API，207+ 采集源，AI 评分/分类/摘要

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

Guide a Chinese-speaking user through code or a PR while reviewing correctness. Trigger on 帮我review, 带我读代码, or an explicit implementation walkthrough.

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

Inspect GitHub pull requests, issues, workflow runs, and API data with the gh CLI. Use when the user wants repository facts from GitHub without opening the browser, especially for PR status, CI failures, issue lists, or structured JSON output.

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

Split mixed Git changes into public-safe, reviewable commits and PRs when the user requests publication or cleanup. Preserve unrelated work; merging is separate.

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

Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the fastest proof path without making code edits.

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