40건 · 관련도순
Understand and extend GitNexus taint analysis, which tracks data from input sources to potentially dangerous operations. Use its implementation guidance to investigate missed or incorrect findings, add detection models, and validate analysis changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guides systematic mapping of international personal data flows across an organisation. Covers system-by-system inventory methodology, third-party identification, transfer mechanism assignment, gap analysis, and data flow visualisation. Keywords: data flow mapping, international transfers, data inventory, transfer register, cross-border data flows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
코드 변경과 시스템 구성을 움직이는 SVG 그림으로 설명합니다. 변경 부분과 주변 구성 요소의 관계, 데이터 흐름을 시각화해 풀 리퀘스트에서 공유하도록 돕습니다.
자연어, Mermaid, 코드 근거로 시스템 구성도와 업무 흐름, 시간선 등을 만들고 검증하여 독립적으로 열람할 수 있는 대화형 HTML로 출력합니다.
Identify security threats across system components and data flows, score their risks, and prioritize mitigations. Run a quick scan for exposed credentials and route requests beyond threat modeling to the appropriate specialist skills.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Translate approved game designs into a technical blueprint before coding begins. Map system layers, module responsibilities, data flow, and API boundaries, then check architecture decisions against the pinned engine and identify missing knowledge or decisions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn plain-language descriptions or Mermaid diagrams into interactive, standalone HTML diagrams of systems, workflows, API exchanges, data flows, and state changes. Validate layouts, explore relationships, switch themes, and export diagrams as images or video.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guides authorized source code security reviews across dangerous functions, data flow, authentication, logic flaws, and dependencies. Helps agents prioritize review paths and organize code locations, reproduction evidence, and remediation advice before drawing conclusions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
WHAT: Draws a code change or part of a codebase as an animated architecture or data-flow diagram, on its own or in a pull request. WHEN: asked to diagram, visualise or explain a change or a system, or when a pull request should carry a diagram. KEYWORDS: PR Lens, diagram, architecture, data flow, visualise, visualize, pull request
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Privacy planning reference for data-flow reasoning, standards mapping, and DPIA thresholds
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for architecture, current-state, process, data-flow, medallion, or DP diagrams, including redrawing .drawio and Mermaid sources. Creates branded flowchart, sequence, ER, org, timeline, and chart visuals as standalone HTML/SVG/PNG.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SwiftUI's actual mental model — view identity, lifetime, and dependencies (the Demystify canon), state ownership decision rules, Observation's per-property tracking, body-performance discipline, and the main-actor concurrency contract. Use when state resets mysteriously, views re-render too often, animations glitch between branches, choosing @State vs @Bindable vs plain property, or debugging "why did body run."
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates a Mermaid sequence diagram showing how data moves between components. Use when tracing request flows or documenting data transformation pipelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SaaS vendor data processing inventory management. Covers shadow IT discovery, API-based data flow detection, processing purpose mapping, contract status tracking, and continuous inventory reconciliation for cloud service providers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conducts comprehensive inventory of protected health information across the enterprise per HIPAA Security Rule requirements at 45 CFR §164.308(a)(1)(ii)(A) and §164.310(d). Covers identification of all ePHI repositories, data flow mapping, classification of PHI by sensitivity, and integration with risk analysis. Keywords: PHI inventory, ePHI, data mapping, information asset, data flow, HIPAA risk analysis, designated record set.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements data lineage tracking for privacy compliance including origin tracking, transformation logging, access auditing, deletion verification, and cross-system lineage graphs. Covers source-to-sink mapping, GDPR Art. 30 RoPA integration, automated lineage discovery, and breach impact scoping. Keywords: data lineage, data provenance, data flow mapping, transformation logging, deletion verification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds comprehensive data inventory per GDPR Art. 30 Records of Processing Activities. Covers system-by-system discovery, data flow diagramming, third-party identification, and legal basis per category. Keywords: data inventory, data mapping, Art 30, RoPA, data flow, processing activities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify bug-introducing commits using semantic analysis that extends traditional SZZ algorithm. Distinguishes semantic changes from refactorings or code movements using control-flow and data-flow similarity analysis. Use when analyzing bug-fix commits to trace back to bug-introducing changes, investigating software evolution, conducting empirical studies on defect prediction, or reducing false positives in bug localization. Supports git repositories and provides explanations for why commits are identified as bug-introducing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a reader needs an editorial architecture, flowchart, sequence, state, ER, swimlane, loop, layer-stack, data-flow, or process diagram as self-contained HTML/SVG. Symptoms: 'draw the system', 'architecture diagram', 'sequence of calls', 'state machine visual'. Not for logos, OG images, or Marp decks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews Remix v2 loaders and actions for mutations-in-loader, missing validation, leaked server fields, wrong return helpers, v1 useTransition holdovers, and revalidation traps. Use when reviewing loader/action code in a Remix v2 codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Remix v2 data loading and mutations. Use when writing loaders, actions, deferred data, revalidation logic, or pending state. Triggers on loader, action, useLoaderData, useActionData, json(), defer(), <Await>, shouldRevalidate, useRevalidator, useNavigation, useTransition (v1 holdover).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a covered entity or business associate needs to know where protected health information lives and moves, or asks "map our PHI", "ePHI inventory", "HIPAA data flow diagram", "where does patient data go", "PHI flow map for the risk analysis", "which vendors need a BAA" or "do our logs contain PHI". Traces health data from where it enters, through systems, integrations, logs, backups and vendors, to where it leaves and is disposed of, records the safeguards that cover each flow and the business associate agreement behind each external one, and lists the gaps as input to the security risk analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid. Also use for Archify, interactive or animated HTML diagrams, インタラクティブ図, 動く構成図. When an editable .drawio file is required, use the draw.io workflow instead and treat Archify HTML only as a supplement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a full feature in this Flutter repository that includes backend or storage data flow: read API schema, create DTOs, map DTOs to entities, add Riverpod use cases, connect feature state, and render UI data. Use when a task goes beyond a screen and needs real data integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.