238건 · 관련도순
Own the lifecycle of short-lived paid CPU/GPU hosts and attached resources, from bounded provisioning through verified permanent deletion. Use when renting, extending, retiring, or recovering billable remote resources; campaign scheduling belongs to run-ephemeral-hosts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive Mastra framework guide for building agents, workflows, tools, memory, workspaces, and storage with current APIs. Use for documentation lookup, API verification, TypeScript setup, common errors, migrations, and `mastra api` CLI tasks: inspect or call resources on local, Mastra platform, Trace Intelligence, or remote servers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Best practices for Remotion - Video creation in React
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinate eval, benchmark, load-test or batch campaigns on authorized SSH hosts or short-lived rented hosts, with isolated jobs, configured-path canaries, telemetry and evidence. Use manage-remote-resources for paid resource ownership and run-remote-builds for build-only offload.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Offload builds, tests, or artifact verification to authorized SSH hosts and isolated worktrees; synchronize remote fixes into dedicated coordinator commits and preserve reproducible build provenance. Use for spare development capacity and remote build troubleshooting. Paid provisioning requires a separate resource lifecycle contract.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scientific model and eval tuning loop for prompt/skill/system-prompt changes, model configuration, runtime options, and local/Ollama model sizing or environment variables. Use when tuning eval performance, comparing local or remote models, improving tool-use behavior, reducing timeouts/loops, or deciding whether an eval optimization is worth keeping.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigate anonymous or stealth model identities by correlating model availability with provider outages and OpenRouter or Vercel AI Gateway incident reports. Use for stealth-model attribution or maintaining an outage evidence ledger.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compatibility entry for remote GPU resource management. Follow the project-local manage-remote-resources lifecycle skill; GPU inference readiness is a workload-specific reference.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess package choices and generated dependency names, publisher or release anomalies, incident exposure, and changes in package risk reports. Use before trusting a new dependency, when a release changes unexpectedly, or when investigating a supply-chain alert.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a network probe, DNS lookup, HTTP fetch, or nmap scan reports the target host or the internet is unreachable. Stops further probing and reports a target-readiness blocker with useful diagnostics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safely develop, verify, and document proof-of-concept exploits and payloads for authorized targets inside isolated Workspace Containers. Use when a Hypothesis is well-founded, target authorization covers scope, and each active step will carry a durable approval — for minimal PoCs, impact verification, or reproducible exploit Evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when explicitly authorized lab traffic must be captured, searched, or exported from the project's mitmproxy-backed Docker lab recorder.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the extended Corpo Net range suite across many models on one remote host with parallel isolated range instances, local Langfuse recording, bounded spend, and verified teardown. Use when asked to run, rerun, or scale a Corpo Net campaign; use run-ephemeral-hosts for the host contract and manage-remote-resources for billable resource ownership.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Authorized testing of LLM applications, agents, chatbots, RAG systems, guardrails, and tool-using model workflows. Use for LLM mode selection, jailbreak and prompt-injection assessment, guardrail bypass review, tool misuse, tool or system prompt disclosure, data exfiltration paths, model refusal/stop detection, bypass hypotheses, and hardening guidance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use common CLI, Kali, and shell tools to inspect web Targets, captured assets, logs, HAR/PCAP files, packages, and generated artifacts, then turn observations into Evidence, Security Signals, and ranked Hypotheses. Use when the user asks for web bug-hunting inspection, digital records, URL maps, crawling, endpoint discovery, JS bundle/package analysis, light forensics, or command-line investigation workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generalize published Spectre and remote microarchitectural research into passive target prerequisites, defensive review, and approval-gated local validation. Use for shared runtimes, JavaScript isolates, edge workers, serverless platforms, browser sandboxes, remote timing, cache side channels, speculative type confusion, or Dynamic Process Isolation analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze suspicious SMS/email messages, phishing links, redirects, domains, payloads, malware indicators, and suspected C2 infrastructure safely. Use when the user provides spam, smishing/phishing content, raw .eml headers, URLs, QR links, attachments, hashes, strange payloads, redirect chains, DNS/WHOIS/RDAP questions, C2 clues, exploit-chain questions, or asks what defenses to apply.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Passive, citation-grounded review of security-relevant specifications, protocols, standards, APIs, and implementations. Use when a reviewer must trace external preconditions and invariants into source code without treating a cited claim as proof of a vulnerability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Record measured or directly seen security-research behavior as cited Observations, classify it against reusable security concepts, and decide whether it remains an observation, becomes a Lead, or supports a Finding. Use after passive analysis, a tool run, a probe, a crash, a timing anomaly, or a user-supplied behavioral report produces noteworthy evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Passive, pattern-calibrated risk discovery for authorized security research over an open-source project, repository URL, dependency, release, or local checkout. Use when the security research agent needs to find highest-risk areas, map attack surface, identify likely bug-hunting targets, prioritize security review, inspect structural/logical/security-critical code, compare vulnerable versus patched versions, reason from broad high-severity vulnerability families, or remember areas of interest for later attack-chain research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.