'case' 검색 결과

Use this skill whenever a lawyer or mediator needs help analyzing a dispute for mediation purposes. This includes: reviewing case materials (pleadings, contracts, correspondence, evidence) to identify issues in dispute, summarizing each party's position and interests, conducting legal analysis of the key issues, proposing mediation strategies or settlement directions, and preparing for mediation sessions. Trigger this skill when the user mentions 'mediation', 'dispute analysis', 'settlement', 'dispute resolution', 'identify issues in dispute', 'party positions', 'mediation brief', 'case analysis for mediation', 'ADR', 'mediation preparation', 'caucus strategy', 'settlement options', or any request to analyze a conflict between two or more parties with the goal of finding resolution. Also trigger when the user uploads case files and asks for a structured breakdown of who wants what, what the core disagreements are, or how the case might settle. Even if the user doesn't explicitly say 'mediation', trigger when the context involves analyzing opposing positions in a dispute with a resolution-oriented (rather than litigation-oriented) goal.

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

Expert blueprint for Godot 4 project organization (feature-based folders, naming conventions, version control). Enforces snake_case files, PascalCase nodes, %SceneUniqueNames, and .gitignore best practices. Use when starting new projects or refactoring structure. Keywords project organization, naming conventions, snake_case, PascalCase, feature-based, .gitignore, .gdignore.

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

Expert blueprint for Godot 4 project organization (feature-based folders, naming conventions, version control). Enforces snake_case files, PascalCase nodes, %SceneUniqueNames, and .gitignore best practices. Use when starting new projects or refactoring structure. Keywords project organization, naming conventions, snake_case, PascalCase, feature-based, .gitignore, .gdignore.

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

Finds a prospect company's own case-study or customer-stories page and pulls one named customer off it, so email 1 can open with "saw your work with Intercom". Triggers on "case study", "customer stories", "who are their clients", "saw your work with X", "name-drop one of their customers", "logos on their site". Outputs case_study_line, a short clause that finishes the sentence "Saw ...".

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

Build a single-product deep-dive showcase page as a self-contained HTML file. Triggers on: "build a product showcase page", "deep dive landing page for [product]", "create a product spotlight page", "product feature page", "single product page", "detailed page about [product]", "build a page showing everything about [product]", "create a long-form product page", "build a sales page for [product]", "product deep dive page", "make a feature breakdown page for [product]".

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

Provides edge case, corner case, boundary condition, and limit testing patterns for Java unit tests. Validates minimum/maximum values, null cases, empty collections, numeric overflow/underflow, floating-point precision, and off-by-one scenarios using JUnit 5 and AssertJ. Use when writing .java test files to ensure code handles limits, corner cases, and special inputs correctly.

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

Synthesize the single strongest EVIDENCE-BOUND reviewer case to reject a paper, built ONLY from the evidence ledger (claims.json) + the other auditors' confirmed findings — never free-floating LLM critique. Two fresh cross-model codex threads: an attack writes the ~200-word rejection paragraph (every accusation tagged to an existing claim_id/finding_id), a defense decomposes it and rules each point against the anchored evidence. MEMO-ONLY: emits adversarial-case-builder.memo.md (fed to the adjudicator via --memo) and carries NO verdict weight — tools/adjudicate_findings.py lists it in ZERO_WEIGHT_SKILLS and caps it at info. Honest-null allowed (the paper may survive). Run LAST. Detect-only. Adapted from ARIS kill-argument. Triggers: "adversarial case", "strongest objection", "rejection memo", "kill argument", "最强拒稿点".

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

Use this skill when writing acceptance criteria for Salesforce features, structuring UAT test scripts from user stories, classifying defects found during UAT, or planning regression testing before a Salesforce release. Trigger keywords: UAT, user acceptance testing, test script, acceptance criteria, defect classification, regression testing, test plan, test case. NOT for Given/When/Then AC syntax — use admin/acceptance-criteria-given-when-then. NOT for the per-case field schema and AC-to-case decomposition — use admin/uat-test-case-design. NOT for automated Flow or Apex test coverage — use flow/flow-testing. Also covers: UAT plan record, sandbox selection for UAT, pre-UAT environment checklist, sandbox email deliverability for testers, test-user personas, negative and bulk coverage, defect triage categories, go/no-go sign-off, quick-deploy window.

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

Guidance on non-obvious runtime behaviors of Salesforce standard objects — polymorphic lookups, lead conversion field loss, PersonAccount dual-nature, CaseComment trigger isolation, and Activity date fields. Also covers which trigger actually fires for a person account, the either/or Event duration contract, the Closed status category behind Task.CompletedDateTime, the 3-record merge cap and its single delete + single update trigger events, and the CaseComment post-insert write lock. Trigger keywords: person account trigger not firing, Contact trigger person account, Event required field EndDateTime, DurationInMinutes, CompletedDateTime null, merge MasterRecordId, CaseComment cannot be edited, IsNotificationSelected null, lead conversion triggers disabled. NOT for the Activity object model — use admin/activity-and-task-patterns. NOT for writing TYPEOF queries — use apex/apex-polymorphic-soql.

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

