186건 · 관련도순
Audit a deployed AI agent through its product interface to test tool misuse, cross-user memory leaks, and unauthorized actions. Focuses on observable actions and reproducible evidence, including whether required human confirmation can be bypassed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore web application vulnerabilities by class, including access control failures, XSS, and SQL injection. Use root causes, testing checklists, and examples to plan investigations and distinguish observable security impact from an initial warning sign.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate browser-side security flaws in DOM handling, cross-window messages, Service Workers, and CSS. Trace untrusted input to sensitive operations and verify observable impact, helping distinguish reproducible vulnerabilities from harmless signals.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Assess Node.js applications for unsafe input handling and configuration weaknesses. The skill covers prototype pollution, where shared object properties are altered, plus template and command injection, proxy trust issues, and file exposure, with checks for observable impact.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Practice one programming concept through a small exercise matched to your goals, experience, and available time. Get feedback based on observable results, with hints or explained solutions and a harder variation when you are ready.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Frame a new design proposal (RFC-shape) under proposals/ — problem before solution, named beneficiary and observable change, real alternatives, honest drawbacks, and a live open-questions backlog. Read when asked to frame a proposal, write an RFC, propose a design, pitch a change, draft a PRD-style design doc, or open a design proposal for review. Do NOT read to record a decision after it is accepted (use record-a-decision), to write an implementation spec (use write-a-spec), to write a postmortem (use write-a-postmortem), or to review or critique an existing design (use review-a-design).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a website's observable HTTP traffic into a best-effort OpenAPI 3.1 spec by analyzing a `browser-trace` capture. Use when the user wants to discover/extract API endpoints from a browser session, build an OpenAPI doc from network traffic, or document a third-party site's XHR/fetch surface for client integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state and `@Observable` data flow, view composition, resizable layouts, safe areas, display scale, performance, lists, environment, localization, animation, Liquid Glass, and API migration. Also use for iPhone Duo, foldable, or large-display layouts (`NavigationSplitView` on large displays, iPhone tab sidebar, two-column reflow, foldable grids, `ArrangementView`, `ReservedRegion`), hinge effects, vertical bars, `@State` initialization or synthesized-property diagnostics, `@ContentBuilder` ambiguity, `reorderable` drag/drop, custom `AsyncImage` `URLSession`, swipe actions outside List, item-bound `alert`/`confirmationDialog`, `ToolbarOverflowMenu`, `AnimatableValues`, Document APIs (`Document`/`DocumentReader`), and Instruments `.trace` capture or analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reactive streams and event-driven programming in Golang using samber/ro — ReactiveX implementation with 150+ type-safe operators, cold/hot observables, 5 subject types (Publish, Behavior, Replay, Async, Unicast), declarative pipelines via Pipe, 40+ plugins (HTTP, cron, fsnotify, JSON, logging), automatic backpressure, error propagation, and Go context integration. Apply when using or adopting samber/ro, when the codebase imports github.com/samber/ro, or when building asynchronous event-driven pipelines, real-time data processing, streams, or reactive architectures in Go. Not for finite slice transforms (→ See `samber/cc-skills-golang@golang-samber-lo` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[omh] Evaluating a plugin, connector, or API for adoption: external connector readiness - assess whether a named plugin, connector, API, data provider, or multimodal route is safe, affordable, fresh, and observable; use toolbelt-readiness for missing capability inventory. Use when the user says: external-connector-readiness, external connector readiness, connector readiness matrix, plugin readiness matrix, provider readiness, api readiness, connector adoption, external plugin adoption.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[omh] Evaluating a plugin, connector, or API for adoption: external connector readiness - assess whether a named plugin, connector, API, data provider, or multimodal route is safe, affordable, fresh, and observable; use executor-runtime-readiness for coding-owner choice and toolbelt-readiness for missing capability inventory. Use when the user says: external-connector-readiness, external connector readiness, connector readiness matrix, plugin readiness matrix, provider readiness, api readiness, connector adoption, external plugin adoption.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical. Use when the user says: ai-slop-cleaner, cleanup, deslop, refactor, risky, behavior-preserving refactor, risk analysis, refactor workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write or revise an MVP product requirements document with scope and observable acceptance criteria.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply Martin Fowler-inspired refactoring rules when improving existing code structure while preserving observable behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze and design an Attio request governor with separate read and write budgets, query-score awareness, bounded retries, and observable backpressure. Use when an Attio integration receives 429 responses or needs safe concurrency controls. Trigger with "Attio rate limits", "Attio 429", or "throttle Attio requests".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bug-fix discipline — every defect has an etiology, the chain of cause that produced the observable fault; trace it before patching. Errors only grow: a bandaid leaks unless genuinely localized and leak-free. Walk the diagnostic ladder (presentation → proximate cause → API contract → isolated or systemic) before writing the fix. Use when authoring or reviewing any bug fix, regression patch, "quick fix" PR, or when deciding whether to ship, defer, or refactor.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write or review Windows regression tests for observable contracts, independent expectations, faithful fixtures, and distinct coverage without weakening native proof or architecture guards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SwiftUI 架构模式，使用 @Observable 进行状态管理，视图组合，导航，性能优化，以及现代 iOS/macOS UI 最佳实践。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SwiftUI 架构模式，使用 @Observable 进行状态管理，视图组合、导航、性能优化以及现代 iOS/macOS UI 最佳实践。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Change Octane's runtime, compiler, scheduler, reconciler, SSR, or hydration engine. Use before editing packages/octane/src. Covers the observable contract, hot-path analysis, and the performance evidence required before handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Records visual proof while testing UI behavior — the agent tests the app hands-on via computer use while a screen recording with structured test/assertion annotations captures the session — then posts the video and a results summary to the requested destination. Use when changed runtime behavior needs observable verification, including headless environments (scripted screenshots and probes) and non-UI changes (measured numbers, output pairs).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use when: planning, breaking down or scoping a change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Restructure existing code while preserving observable behavior. Use for targeted technical debt or hotspot work with characterization tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.