'logic' 검색 결과

Helps organize biological datasets and models in LaminDB. Covers data registration, table validation, annotation with standardized biological terms, metadata searches, and tracking analysis inputs and outputs so researchers can preserve the context needed to repeat their work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Register and organize biological datasets
• Validate DataFrame or AnnData metadata
• Standardize annotations with biological vocabularies

Find business logic repeated across software components, such as notifications, auditing, and validation. Compare responsibilities and dependencies, then recommend a shared service, shared library, or component merger with a prioritized consolidation plan.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding duplicate business logic before refactoring
• Reviewing whether notification components should be merged
• Identifying candidates for shared services or libraries

Detect business logic vulnerabilities in a codebase using a three-phase approach: threat modeling (domain analysis and attack scenarios), batched verify (check exploitable gaps in parallel subagents, 3 scenarios each), and merge (consolidate batch results). Covers price manipulation, workflow bypass, limit violations, race conditions, reward abuse, etc. Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/businesslogic-results.md. Use when asked to find business logic, logic flaws, or abuse-of-function bugs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates professional logical flow diagrams and logical system architecture diagrams using draw.io XML format (.drawio files). Use when creating: (1) logical flow diagrams showing data/process flow between system components, (2) logical architecture diagrams representing system structure without cloud provider specifics, (3) BPMN process diagrams, (4) UML diagrams (class, sequence, activity), (5) data flow diagrams (DFD), (6) decision flowcharts, or (7) system interaction diagrams. This skill focuses on generic/abstract representations, not AWS/Azure-specific architectures (use aws-drawio-architecture-diagrams for cloud diagrams).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Helps build and review NeuroKit2 research workflows for physiological recordings such as ECG, respiration, and skin conductance. Covers preprocessing, time alignment, event analysis, heart rate variability, and complexity measures, while recording methods and checking data quality.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Inspect physiological recordings before preprocessing
• Analyze ECG and heart rate variability for research
• Plan event windows and baseline correction

Set up Microsoft Sentinel to collect security logs from AWS, Azure, and GCP. Build detection queries, investigate historical activity, and create automated response workflows for a centralized security operations team.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Centralizing security monitoring across multiple clouds
• Migrating from an existing SIEM platform
• Automating responses to suspicious cloud activity

Build reusable parts for n8n workflows instead of copying shared logic. This skill guides typed inputs, consistent outputs, naming, and execution settings so workflows and AI agents can call the same processing steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Sharing common logic across workflows
• Splitting a large workflow into reusable parts
• Exposing shared processing as an AI agent tool

Build Native SDK app logic in TypeScript using explicit state, messages, and update functions. Explains the supported language subset, compiler diagnostics, module organization, and tests for logic that compiles directly into native code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing state and messages for a new app
• Fixing unsupported TypeScript constructs
• Splitting app logic into modules

Test application business rules by mapping workflows and checking unexpected actions, inputs, identities, and repetition. The skill helps investigate checkout, refunds, subscriptions, permissions, and concurrency flaws, then document reproduction steps and financial impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking checkout and refund workflows
• Testing price, quantity, and coupon rules
• Reviewing role and tenant boundaries

Build reusable parts for n8n workflows instead of copying shared logic. This skill guides typed inputs, consistent outputs, naming, and execution settings so workflows and AI agents can call the same processing steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Sharing common logic across workflows
• Splitting a large workflow into reusable parts
• Exposing shared processing as an AI agent tool