Use this skill to design, configure, and troubleshoot Salesforce Entitlement Management on Cases: entitlement processes, milestone definitions, recurrence types, milestone actions (success/warning/violation), business hours assignment, and entitlement templates. Covers the deployable EntitlementProcess / MilestoneType / EntitlementTemplate / EntitlementSettings metadata, signed timeLength time triggers, recurrenceType semantics, process versioning, and how a milestone actually completes. Trigger keywords: entitlement process, milestone, SLA timer, milestone tracker, first response SLA, time trigger, recursChained, CaseMilestone, EntitlementId, SlaProcess, stopped clock. NOT for SLA milestones on Field Service work orders — use admin/fsl-sla-configuration-requirements. NOT for time-based case escalation rules — use admin/escalation-rules. NOT for the business-hours calendar itself — use admin/business-hours-and-holidays.

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

Identify, score, and prioritize Salesforce AI use cases before any implementation begins — opportunity identification, Impact-Effort matrix scoring, feasibility evaluation across Technical/Operational/Data/Risk dimensions, and ROI framing. NOT for the license checks and enablement steps once a use case is approved — use agentforce/agentforce-service-ai-setup or agentforce/agentforce-sales-ai-setup. NOT for making the data model AI-ready — use architect/ai-ready-data-architecture.

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

Generates structured case briefs from judicial opinions. Use when the user provides a court opinion and needs a case brief, case summary, or distillation of a judicial decision for legal research.

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

Synthesizes multiple case summaries into one unified Case Summary Report. Triggers when the user has two or more case summaries, document analyses, or memoranda and needs them consolidated into a single report with patterns, contradictions, and gaps identified.

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

Produces U.S. litigation case chronologies with dated timelines, executive summaries, source attribution, gap analysis, and investigation recommendations. Use when asked for a chronology, timeline, case summary, or executive summary of a legal matter, or during case intake, deposition prep, or trial prep.

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

Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names, missing fields, huge counts, zero items, long labels, non-Latin text, emoji, extreme numbers — then render it behind a "Demo data / Worst case" toggle and report everything that broke, with the fix for each. Use when the user asks to stress-test, break, or find edge cases in a component or screen, or to "try the worst case". For visual design critique use emil-design-eng; for motion use review-animations.

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

Create a self-contained, visually polished HTML showcase page for a topic or set of artifacts. Supply a mission (topic summary) and optional artifact paths explicitly — the skill never auto-scans the repo. Writes output to assets/showcase/<mission>/. Screenshots are optional (requires Puppeteer). Publishing is local-only by default; publish requests without a configured path fail clearly.

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

Drafts one anonymised DRAFT case study (situation, approach, outcome as evidenced, optional lessons) from engagement notes, status reports, closing reports, emails and metrics extracts the user supplies, with a fact trace to the notes, an evidence grade on every result, quotes only where the user supplied them with speaker role and permission, an anonymisation log and a confidentiality checklist that must be completed before publication. Use when the user asks to "write a case study from these notes", "turn this engagement into a customer story", "draft a success story for the website", "anonymise this project write-up" or "prepare a reference case for the proposal". Do not use for redacting identifiers from an existing document, use document-deidentification-pass instead; for checking whether a document's claims are substantiated, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.

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

반복되는 null 검사를 Special Case(Null Object) 클래스로 대체하여 다형성으로 처리. "null 객체 패턴", "null 체크 반복 제거", "특수 케이스 클래스", "/introduce-special-case" 요청 시 사용. 단, 단순 전제 조건 명시는 /introduce-assertion, 타입별 분기 전반은 /replace-conditional-with-poly가 적합. /introduce-special-case [commit-ref]로 호출.

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

Enforces project coding standards during code review: naming conventions (PascalCase for classes, camelCase for methods/variables, UPPER_SNAKE_CASE for constants, kebab-case for files), standard file structure, anti-magic-number policy, file size limits (500/800 lines), security patterns, and design patterns. Use when reviewing code, writing new code, or checking adherence to project conventions.

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

From a KiCad board to a parametric enclosure that fits it: ERC and DRC clean, board dimensions extracted, an OpenSCAD case with your clearance, Gerbers exported, fab hand-off only after GO. Use for "PCB to enclosure", "case for this board", "KiCad to OpenSCAD case".

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

테스트를 먼저 작성하는 Go 개발을 돕습니다. 여러 사례 검증, HTTP 응답 확인, 성능 측정, 입력 자동 생성 검사와 커버리지 확인을 다룹니다.

• 테스트를 먼저 작성하는 Go 개발
• 정상 및 오류 테스트 사례 보완
• 처리 시간과 메모리 할당량 비교

슬라이드, 문서, 보고서, HTML 랜딩 페이지의 색상과 글꼴을 통일합니다. 열 가지 기본 테마를 선택하거나 원하는 분위기에 맞는 새 테마를 만들 수 있습니다.

• 슬라이드의 색상과 글꼴 통일
• 시각적 예시를 비교해 테마 선택
• 보고서와 문서의 외관 통일

기능 제안, 로드맵, 설계 검토, 회고 자료를 의사 결정용 HTML 슬라이드로 정리합니다. 여덟 가지 테마 중 하나로 전체를 통일하고 가로로 넘겨 볼 수 있게 만듭니다.

• 새 기능의 도입 이유 설명
• 로드맵 검토 자료 작성
• 기술 설계 대안 비교

시니어 디자이너 면접용 HTML 작품집 발표 자료를 만듭니다. 세 가지 프로젝트의 기법과 판단 근거를 정리하고, 노란색 포인트가 있는 정보 밀도 높은 잡지형 레이아웃으로 보여 줍니다.

• 시니어 디자이너 면접에서 작품집 발표
• 세 가지 프로젝트 사례 정리
• 디자인 판단의 이유와 근거 설명