'logic' 검색 결과

Estimates the minimum biological replicates (or cells/events) for a target power at a target FDR in genomics experiments using ssizeRNA, PROPER, powsimR for scRNA-seq, and pilot-data dispersion estimation from DESeq2/edgeR. Covers the biological-versus-technical replication distinction (technical replicates do not add degrees of freedom for biological inference), replicate-number-versus-sequencing-depth budgeting, scRNA-seq sample-versus-cell allocation under a pseudobulk model, and the critique that "n=3" is a publication convention rather than a power calculation. Use when budgeting a sequencing experiment, writing the sample-size justification in a grant, estimating replicates from pilot data, allocating a fixed budget between samples and depth, or planning scRNA-seq cohort size. For clinical-trial sample size see clinical-biostatistics/power-and-sample-size; for the power-given-n direction see experimental-design/power-analysis.

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

Fix the psychologically significant moment, not the logically significant metric — Rory Sutherland on experience. Use when the outcome is fine but the journey feels bad: complaints about waiting, anxiety, uncertainty, or 'it's technically fast/cheap/correct but people still hate it'; when the user asks 'how do we reduce complaints', 'how do we make waiting/onboarding/checkout feel better', 'people are anxious during X', or is about to spend big to shave a number (wait time, load time, steps) when the real pain is how the moment feels. Covers uncertainty reduction, idle vs occupied waiting, and the peak-end rule. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「待ち時間のクレームが多い」「手続きの途中で離脱される」「お客様を不安にさせている」）にも使う。中文咨询（“等待时间投诉多”“办理中途流失”“让客户感到不安”）也适用。

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

Rory Sutherland's 'psycho-logic' approach to marketing, product, and business problems — solve the human perception, not just the engineering or economic metric. Use when the obvious 'logical' fix is expensive, slow, or already done by every competitor; when the user asks 'how do we make people want X', 'the product/price/funnel is fine but nobody converts', 'how do we stand out', 'is there a cheaper way to fix this', or mentions behavioral economics, nudges, irrational behavior, perception, or 'it doesn't make sense but it works'. This is the ROUTER skill: it diagnoses the problem in human terms, then dispatches to reframing, costly-signaling, counterintuitive-tests, or experience-design. Inspired by Rory Sutherland's book *Alchemy*. 日本語の相談（「商品はいいのに売れない」「値下げしかない？」「競合と差別化できない」）にも使う。中文咨询（“产品很好却卖不动”“只能降价吗？”“无法差异化”）也适用。For a catalogue of individual biases, use marketing-psychology (separate plugin) instead.

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

The live fieldwork layer for psycho-logic — go look at the actual target market NOW instead of reasoning from your training-data stereotype of it. Use when a psycho-logic move needs grounding in a specific place: the user asks 'what do competitors in [region/country] actually do', 'what's the real price band / norm here', 'how do local leaders position themselves', 'research this market before we localise', 'what signals trust to buyers in X', or is about to launch/adapt in a market you haven't studied. Runs structured web research in the local language — local competitors and their signals, price bands, category conventions, review/trust sources, local terminology, taboos and regulations — and synthesises a compact perception profile the four moves consume. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic; pair with cultural-context (the lens that tells you what to look for). 日本語・中文の相談（「現地の実態を調べて」「调研当地市场」）にも使う。

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

Generate ideas that don't sound logical, then validate them with cheap behavioural experiments — Rory Sutherland's 'the opposite of a good idea can be a good idea' plus revealed-preference testing. Use when the obvious/logical solution is saturated and the user wants genuinely different options, asks 'what's a creative/unconventional angle', 'how do we stand out', 'should we run a test/experiment', 'how do we know what people actually want', or is about to trust a survey/focus group. Covers deliberate inversion of the obvious move, why stated preferences lie, and designing small reversible experiments that watch behaviour. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「競合と同じ案しか出ない」「アンケートは好評なのに売れない」「思い切った案を安く試したい」）にも使う。中文咨询（“只能想出和竞品一样的方案”“问卷好评却卖不动”）也适用。

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

Estimates the minimum biological replicates (or cells/events) for a target power at a target FDR in genomics experiments using ssizeRNA, PROPER, powsimR for scRNA-seq, and pilot-data dispersion estimation from DESeq2/edgeR. Covers the biological-versus-technical replication distinction (technical replicates do not add degrees of freedom for biological inference), replicate-number-versus-sequencing-depth budgeting, scRNA-seq sample-versus-cell allocation under a pseudobulk model, and the critique that "n=3" is a publication convention rather than a power calculation. Use when budgeting a sequencing experiment, writing the sample-size justification in a grant, estimating replicates from pilot data, allocating a fixed budget between samples and depth, or planning scRNA-seq cohort size. For clinical-trial sample size see clinical-biostatistics/power-and-sample-size; for the power-given-n direction see experimental-design/power-analysis.

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

Estimates the minimum biological replicates (or cells/events) for a target power at a target FDR in genomics experiments using ssizeRNA, PROPER, powsimR for scRNA-seq, and pilot-data dispersion estimation from DESeq2/edgeR. Covers the biological-versus-technical replication distinction (technical replicates do not add degrees of freedom for biological inference), replicate-number-versus-sequencing-depth budgeting, scRNA-seq sample-versus-cell allocation under a pseudobulk model, and the critique that "n=3" is a publication convention rather than a power calculation. Use when budgeting a sequencing experiment, writing the sample-size justification in a grant, estimating replicates from pilot data, allocating a fixed budget between samples and depth, or planning scRNA-seq cohort size. For clinical-trial sample size see clinical-biostatistics/power-and-sample-size; for the power-given-n direction see experimental-design/power-analysis.

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

