'behavioral' 검색 결과

Prepare for engineering interviews with structured practice in algorithms, system design, and questions about past experience. Develop explanations of your reasoning, analyze solution efficiency, discuss design tradeoffs, and organize concrete stories about your work.

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

• Practicing algorithm problems and explaining solutions
• Rehearsing system design interviews
• Structuring stories about past work experience

Analyze meeting transcripts to understand speaking habits, interruptions, conflict avoidance, and listening patterns. Get specific examples with timestamps and practical suggestions, then compare meetings over time to track changes in communication and facilitation.

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

• Find moments when difficult conversations were avoided
• Review speaking time and interruptions
• Assess facilitation in team meetings

Audit recovered bug reproduction tests before writing a fix or reviewing a pull request. Check that assertions reflect intended behavior, establish a valid failure on unfixed code, and verify the same test passes after the fix.

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

• Checking recovered reproduction tests before fixing a bug
• Validating test evidence for a pull request
• Rewriting weak assertions around actual behavior

Review an existing bug-fix pull request using validated reproduction tests and the complete code diff. Assess root-cause coverage, scope, and regressions, then document behavioral evidence and follow the workflow's branch and approval rules.

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

• Independently verifying an existing bug-fix pull request
• Checking a complete diff for scope and root-cause coverage
• Recording the user journey on the proposed fix

Build a developer profile from past sessions or a questionnaire, then generate files and settings that personalize Claude's responses. Choose which outputs to create and compare changes when refreshing an existing profile.

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

• Documenting development habits and preferences
• Building a profile through a questionnaire
• Generating settings to personalize Claude's responses

Guide an AI agent through code changes with explicit assumptions, simple implementations, focused edits, and testable goals. Use it for bug fixes, features, refactoring, or reviews to reduce guesswork and unnecessary changes.

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

• Fixing a bug with a test that reproduces it
• Adding a feature without expanding its scope
• Refactoring while preserving existing behavior

Calculate change risk for a specific .NET method, class, or file by combining code complexity with measured test coverage. Get ranked results and recommendations on where to add tests or simplify logic.

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

• Calculate risk scores for a specific method
• Prioritize tests within a class
• Find complex, undertested methods in a file

Move existing .NET 9 projects to .NET 10 by updating project settings and dependencies, fixing build errors, and reviewing behavior changes. Includes CI and Docker updates, followed by builds, tests, and security checks.

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

• Upgrading an existing .NET 9 project to .NET 10
• Fixing build errors and warnings after an SDK upgrade
• Reviewing ASP.NET Core and EF Core behavior changes

Upgrade an existing .NET 8 project to .NET 9 by addressing build errors and compatibility changes. Update related packages, containers, and build pipelines, then verify the migration with clean builds and tests.

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

• Upgrading a project from net8.0 to net9.0
• Resolving new build errors and warnings after upgrading
• Reviewing ASP.NET Core and EF Core behavior changes

Find changes in observable behavior that existing tests could miss. Map public results to test assertions, identify gaps in boundaries, permissions, and calculations, and propose focused tests, with optional verification when requested.

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

• Check whether existing tests would catch a bug
• Find missing boundary and permission-denial tests
• Review exact amounts and rounding in financial calculations

Upgrade an existing .NET 10 project to .NET 11 by updating framework targets and packages, fixing compatibility issues, reviewing runtime behavior changes, and verifying builds, tests, and deployment configuration.

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

• Upgrading a project from net10.0 to net11.0
• Fixing build errors after an SDK upgrade
• Reviewing changes in runtime and EF Core behavior

Review test files or suites for missing checks, hidden exceptions, unreliable timing, shared state, and maintenance problems. Get a severity-ranked report with specific locations, explanations, and concrete suggestions for improving the tests.

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

• Reviewing whether existing tests meaningfully check results
• Investigating timing and execution-order risks in tests
• Prioritizing test improvements before editing code

Optimize .NET loops with SIMD, which processes multiple values in one operation, or review existing SIMD code. Check behavioral equivalence, memory safety, platform fallbacks, and benchmarks to establish whether the optimization is correct and worthwhile.

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

• Optimize numeric loops with SIMD
• Review existing vectorized code for correctness
• Test boundary lengths and overlapping buffers

Map a single-page application's backend API from its public JavaScript files, including routes loaded later. Compare unauthenticated responses with a protected endpoint to investigate missing authentication and access control using minimal evidence.

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

• Discovering backend API routes in public JavaScript
• Checking API authentication behind an SSO login
• Investigating routes in lazily loaded JavaScript files

Parallel read-only multi-agent review of a current git diff or explicit file scope to find behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps. Use when the user asks for a review swarm, parallel review, diff review, regression review, security review, or wants high-signal issues plus a prioritized fix path without editing files.

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

Generate developer behavioral profile and create Claude-discoverable artifacts

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

Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.

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

Authoring and running behavioral evals for a shopping or merchant agent, covering the case shape, authoring rules, code graders and judges, the run pattern, and poisoned fixtures. Load when writing eval cases or rubrics or deciding how a suite runs.

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

Synthesize qualitative and quantitative user research into structured insights and opportunity areas. Use when analyzing interview notes, survey responses, support tickets, or behavioral data to identify themes, build personas, or prioritize opportunities.

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

Use when the user asks to "build email segments from my list", "make engaged / lapsed / RFM segments", "set up cart-abandoner or lifecycle-stage audiences", or "build a suppression list of unsubscribes and bounces"; turns the user's OWN list/CRM/GA4/ecommerce export into behavioral, attribute, and lifecycle-stage segments plus a suppression list, with per-segment sizes labeled Measured/Estimated, informing the SEND E (Engagement/targeting) dimension. Not for scoring EQS or running vetoes — use email-quality-auditor; not for authentication or spam-content checks — use deliverability-qa. 邮件列表分群/生命周期分群/抑制名单/流失召回

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

Design products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation". Use when the user mentions "pricing", "how much should we charge", "willingness to pay", "pricing page", "packaging", "freemium vs free trial", "are we leaving money on the table", "nobody buys at this price", "price increase", or "good-better-best". Also trigger when designing or auditing pricing and packaging, validating willingness to pay before building, segmenting customers by value, or choosing between subscription, usage-based, and freemium models. Covers price-before-product, willingness-to-pay talks, the four failures (feature shock, minivation, hidden gem, undead), leader/filler/killer packaging, and behavioral pricing. For offers and guarantees, see hundred-million-offers. For what customers value, see jobs-to-be-done.

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

Code review behavioral standards. Reference during code review to ensure consistent quality checks from a QA perspective.

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

Applies decision science and cognitive bias research to marketing and product decisions — how people actually choose under uncertainty, and how framing, defaults, sequencing, and social context change behavior. Use this to diagnose why a well-argued offer is not converting, to structure choices and pricing presentation, to design an experience around how attention and memory work, or to pressure-test whether a persuasion tactic is legitimate or manipulative.

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

Expert malware analyst specializing in defensive malware research, threat intelligence, and incident response. Masters sandbox analysis, behavioral analysis, and malware family identification. Handles static/dynamic analysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage, threat hunting, incident response, or security research.

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