5.3천건 · 관련도순
Abracon MPN encoding patterns, suffix decoding, and handler guidance. Use when working with Abracon timing devices, crystals, oscillators, RF components, or AbraconHandler.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ABLIC (formerly Seiko Instruments) MPN encoding patterns, suffix decoding, and handler guidance. Use when working with ABLIC power management and memory ICs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[61] VALIDATE. Comprehensive code quality check combining ESLint, TypeScript compilation, and unused code detection. Runs full lint suite with detailed error reporting and fix suggestions. Use before commits, after major changes, or when ensuring code quality standards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinator workflow for orchestrating dockeragents through fix-review-iterate-present loop. Use when delegating any task that produces code changes. Ensures agents achieve 10/10 quality before presenting to human.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code quality standards for OneKey. Use when fixing lint warnings, running pre-commit tasks, handling unused variables, writing comments, or ensuring code quality. All comments must be in English. Triggers on lint, linting, eslint, oxlint, tsc, type check, unused variable, comment, documentation, spellcheck, code quality, pre-commit, yarn lint.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Patches native modules (expo-image, react-native, etc.) to fix native crashes or bugs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performance optimization guidelines for OneKey React/React Native applications. Use when optimizing app performance, fixing UI freezes/lag, reducing re-renders, handling concurrent operations, or analyzing performance bottlenecks. Triggers on performance, optimization, optimize, slow, lag, freeze, hang, jank, stutter, memory, leak, concurrent, batching, batch, memoization, memo, bridge, windowSize, contentVisibility, FlashList, re-render, fps, tti, bundle.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when GitHub may have shipped a GraphQL schema update affecting timeline event unions (PullRequestTimelineItems / IssueTimelineItems), when the gh-timeline dispatcher fallback is hitting more than expected, before a gh-timeline release, or when the user requests phrases like "verify timeline coverage", "audit gh-timeline schema", "check for new timeline events", "GitHub schema changed". Walks through schema diff → patch → test update → live verification → optional fixture refresh, marking each spot where a human decision is required.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Develops iOS/iPhone applications with XcodeGen, SwiftUI, and SPM. Triggers on XcodeGen project.yml configuration, SPM dependency issues, device deployment problems, code signing errors, camera/AVFoundation capture debugging, iOS version compatibility, or "Library not loaded @rpath" framework errors. Use when building iOS apps, fixing Xcode build failures, or deploying to real devices. Not for AVPlayer playback issues (seek/scrub/frame stepping → avfoundation-reference skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Substackの編集画面（Tiptap/ProseMirror）で、指摘済みの誤字脱字などの修正リストをスクリーンショット操作なしで高速に反映するスキル。jp-checkの校正結果をSubstack下書きに適用するときなどに使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Finds open GitHub PRs with security and priority-high labels, links each to its issue, detects duplicates (multiple PRs fixing the same issue), and presents a table of review candidates. Use when looking for the next PR to review. Trigger keywords - find pr, find review, next pr, pr to review, duplicate pr, security pr.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when working with the nuxt-ui-tools form runtime as a package consumer. It covers schema-driven forms, the provider-backed form API, inline rendering, overlay rendering, form pages with a section navigation, rich options (icon, avatar, chip, description, suffix, grouped menus, and renderOption/renderValue render functions on select, auto-complete, radio, and checkbox group), choice cards, and typed submit results.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing any feature or bugfix, before writing implementation code
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates user-facing changelogs and release notes from git commit history. Parses conventional commits, categorizes changes into features, fixes, breaking changes, and more, then rewrites technical messages into customer-friendly language. Use when the user asks to generate a changelog, write release notes, summarize recent commits, prepare CHANGELOG.md, or document what changed between versions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply systematic performance optimization techniques when writing or reviewing code. Use when optimizing hot paths, reducing latency, improving throughput, fixing performance regressions, or when the user mentions performance, optimization, speed, latency, throughput, profiling, or benchmarking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.