Hunting skill for business logic vulnerabilities. Built from 12 public bug bounty reports. Covers coupon-race-stacking (Instacart, Stripe, Reverb), negative-quantity-in-cart price tampering (Upserve, Eternal/Zomato), decimal/fraction price-field overflow (Shipt), client-side checkout amount trust on PayPal redirect (WordPress.org), price-per-unit mass-assignment (Krisp), and archived-price swap / cart-TOCTOU (Stripe). Use when hunting business logic — heavy emphasis on financial-impact-demonstrated cases.

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

Django 앱의 구조, API, 데이터 조회, 캐시 구현과 검토를 돕습니다. 환경별 설정과 업무 로직을 분리하고 불필요한 데이터베이스 조회를 줄이는 예시를 제공합니다.

• Django 구조와 설정 정리
• Django REST Framework API 설계
• 불필요한 데이터베이스 조회 줄이기

Node.js, Express, Next.js의 API와 서버 데이터 처리를 설계하고 검토합니다. 데이터베이스 조회, 캐시, 인증, 오류 처리를 정리합니다.

• API 설계와 업무 로직 및 데이터 조회 분리
• 중복 데이터베이스 조회 줄이기
• 캐시와 비동기 처리 도입

Android와 KMP 프로젝트의 모듈 구조와 의존 관계를 정리합니다. 업무 로직·화면·데이터 접근을 분리해 설계하고 구현 예시로 각 계층의 역할을 설명합니다.

• Android와 KMP 프로젝트 구조 설계
• 화면 코드에서 업무 로직 분리
• 기기와 서버의 데이터 접근 설계

새 기능과 버그 수정 전에 실패하는 테스트를 작성합니다. 최소 구현과 코드 정리를 반복하며 기대 동작과 기존 기능에 미치는 영향을 확인합니다.

• 테스트를 먼저 작성한 뒤 구현
• 보고된 버그 재현과 수정
• 코드 변경 시 기존 동작 확인

설계와 구현의 중요한 결정을 작업 이력을 공유하지 않는 별도 검토자에게 검증받습니다. 숨은 전제와 실패 조건을 찾아 수정하거나 결정을 재검토합니다.

• 설계안의 전제 검증
• 익숙하지 않은 코드의 판단 확인
• 인증과 민감한 처리 로직 검증

Map a codebase into feature flowcharts, find duplicated logic, and propose a simpler shared architecture. Produce source-linked diagrams, an evidence-based duplication report, and prompts for handing each proposed system to /make-plan.

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

• Map feature flows before a refactor
• Find duplicated logic within and across features
• Compare a unified architecture with existing call sites

Restructure claude-flow v3 into focused modules using Domain-Driven Design, which groups code by responsibility. Define module boundaries, event communication, and plugin interfaces to support a modular architecture with independently testable business logic.

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

• Split an oversized orchestrator into focused modules
• Define boundaries between tasks, sessions, and monitoring
• Design plugin extensions and domain events

Restructure claude-flow v3 into focused modules using Domain-Driven Design, which groups code by responsibility. Define module boundaries, event communication, and plugin interfaces to support a modular architecture with independently testable business logic.

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

• Split an oversized orchestrator into focused modules
• Define boundaries between tasks, sessions, and monitoring
• Design plugin extensions and domain events

Evaluate whether tests catch defects in business logic, calculations, or state machines. Using Stryker, the skill introduces small code changes, reviews which changes escape detection, and helps strengthen tests where important behavior is insufficiently checked.

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

• Checking test quality beyond code coverage
• Introducing Stryker for a single module
• Strengthening tests for critical calculations

Review source code with Strix to trace data flow and authorization checks, then test suspected vulnerabilities in a running environment. Receive proven findings with exploit examples and code locations, while keeping unconfirmed observations clearly identified.

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

• Reviewing a repository for security vulnerabilities
• Checking authorization logic in a specific service
• Reviewing security risks introduced by a branch

Plan and write tests for changes to agent behavior, favoring integration tests that check components together. Identify key logic changes and user-visible behavior to cover, reuse existing helpers, and keep unit tests in dedicated files.

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

• Identify test coverage for changes to agent logic
• Add integration tests for user-visible behavior
• Organize unit tests in dedicated files

Understand customer decisions and turn psychological principles into practical marketing ideas. The skill explains relevant thinking tools and behavioral patterns, then suggests ethical applications for pricing, trust, messaging, onboarding, retention, and deciding which marketing problems to address first.

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

• Exploring why customers hesitate to purchase
• Reviewing how prices and plans are presented
• Building trust through testimonials and evidence

Write small, reproducible Python scripts and run them in a sandbox using execute_python. Check the script's logic and output, then report the actual results or errors while clearly distinguishing executed results from code that has not been run.

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

• Checking a Python script's logic
• Confirming actual output from a short script
• Reproducing an error with minimal code

Find biological pathways and functions enriched in gene lists or ranked gene data. Choose an appropriate statistical method, align gene identifiers, define comparison backgrounds, and turn results into interpretable tables and plots with multiple-testing corrections.

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

• Finding enriched pathways among differentially expressed genes
• Running GSEA on a complete ranked gene list
• Calculating gene-set scores for individual samples or cells

Turn descriptions of scientific components and relationships into PNG diagram drafts with Nano Banana 2. Gemini 3.7 Flash reviews each draft and may request one revision, while saved image versions and review logs support manual checking.

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

• Drafting neural network architecture diagrams
• Illustrating biological pathways
• Creating study flowcharts

Analyze DepMap cancer model data to rank genes required for cell survival, compare groups defined by biological markers, and explore drug responses. Release tracking and statistical checks help organize evidence for research hypotheses.

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

• Ranking gene dependencies in cancer models
• Comparing groups defined by biological markers
• Finding genes with similar dependency patterns