162건 · 관련도순
Keep coding tasks small by checking whether new code is needed, reusing existing helpers, and preferring standard libraries or built-in platform features. Apply the same approach to feature development, bug fixes, refactoring, and reviews.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Helps implement iii workers in Node.js, browsers, Python, and Rust with language-specific guidance on installation, function registration, calls, data channels, and logging. Explains package choices and connection constraints for each environment.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create reusable Helm charts, packages of Kubernetes deployment templates and settings. The skill guides environment configuration, dependency management, shared templates, and release procedures so applications can be deployed across environments with fewer template changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build runnable Foundry tests that demonstrate smart contract vulnerabilities with before-and-after logs and assertions. Use fork tests, which copy blockchain state, and test helpers to reproduce known DeFi incidents or prepare evidence for a report.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write and review animation code using gsap.utils helpers. Convert scroll positions into animation values, constrain ranges, generate random values, snap positions to a grid, and handle element collections with reusable functions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Sign in to a cloud provider’s command-line tool using a verification URL and one-time code approved on the user’s device. Check installation and account identity, save the login, and run commands within that user’s permissions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide OpenRig CLI and background service upgrades while protecting active sessions and local file changes. The skill provides staged checks, verified database backups, selective plugin refreshes, and migration helpers, with evidence checked after each change.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Work around file-writing errors caused by quotes, backticks, or JavaScript template literals using a temporary Python script. The workflow includes reading back each saved file to check its contents and removing the helper script afterward.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build dashboard panels in vanilla TypeScript with resizing, saved layout state, loading indicators, and retry controls. Examples also show how to wrap existing data-fetching functions with caching and temporary request pauses after repeated failures.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write and troubleshoot native Python in n8n Code nodes. Covers data filtering and transformation, migration from older Python code, valid return formats, and restricted execution environments, including cases where errors pass unprocessed input downstream.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build custom calculation and parsing tools that an n8n AI Agent can call. This skill covers JavaScript or Python inputs, structured arguments, string results, tool descriptions, and fixes for invocation and output errors.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (_rich_success, _rich_warning, _rich_error, _rich_info, _rich_echo), DiagnosticCollector, STATUS_SYMBOLS, CommandLogger, or any user-facing terminal output — even if the user doesn't mention "logging" or "UX" explicitly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactor and review SwiftUI view files with strong defaults for small dedicated subviews, MV-over-MVVM data flow, stable view trees, explicit dependency injection, and correct Observation usage. Use when cleaning up a SwiftUI view, splitting long bodies, removing inline actions or side effects, reducing computed `some View` helpers, or standardizing `@Observable` and view model initialization patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Functional programming helpers for Golang using samber/lo — 500+ type-safe generic functions for slices, maps, channels, strings, math, tuples, and concurrency (Map, Filter, Reduce, GroupBy, Chunk, Flatten, Find, Uniq, etc.). Core immutable package (lo), concurrent variants (lo/parallel aka lop), in-place mutations (lo/mutable aka lom), lazy iterators (lo/it aka loi for Go 1.23+), and experimental SIMD (lo/exp/simd). Apply when using or adopting samber/lo, when the codebase imports github.com/samber/lo, or when implementing functional-style data transformations in Go. Not for streaming pipelines (→ See `samber/cc-skills-golang@golang-samber-ro` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build, validate, and run the claude-osint skills repo — check SKILL.md frontmatter, run the secret_scan.py and h1_reference.py helpers, run sync-skill-content.sh, run the smoke test. Use when asked to run, build, test, validate, or smoke-test claude-osint or its OSINT skills/scripts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reference for the TRL (Transformer Reinforcement Learning) library codebase. Use proactively before reading or editing any file under `trl/` so you have the intended contracts and invariants in mind, not just what the current code says. Covers trainer hierarchy (SFT, DPO, GRPO, KTO), shared utility functions (selective_log_softmax, decode_and_strip_padding, padding helpers), configuration system, model wrappers, and how data flows through any TRL trainer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnoses macOS system-level slowness, heat and fleet-wide timeouts: high load average, leaked per-session child processes (MCP servers, helpers), fork storms, busy loops. Use when the Mac feels slow or hot, fans spin up, or everything times out at once (电脑发烫/卡顿/负载高/全部超时). Not for single-app bugs, network slowness (use tunnel-doctor), launchd watchdog design (use macos-watchdog), or disk-full (use macos-cleaner).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Organize care for an aging or ill family member across multiple helpers — the shared care map, a fair rotation with backup rules, the information binder, and family-meeting agendas that prevent the one-sibling-does-everything spiral. Use when asked help me coordinate care for my mom, my siblings and I need to split caregiving, organize care for a sick family member, or set up a care schedule. Produces the care map of needs and coverage, the rotation schedule with escalation rules, the binder outline, and the family meeting agenda.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Organize the people and information involved in caring for someone — family, doctors, helpers — so care doesn't fall through the cracks or all land on one person. Use when asked help me coordinate care for, organize caregiving for my parent, set up a care system, or I'm drowning coordinating everyone. Produces a map of who does what (medical, daily, financial, emotional), a shared-information system so everyone's on the same page, a way to divide tasks fairly among family, a communication rhythm, and how to keep the key information (meds, contacts, wishes) in one accessible place — turning caregiving chaos into a coordinated effort.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write and edit project docs (README/markdown) as a glossary of principles, not a mirror of the code. Use when creating or revising a README; when a doc enumerates exact scenes, scenarios, helpers, class ids, file lists, or command/flag matrices the code already holds; when trimming narrative or changelog out of a doc; or when deduplicating overlapping docs and wiring a root doc to its sub-docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create and edit presentation slide decks (`.pptx`) with PptxGenJS, bundled layout helpers, and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Boost.UT test layout, device helpers, adding tests, and running them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.