Domain routing and boundary guidance for authorized business logic vulnerability testing, including race conditions, flow bypass, price tampering, permission logic errors, and bulk operation abuse. Use when a task belongs to the logic testing domain and needs scope, evidence, pivot, or exit criteria.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert knowledge for Azure Logic Apps development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when building Logic Apps with AI/OpenAI, SAP/B2B, private endpoints, DevOps deployments, or DR/multi-region designs, and other Azure Logic Apps related development tasks. Not for Azure Functions (use azure-functions), Azure App Service (use azure-app-service), Azure Service Bus (use azure-service-bus), Azure Data Factory (use azure-data-factory).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Think and work like an expert Logician. Use when a task calls for Logician judgment. Reasons from syntax-versus-semantics and object-versus-metalanguage discipline, the ⊢/⊨ distinction, and matching each logic to its intended semantics through natural deduction and sequent calculus (cut-elimination, subformula property), compactness and Löwenheim–Skolem, forcing and diagonalization, and proof assistants (Lean 4/mathlib, Coq, Isabelle/HOL, Agda) with Z3/CVC5/Vampire/Mace4 automation while treating use–mention conflation, second-order misuse of compactness, mis-stated incompleteness hypotheses (ω-consistency vs consistency), and Gödel philosophical overreach as first-class failure modes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Protects complex business logic from accidental deletion or overwrite. Use when editing payment, trading, state-machine, or other load-bearing business logic where a single deleted line can cause silent data corruption. Maintains a logic manifest, enforces pre-edit gates, validates post-edit diffs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The logical structure of mathematical proof -- how first-order logic, natural deduction, and semantic reasoning combine to produce rigorous mathematical arguments. Covers the logical skeleton of direct proof, contraposition, contradiction, cases, and induction; the role of definitions, lemmas, and theorems; how informal mathematical prose maps to formal deductive structure; and the difference between proof-as-object and proof-as-activity. Use when the question is "why is this a valid proof?" rather than "what proof technique applies?"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deductive and inductive reasoning, formal and informal logical structure, validity, soundness, and rules of inference. Covers propositional logic, quantified reasoning, syllogisms, common inference patterns (modus ponens, modus tollens, hypothetical syllogism, disjunctive syllogism), and the distinction between deductive certainty and inductive probability. Use when the question is not whether a premise is true but whether the reasoning from premises to conclusion is logically valid.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Hunt business logic flaws — race conditions, workflow state bypass, parameter pollution affecting logic, coupon/discount abuse, refund logic, multi-step process bypass, integer overflow, negative quantities, double-spend. Use when looking for non-CVE bugs that require understanding the app's intended workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design combinational logic circuits from a functional specification through gate-level implementation. Covers AND, OR, NOT, XOR, NAND, NOR gates; NAND/NOR universality conversions; and standard building blocks including multiplexers, decoders, half/full adders, and ripple-carry adders. Use when translating a Boolean function or truth table into a hardware-realizable gate network and verifying it by exhaustive simulation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identify and exploit flaws in the core business rules and logic of web applications. This skill focuses on manipulation of application workflows, pricing, inventory limitations, and multi-step processes. Use this skill when bug hunting or testing e-commerce, banking, or SaaS platforms where standard technical vulnerabilities (e.g., XSS/SQLi) are not present but the application's logic is flawed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert-level mathematical logic knowledge. Use when working with propositional logic, first-order logic, proof theory, model theory, computability theory, Godel incompleteness theorems, set theory, type theory, or formal verification. Also use when the user mentions 'formal proof', 'Godel', 'incompleteness', 'Turing machine', 'decidability', 'Zermelo-Fraenkel', 'axiom of choice', 'model theory', 'completeness theorem', 'computability', 'formal language', or 'type theory'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Epistemic logic for multi-agent perceptual systems — Kripke models, vision sets, public announcement as coordination primitive, and satisfiability-as-reconfiguration applied to agents with limited observability. From Charrier, Ouchet, Schwarzentruber's "Big Brother Logic" demonstration paper (ENS Rennes / IRISA).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Business logic vulnerability testing for web/mobile/API engagements. Covers workflow bypass, state machine violations, multi-step process abuse, price/quantity/discount manipulation, currency confusion, coupon stacking, refund/chargeback abuse, race conditions on logic boundaries, parameter tampering for hidden flows, role/tenant boundary violations, time-of-check vs use, anti-automation defeat, fraud-detection evasion, and subscription/quota abuse. Use when scoping an application after surface-level OWASP Top 10 has been covered, or when the asset is a transactional/marketplace/fintech/e-commerce/SaaS app where logic flaws produce direct financial impact.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

처리 흐름과 상태 변화를 시험하는 HTML이나 여러 화면안을 전환하는 시제품을 만듭니다. 직접 조작하며 설계 의문을 확인하고 판단을 기록합니다.

• 복잡한 상태 변화를 직접 조작해 볼 때
• 서로 다른 화면 디자인을 비교할 때
• 비개발자에게 로직 시제품을 공유할 때

Review CSS spacing, borders, and positioning for conversion to logical properties, which follow writing direction. Check rendered layouts across screen sizes and interaction states to support right-to-left languages and vertical text.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adapting layouts for Arabic or Hebrew
• Replacing fixed left and right spacing in CSS
• Reviewing layouts for vertical writing