333건 · 관련도순
Analyzes malicious and vulnerable Windows kernel drivers (.sys) by parsing the PE for the native subsystem, identifying DriverEntry/IRP dispatch and IOCTL handlers, and flagging BYOVD and kernel-callback abuse. Activates for requests to analyze a Windows driver, examine a .sys sample, or assess a BYOVD/kernel driver threat.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of an animal trainer — designing a behavior-modification plan for a specific problem behavior, choosing a reinforcement schedule and deciding when to raise criteria, structuring session length and frequency to avoid fatigue or frustration plateaus, or setting a handler/public safety protocol around a training animal.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a fully customized Amazon Connect AI agent PoC bundle (Lambda handlers, OpenAPI spec, AI agent prompt, Contact Flows, CloudFormation/CDK infrastructure, FAQ knowledge base) from a ~15-minute structured interview — or from a requirements doc, a flow sketch, or an existing flow/prompt you want to improve. Triggers on "amazon connect", "aicc", "contact center AI", "connect ai agent", "connect ai agents domain", "agentic cx designer", "acxd", "connect customer", "agentic cx block", "requirements document", "improve my contact flow", "flow sketch", "\uc544\ub9c8\uc874 \ucee4\ub125\ud2b8", "\ucee8\ud0dd\uc13c\ud130 AI \uc0c1\ub2f4\uc6d0".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a fully customized Amazon Connect AI agent PoC bundle (Lambda handlers, OpenAPI spec, AI agent prompt, Contact Flows, CloudFormation/CDK infrastructure, FAQ knowledge base) from a ~15-minute structured interview — or from a requirements doc, a flow sketch, or an existing flow/prompt you want to improve. Use when the user wants to build, scaffold, prototype, or refine an Amazon Connect contact center, an AI voice/chat agent on Amazon Connect, or any contact-center use case that mentions Connect, Lex, Wisdom, Q in Connect, "AI agent domain", or Agentic CX Designer (ACXD, Connect Customer, the Agentic CX block — the ACXD runtime target). Also triggers on "I have a requirements document", "turn this flow sketch into a Contact Flow", or "improve my existing Contact Flow / AI prompt". Produces 6 asset packages on local disk.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Parse natural-language quantities, units, dates, and ranges ("5'11\"", "1.5 cups", "72 in to cm", "three days ago", "between 5 and 10 kg", "it's hot") into canonical, validated values with issue codes and spans — and humanize them back. Use when a form input, LLM tool schema, MCP handler, or import pipeline takes free-text measurements/units/dates. Covers Standard Schema fields (quantityField/dateField/lingoObject) for the AI SDK and MCP, the headless <lingo-input>, unit conversion, and format/humanize round-trips. Zero-dependency TypeScript, deterministic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spring Boot 4 REST API implementation patterns. Use when creating REST controllers, REST endpoints, request validation, exception handlers with ProblemDetail (RFC 9457), API versioning, content negotiation, WebFlux reactive endpoints, HTTP clients with @HttpExchange, JSON serialization with Jackson 3, error handling, or CORS configuration. Covers @RestController patterns, Bean Validation 3.1, global error handling, and declarative HTTP clients.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deep cross-layer consistency audit for any codebase. Traces every feature from UI to database, finds broken wiring, missing handlers, model mismatches, and security gaps. Auto-fixes critical and warning issues. Use this after building features, before releases, or whenever something feels off. Works with any tech stack.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Presentation/Core/Engine split control plane — the canonical entry point for any work decomposing the Yuzu server into three binaries (presentation · core · engine) per ADR-0031-presentation-core-engine-decomposition / ADR-0032 (the admission interlock) / ADR-0033 (access-control spine). Use when the user says "/split", "/pce-split", "/decomposition", asks to plan or implement a split workstream (WS-A*, WS-B*, WS-X*), asks "what's our gap to the presentation/core split" or "is it safe to extract presentation/the engine yet", asks to audit split readiness, or starts work touching the seam (handlers calling stores directly, the INV-31-4 contract test, the Drogon port, `server/presentation` or `server/engine`, the `uce` DB grants, component service identity, or the ADR-0032 admission/grant/audit substrate — `use_case_run_id`, the release log, the capability-declaration registry).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a subscriber admin is installing, upgrading, or rolling back a managed package (1GP or 2GP) sourced from AppExchange or a private install URL — covers pre-install evaluation, sandbox dry runs, license and dependency checks, the install/upgrade audit trail, post-install configuration the package's InstallHandler cannot perform, and uninstall fallback. NOT for building managed packages as an ISV (use devops/managed-package-development), unlocked-package development (use devops/unlocked-package-development), or AppExchange listing setup. Trigger keywords: InstalledPackage, installedPackages, securityType, activateRSS, sf package install, sf package installed list, PackageLicense, UserPackageLicense, AllowedLicenses, UsedLicenses, push upgrade, PackageSubscriber, namespace prefix, 04t, certified managed package limits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when adding external users to an Experience Cloud site, configuring self-registration, managing external user licenses, or customising the login and registration pages. Trigger keywords: add members to community, external user license, self-registration, customer portal login, partner user onboarding, ConfigurableSelfRegHandler. NOT for choosing which external user license to buy — use architect/experience-cloud-licensing-model. Also covers the networkMemberGroups membership block, NetworkMemberGroup assignment status, external-user creation from contacts, offboarding, and LoginHistory diagnosis for site logins. NOT for what records external users can see — use security/experience-cloud-security.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configures global exception handling middleware
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Advanced OpenClaw skill creation handler that executes the official 5-step research flow with comprehensive analysis and best practices. Ensures proper methodology when users request to create or modify OpenClaw/Moltbot/ClawDBot skills following official standards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building data pipelines, ETL jobs, event processors, message-broker producers/consumers, application caching layers, database migrations, BigQuery queries, or event-sourcing handlers in TypeScript. Triggers on edits to indexer/ETL/migration code, Prisma or Drizzle schemas, BigQuery integration code, RabbitMQ/Kafka/SQS/BullMQ producer or consumer code, Redis cache wrappers, or mentions of "data engineering", "ETL", "pipeline", "indexer", "event sourcing", "data warehouse", "data migration", "message queue", "RabbitMQ", "Kafka", "SQS", "BullMQ", "Redis cache", or "caching".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate CLI command with argument parsing, handler, help text, and tests
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building APIs on Hono (Cloudflare Workers, Bun, Deno, Node), debugging route ordering, wiring middleware, validating with @hono/zod-validator, returning streaming responses, configuring CORS with credentials, handling errors via app.onError, or composing typed RPC clients. Triggers: c.env binding types, c.header + c.redirect interaction, missing await next() bugs, Set-Cookie not attaching to redirect, route-precedence surprises, JWT middleware setup, hono/client typed RPC end-to-end. NOT for Express/Fastify/Koa idioms, tRPC/GraphQL paradigms, or Next.js Route Handlers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
CQRS pattern, event stores, projections, eventual consistency. Activate on: CQRS, event sourcing, event store, read model, projection, aggregate, domain event, command handler. NOT for: message broker setup (use event-driven-architecture-expert), database optimization (use data-warehouse-optimizer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing a background-job system, choosing between BullMQ / Sidekiq / RQ / Temporal / SQS, deciding queue-vs-workflow, sizing concurrency vs rate limits, building dead-letter queues, or making handlers idempotent. Triggers: jobs running twice on retry, lost jobs after worker crash, DLQ filling up, Redis OOM from job backlog, exactly-once requested, "do we need Temporal?", visibility timeout / lockDuration confusion, exponential backoff vs jitter, fan-out fan-in workflows. NOT for outbound webhook publishing (different concerns), receiver-side webhook handling (different concerns), event-streaming/Kafka topology, or in-process async (event loop only).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates OpenAPI 3.0/3.1 specs, TypeScript client types, and curl examples from existing route handler code. Supports Express, Next.js API routes, Fastify, and Hono. Produces complete documentation including auth requirements, rate limits, error codes, and request/response examples. Activate on: 'generate API docs', 'OpenAPI from code', 'document endpoints', 'API reference', 'swagger generation', 'endpoint documentation'. NOT for: API design from scratch (use api-architect), deployment (use devops-automator), testing (use test-automation-expert).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search for raw byte patterns (hex sequences, opcodes) in binary code. Use when looking for specific instruction sequences, machine code patterns, UEFI SMI handlers, or known vulnerability signatures by their byte representation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and implement backend changes end to end: endpoints, handlers, services, integrations, webhooks, jobs, authenticated access. Routes contracts to api-design-principles, schema to database.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing or reviewing Go code in fusionaly-oss — adding routes, handlers, domain contexts, background jobs, the manager CLI, wiring the app, or writing tests. Covers the cartridge framework, matcha for the manager, Phoenix Contexts, lifecycle/shutdown, and the test conventions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The primary tool for code-navigation questions in ANY language (frontend or backend) — walk the structural graph from an entry point (page, route, handler, command, `main`) down through imports to the IO boundary (network call, query, file read). Use this skill, in preference to the Explore agent or global grep, whenever the user asks "where does X come from?", "what API/data populates Y?", "what renders or wraps the Z panel?", "which file for feature F?", "how is this wired up?", or any code-navigation question mapping a UI element, route, or feature concept to source files. Also reverse queries ("what uses /api/foo?", "who consumes this service?"). Keyword search routinely picks up unrelated flows sharing a domain word and produces wrong answers; the walk follows the actual graph. The JS/TS `walk.mjs`/`discover.mjs` are an optional accelerator, not required — the walk is language-agnostic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design conventions for this codebase. Use whenever writing or reviewing API endpoints, route handlers, or HTTP clients.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.