3.6천건 · 관련도순
Use for insight, reframing, contradiction, impasse, and anomaly-driven problem solving when execution effort no longer helps. NOT for routine optimization, error correction, or well-specified tasks with known solution paths.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level idiomatic Rust API design — the patterns that make illegal states unrepresentable and abstractions zero-cost. Type-state programming (PhantomData state machines), newtype + sealed + extension traits, typestate builders, RAII guards & Drop ordering, the interior-mutability decision tree (Cell/RefCell/Mutex/RwLock/Atomic/OnceLock), enum-driven state machines, error architecture (thiserror vs anyhow), dyn vs generic dispatch & object safety, the impl Trait / GAT / RPITIT toolbox, and Deref-for-smart-pointers (and its abuse). Use when designing a Rust library's public API, encoding invariants in the type system, choosing a dispatch or error strategy, or reviewing Rust for idiom. NOT for borrow-checker firefighting / toolchain / test-runner workflow (use rust-development-workflow), NOT for pd-console GPUI rendering/layout/panes (use gpui-rust-console), NOT for app packaging/notarization (use rust-app-distribution).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Programmatic SEO planning and analysis for pages generated at scale from data sources. Covers template engines, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention. Use when user says "programmatic SEO", "pages at scale", "dynamic pages", "template pages", "generated pages", or "data-driven SEO".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dense UI posture — maximum information density with clear hierarchy. Use when building or reworking admin dashboards, data tables and grids, ops or monitoring views, settings-heavy panels, debug inspectors, state or log viewers, and multi-pane tool UIs someone drives all day.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user wants to "investigate a bug", "debug an issue", "figure out why something is happening", "find the root cause", "troubleshoot", "強い推論で調査", "仮説を立てて検証", "原因を特定", "バグの原因調査", "なぜ動かないか調べて", "問題を切り分け", "原因不明", "デバッグ", or mentions systematic hypothesis-driven debugging. NOTE: Use this for investigating UNKNOWN causes, not for validating design proposals (use devils-advocate for that).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Save durable preferences, decisions, project facts, commitments, and lessons cheaply with knowledge_remember, or short notes and page updates with attribution and readback. Use for explicit saves or agent-driven remembering when Knowledge is the selected memory provider.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The single-file, dial-driven taste-skill that was the default before v2, kept for projects that depend on its exact behaviour. Opt-in: it runs only when called by name.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive Keel agent test-first or evidence-first execution for a selected OpenSpec task. Use when a task needs software tests, hardware testbench, assertions, lint, new behavior proof, regression coverage, or red/green evidence before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drives OBS Studio through its WebSocket, read-only by default, and turns recordings into clips, VOD cuts and chapters with FFmpeg. Trigger to audit an OBS setup; when a stream drops frames or lags; to switch a scene, mark a moment or save the replay buffer; to cut clips, burn in captions, normalize loudness or write chapters; when OBS shares a GPU; or say obsrunner (audit, check, set, mark, post, sheet, status, hold, release, refresh). Live work needs the user-installed obsws-python package. Never goes live, uploads or moderates chat. Caption files are whisperrunner's; thumbnails comfyrunner's; titles commscribe's; analytics duckrunner's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Finds where every credential on the machine lives, without showing a value. Trigger to list where keys, tokens and passwords are stored (Credential Manager, gh, .env, settings, .mcp.json, Docker); to cut a gh token to least privilege or switch gh accounts; to rotate a key and update its users; after a key was printed, pasted or committed; to check a command that uses a token before it runs; or say keywarden (inventory, scope, rotate, leak, preflight, refresh). Drives op or bw when present. Leak scans and commit email are shieldwarden's; rules and hooks gatewarden's; routine credentials agentwright's; vetting a vault MCP trustwarden's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prove a Convex feature works — seed, drive as multiple mocked users via convex-test, assert behavior including the negative authz cases (wrong user refused, data-scope enforced).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Preview Convex spend — rank functions by bytes/documents-read × call-volume from insights, project each cost driver's growth curve, name the cheapest fix; confirm-cost for paid actions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
DDD architecture knowledge base. Provides patterns, antipatterns, and PHP-specific guidelines for Domain-Driven Design audits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write acceptance tests before unit tests to ensure you're building the right thing
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Law-driven abstraction protocol: evidence first, seam test, minimal algebra, executable law check.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run TDD cycle for feature implementation. Use when implementing features with RED-GREEN-REFACTOR, running test-driven development, automating TDD workflow, or ensuring test-first development.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate A2UI 0.8 protocol compliant UI code. Use when building agent-driven interfaces, generating JSONL messages for surfaceUpdate/dataModelUpdate/beginRendering, creating forms, lists, cards, or any UI components that render across web/mobile/desktop platforms.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.