1.1천건 · 관련도순
Create and wire Replica prototype controls. Use when asked to add or change dropdowns, sliders, input fields, toggles or action buttons that configure variants, scenarios, visible UI, app state or data sources, even without canvas terminology. Covers declarations, typed bindings, defaults, conditions, resets and actions. Product UI form fields and filters alone belong to create-prototype.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level medical device design covering regulatory pathways, design controls, biocompatibility, sterilization, risk management, and verification and validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check proposed stack, data flows, cloud choices, and delivery controls against declared enterprise policies, compliance frameworks, and security controls. Trigger at R2/R3 risk classification, before locking architecture decisions, or when the operating profile names a governance pointer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a vulnerability exception and risk acceptance tracking system with approval workflows, compensating controls documentation, and expiration management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill details how to conduct cloud security audits using Center for Internet Security benchmarks for AWS, Azure, and GCP. It covers interpreting CIS Foundations Benchmark controls, running automated assessments with tools like Prowler and ScoutSuite, remediating failed controls, and maintaining continuous compliance monitoring against CIS v5 for AWS, v4 for Azure, and v4 for GCP.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused security controls, or mapping detection gaps to kill chain phases. Activates for requests involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed Martin kill chain framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compares one policy against one requirement set (standard, regulation, contract schedule or customer requirement) clause by clause and returns a draft gap review: each requirement element, the policy clause that appears to address it, an apparent match state, and every gap as a question with the clause reference on both sides. Never concludes that the policy complies; the owner decides. Use when the user asks to "gap our policy against the standard", "map this policy to the regulation clause by clause", "check the security policy against the customer's contract schedule", "compare our policy with the new edition" or "where does our policy fall short of the requirements". Do not use for mapping a requirement to the operating controls that implement it, use controls-gap-pack instead; for what a regulatory change means for the organisation, use regulatory-change-impact-note. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns the text of a regulatory change (new regulation, amendment, rule, guidance or standard revision) into a DRAFT impact note: what changed against the prior text where supplied, who is affected as the text scopes it, an obligations table with dates and owners to confirm, and open interpretation questions for legal. States only what the text says; the rest is UNKNOWN. Use when the user asks to "brief legal on this new regulation", "list what we must do by when under this amendment", "compare the new standard with the version it replaces", "turn this directive into an obligations table" or "what does this rule mean for us". Do not use for assessing existing controls against a requirement set, use controls-gap-pack instead; for gapping a policy against a standard, use policy-gap-review. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runtime release controls for deployless repositories. Use when a repo needs feature flags, kill switches, capability gates, targeted rollout, remote config, routing rules, or a provider-neutral release-control facade independent of language and provider.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Register a custom Dynamic Visibility condition for JetEngine — extend \Jet_Engine\Modules\Dynamic_Visibility\Conditions\ Base, hook jet-engine/modules/dynamic-visibility/conditions/register, call $manager->register_condition( new MyCondition() ). The 3 abstract methods are get_id() / get_name() / check( $args = [] ); override get_group() to assign a UI group, is_for_fields() / need_value_detect() / need_type_detect() to control where the condition appears, get_custom_controls() to add per-condition UI controls. The check() $args includes type ('show' or 'hide'), field / field_raw, value, data_type ('chars' / 'numeric' / 'datetime' / 'date' / 'list'), and context ('default' or 'current_listing'). Important — $args['type'] is the user's show/hide intent; condition must invert its boolean accordingly. Use get_current_value() helper for context-aware meta resolution (handles WP_Post, WP_User, WP_Term, WP_Comment, listing macros). Use when scaffolding a JetEngine companion plugin's visib...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert en audit interne (risk assessment, controls, compliance, recommendations, DZ context)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Survey the whole tdmcp project and produce a prioritized list of NEW features it could implement — across artist controls, CLI/DX, AI/LLM integration, and TouchDesigner depth. Use whenever the user wants to brainstorm, discover, survey, list, or audit what features/tools/effects/controls/commands/prompts/capabilities tdmcp *could* add, asks 'what could we build / what's missing / what are the opportunities / ideas for the project', or wants a feature backlog or gap analysis. Also for follow-ups: re-run, refresh, update, re-survey, deepen, or re-prioritize the backlog, or survey just one surface (e.g. 'CLI ideas only'). This is the IDEATION harness — it produces a list to decide from; it does NOT build. When the user has already chosen a feature and wants it implemented/shipped/added, use tdmcp-pipeline instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
bu skill details how to conduct cloud security audits using Center for Internet Security benchmarks for AWS, Azure, and GCP. It covers interpreting CIS Foundations Benchmark controls, running automated assessments with tools like Prowler and ScoutSuite, remediating failed controls, and maintaining continuous compliance monitoring against CIS v5 for AWS, v4 for Azure, and v4 for GCP.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements secure API key generation, storage, rotation, and revocation controls to protect API authentication credentials from leakage, brute force, and abuse. The engineer designs API key formats with sufficient entropy, implements secure hashing for storage, enforces per-key scoping and rate limiting, monitors for leaked keys in public repositories, and builds key rotation workflows. Activates for requests involving API key management, API key security, key rotation policy, or API credenti...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements security controls at the API gateway layer including authentication enforcement, rate limiting, request validation, IP allowlisting, TLS termination, and threat protection. The engineer configures API gateways (Kong, AWS API Gateway, Azure APIM, Apigee) to act as a centralized security enforcement point that validates, throttles, and monitors all API traffic before it reaches backend services. Activates for requests involving API gateway security, API management security, gateway a...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a vulnerability exception and risk acceptance tracking system with approval workflows, compensating controls documentation, and expiration management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill details how to conduct cloud security audits using Center for Internet Security benchmarks for AWS, Azure, and GCP. It covers interpreting CIS Foundations Benchmark controls, running automated assessments with tools like Prowler and ScoutSuite, remediating failed controls, and maintaining continuous compliance monitoring against CIS v5 for AWS, v4 for Azure, and v4 for GCP.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused security controls, or mapping detection gaps to kill chain phases. Activates for requests involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed Martin kill chain framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end shotgun metagenomics workflow from FASTQ to taxonomic and functional profiles, orchestrating controls/host depletion, Kraken2+Bracken classification, MetaPhlAn marker profiling, and HUMAnN functional profiling. Covers the controls-first ordering, why Kraken2 read counts are not abundances and MetaPhlAn cell fractions do not equal Bracken read fractions, and the consistent-pipeline framing. Use when profiling shotgun metagenomic samples end to end, or chaining classification, abundance, and function. For resistome see metagenomics/amr-detection; for strains see metagenomics/strain-tracking; for assembly see genome-assembly/metagenome-assembly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Three.js (three, WebGL / WebGPU 3D グラフィクス) r186 リファレンス。 Scene, Group, PerspectiveCamera, OrthographicCamera, WebGLRenderer, WebGPURenderer, RenderPipeline、 BufferGeometry, BufferAttribute, StorageBufferAttribute, Mesh, InstancedMesh, SkinnedMesh、 MeshStandardMaterial, MeshPhysicalMaterial, ShaderMaterial, node-materials (TSL)、 DirectionalLight, SpotLight, PointLight, AmbientLight, PMREMGenerator、 GLTFLoader, FBXLoader, DRACOLoader, TextureLoader、 AnimationMixer, AnimationClip, AnimationAction, KeyframeTrack, Timer、 AudioListener, PositionalAudio、 Vector3, Matrix4, Quaternion, Euler, Color, Box3, Raycaster、 OrbitControls, TransformControls, WebXRManager。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Windows アプリ開発 (WinUI 3 / Windows App SDK) のコントロール API リファレンス。 Microsoft.UI.Xaml.Controls。Button, CheckBox, RadioButtons, ToggleSwitch, Slider, TextBox, RichEditBox, AutoSuggestBox, NumberBox, ListView, GridView, ItemsView, ItemsRepeater, TreeView, ComboBox, NavigationView, TabView, Frame, SplitView, BreadcrumbBar, ContentDialog, Flyout, CommandBar, TeachingTip, InfoBar, MediaPlayerElement, WebView2, CalendarView, DatePicker, ColorPicker, TitleBar。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
React Flow (ノードベース UI / フロー図ライブラリ for React) リファレンス。 ReactFlow コンポーネント、Node, Edge, Handle, Viewport、 カスタムノード / エッジ、Controls / MiniMap / Background、 レイアウトアルゴリズム (dagre, elkjs)、ドラッグ&ドロップ、エッジ接続。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Declare an agentic application's interaction disclosure, state, context, capabilities, and effect-control boundaries. Use for a reviewable design specification and static consistency audit before implementation. NOT for proving that controls are deployed or enforced, exposing private chain-of-thought, selecting a model/router, or designing a multi-agent protocol.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.