테스트·보안 스킬

Audit a page the way a search engine reads it: what it is about, whether that is obvious, and the three fixes worth doing before anything else.

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

Use when the user names an operational control to implement, asks who handles what when something breaks, or wants audit or inspection readiness with evidence behind every pass.

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

Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing a value proposition. Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation, see design-sprint. For non-leading interview technique, see mom-test.

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

Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less. Use when the user mentions "customer interviews", "validate my idea", "users say they want it but dont buy", "leading questions", "The Mom Test", "customer feedback bias", or "interview script". Also trigger when preparing user-research questions, interpreting ambiguous feedback, or designing customer-discovery that avoids false positives. Covers commitment and advancement, avoiding compliments, and extracting signal from noise. For product-market fit, see jobs-to-be-done. For rapid prototype testing, see design-sprint.

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

Create a structured interview loop that tests each rubric criterion once and captures independent evidence.

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

Triage an intermittent test from run history, environment, and failure pattern before naming a cause.

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

Use when a large deal needs procurement, legal, security, and pricing orchestration: mutual close plans, deal-desk runs, and signature.

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

Prepare a neutral brief for counsel or the security lead on a matter that needs their judgement.

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

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.

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

Use when deals must clear compliance gates: licensing, suitability, audit readiness, and regulated-ops checks before close.

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

Track compliance requirements and audit readiness. Trigger with "compliance", "audit prep", "SOC 2", "ISO 27001", "GDPR", "regulatory requirement", or when the user needs help tracking, preparing for, or documenting compliance activities.

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

Set up compliance work from policies, system inventory, audit reports, approved answers, and counsel contacts.

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

Read an ad test by sample size and spread, and say whether there is a winner yet.

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

Set up dependency and security hygiene from repository evidence, with a clear scope, source list, risk queue, and approval line.

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

Draft a narrow dependency upgrade pull request with evidence, code changes, tests, risk notes, and rollback instructions.

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

Review a dependency change for breaking APIs, runtime shifts, supply-chain risk, test gaps, rollout risk, and rollback quality.

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

Review a deal for evidence gaps across need, scope, stakeholders, process, competition, delivery, security, legal, and commercial approval.

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

Audit CRM fields by fill rate, format, and use, and propose keep, fix, or retire for each.

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

Use when an outsourced support vendor handles your customers: audit the queue, score the sample, calibrate the vendor, and lift capability with evidence.

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

Check cap-table records against signed source documents and report ownership, security, date, and total differences for expert review.

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

Performs security-focused differential review of code changes. Adapts analysis depth to codebase size, uses git blame for context, calculates blast radius by counting callers, checks test coverage of modified code, and generates a markdown report. Use when reviewing a PR, commit, or diff for security vulnerabilities, checking whether a change re-introduces a previously fixed bug, asking what else a change could break, or finding which modified code has no test covering it.

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

Conventions for dependency injection and mocking in Spring Boot in this project. Use this whenever writing, reviewing, or refactoring integration test classes (anything annotated @SpringBootTest, or under src/test that talks to a real Spring context), especially when deciding how to wire dependencies or mock collaborators. Also consult this before adding @Autowired, @MockBean, @MockitoBean, or field injection in any test class.

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

Conventions for using parallelization in all tests using Jupiter

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

Conventions for using annotations in all tests using Jupiter

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