'entry' 검색 결과

Plan a Chinese company's entry into an overseas market (出海): choose the market with evidence, then plan entity, payments, localisation, compliance, channels and team for the first twelve months. Use when asked 出海计划, 我们要进入东南亚 / 中东 / 欧洲 / 美国市场, how should a Chinese company expand overseas, or a go-global plan. Produces a market scorecard, a twelve-month entry plan by workstream, the compliance and data checklist for the chosen market, and the top risks with mitigations. Bilingual output on request.

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

Create data-driven presentation slides using React, Vite, and Recharts with Sentry branding. Use when asked to "create a presentation", "build slides", "make a deck", "create a data presentation", "build a Sentry presentation". Scaffolds a complete slide-based app with charts, animations, and single-file HTML output.

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

Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.

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

Use the official Sentry CLI to investigate issues, events, traces, and logs for Vibe Remote without committing Sentry credentials into the repository.

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

Intent-driven spec precipitation — state a constraint in natural language (加一条规范：禁止用 any / 记录架构约束：服务间走 gRPC / 质量规则：覆盖率≥80%) and the workflow infers the category and records a <spec-entry>. Spec = 项目约束规则（编码规范、架构约束、质量标准）；可复用知识文档走 /maestro-knowhow capture。Triggers on "maestro-spec add", "记录规范", "添加约束", "添加规则", "加一条规范", "spec add". Terminology：spec = project constraints/rules (<spec-entry>). Reusable knowledge documents use /maestro-knowhow capture. Learning discoveries from /maestro-learn use <learning-entry> tags in learnings.md (separate from spec entries).

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

Guides conducting privacy law gap analysis for market entry into new jurisdictions. Covers target jurisdiction assessment, existing compliance mapping, remediation effort estimation, and implementation timeline planning. Keywords: gap analysis, market entry, jurisdiction assessment, remediation planning, compliance mapping.

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

Create or review journal entry prep deliverables with traceable assumptions, decision criteria, ownership, and risk controls. Use when the user asks for journal entry prep planning or analysis.

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

Evaluate an open source project's AGENTS.md and produce a corpus entry for the /agents-md directory. Use when adding a project to the directory, refreshing an existing entry, or running a batch of candidate repositories.

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

Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining `04-prd.md` into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different decision at step 5/8. Phase 0 also defines compressed intake, the path a user's explicit "just build it" choice takes on full-stack-app, pwa-app, authored, and copywriting cores: one batched round of questions in place of the shelf, writing a thinned archive at the same paths so Phase 1 (or, on copywriting, that core's own mining step), `ux-planner`, and the Re-entry pass all keep their documented source. Also use for the Re-entry pass, which mines new scope into additional intents without re-running the shelf, on any core with a module axis to add an intent to (full-stack-app, pwa-app, authored) — landing-page has none, so its own new-scope path runs through `hedgehog-landing-loop`'s Correction Protocol instead. Invoked by the `planner` agent, which decides the path; don't run standalone. landing-page runs this skill's Phase 0 on first run, then mines the same archive through `hedgehog-landing-loop`'s own planning-intake section, that core's counterpart to this skill's Phase 1. copywriting runs this skill's Phase 0 the same way (full or compressed), then mines the same archive through `hedgehog-copywriting-loop`'s own planning-intake section into a what/audience/register brief — no module axis, so its own new-scope path runs through that loop's Correction Protocol rather than the Re-entry pass below. An authored core runs this skill's Phase 0, then `hedgehog-core-design`, then this skill's Phase 1 mining against the designed layer sequence. A brownfield adoption (`hedgehog-adopt`) never runs this skill's shelf at all — the drivers BMAD elicits are already settled facts of a repo that already exists.

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

Use this skill when configuring or troubleshooting NPSP soft credits, partial soft credits, or matching gift workflows — including OpportunityContactRole-based credit attribution, npsp__Partial_Soft_Credit__c records, and the Find Matched Gifts process. NOT for gift entry templates or batch gift entry — use admin/gift-entry-and-processing. NOT for importing historical gifts and credits — use data/gift-history-import.

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

Use when configuring the Salesforce product catalog and pricing structure: creating Product2 records, setting up Standard and custom Pricebooks, managing PricebookEntry junction records, enabling multi-currency pricing, configuring Product Schedules (Revenue and Quantity), or troubleshooting incorrect prices on Opportunity line items and Quotes. Triggers: 'add product to pricebook', 'pricebook entry', 'standard pricebook', 'product catalog', 'multi-currency product pricing', 'product schedule', 'revenue schedule', 'quantity schedule', 'deactivate product'. NOT for bulk catalog loads — use data/product-catalog-data-model. NOT for CPQ bundles and product rules — use admin/cpq-product-catalog-setup.

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

Eliciting and documenting a sales process before it is built in Salesforce: stage sequencing, entry/exit criteria per stage, win/loss analysis requirements, and stage transition rules. Trigger keywords: sales process design, stage discovery, entry criteria, exit criteria, stage gate, win/loss categorisation, sales methodology, pipeline stages, opportunity stage mapping, stage ladder, probability ladder, forecast category mapping, required fields per stage, stage swim lane, discovery workshop, handoff brief. NOT for configuring OpportunityStage, Sales Processes or Path in Setup — use admin/opportunity-management. NOT for cross-functional swim-lane maps — use admin/process-flow-as-is-to-be.

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

Design resilient React error handling with Error Boundaries, Sentry integration, recovery UI, retry patterns, and graceful degradation. Activate on: error boundary, crash recovery, Sentry, error fallback UI, retry logic, unhandled exceptions. NOT for: form validation errors (use form-validation-architect), API error codes (use api-architect).

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

Repository または subsystem を対象に、source-only で明示的なセキュリティ監査を行う entry skill。 通常の PR セキュリティレビューとは分離し、reconnaissance、scope 固定、既存 security skill への委譲、 evidence と unresolved hypothesis、observe-only SecurityAuditCoverage、coverage critic、 structured audit artifact と repeat-run coverage を扱う。target-controlled code は実行しない。

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

6つの専門レビュアーロールを並列実行し、consensusLevel（複数ロールの合意度）と Tech Lead レポート（top3指摘・blindSpots・consensusSummary）で結果を統合する マルチエージェントレビュー entry skill。 Parallel multi-role review with consensus scoring (consensusLevel) and Tech Lead report. Use when a major release needs exhaustive multi-angle review, or when a single-perspective review is not enough and you want confidence that no reviewer angle was missed（重要リリース前の網羅レビュー・多視点の確証が 欲しいとき）。

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

敵対的分析手法を統合したレビューの entry skill。認知バイアス対策の3手法 （Pre-mortem / War Game / Logic Torturing）と、宣言・主張と実態の乖離を突く claim-vs-actual 検出3パターン（Self-Contradiction / Refactor-Claim Audit / Cross-File Leakage）へルーティングし、通常のレビューでは見えない設計の盲点・ 防御の穴・論理の弱点・宣言と実装のズレを可視化する。

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

Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.

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

Design resilient React error handling with Error Boundaries, Sentry integration, recovery UI, retry patterns, and graceful degradation. Activate on: error boundary, crash recovery, Sentry, error fallback UI, retry logic, unhandled exceptions. NOT for: form validation errors (use form-validation-architect), API error codes (use api-architect).

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

Sentry error tracking and monitoring for OneKey. Use when configuring Sentry, filtering errors, analyzing crash reports, or debugging production issues. Covers platform-specific setup (desktop/mobile/web/extension) and error filtering strategies.

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

Analyze and fix production errors from Sentry crash reports. Use when investigating AppHang, ANR, crashes, or production errors. Includes complete workflow from JSON analysis to bug fix implementation with evidence-based methodology. Triggers on sentry, crash, AppHang, ANR, error analysis, production error, bug analysis, crash report, freeze, hang, not responding, stacktrace, breadcrumbs, exception.

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

CodexBar의 로컬 비용 로그에서 Codex나 Claude의 비용을 모델별로 집계하고, 최근 대표 모델이나 전체 모델의 내역을 텍스트 또는 JSON으로 확인합니다.

• 최근 대표 모델의 비용을 확인합니다
• 전체 모델의 사용 비용을 비교합니다
• 내보낸 비용 로그를 집계합니다

TypeScript 패키지 내부 파일의 직접 참조와 순환 의존성을 감지합니다. 공개 파일만 진입점으로 쓰도록 설정하고 예제, 검증, 문서까지 마련합니다.

• 패키지 내부 파일의 직접 참조를 막을 때
• 타입 검사와 함께 패키지 경계를 확인할 때
• 복사해서 쓸 패키지 틀을 만들 때

AI가 조작하는 GStack Browser를 화면에 표시해 실행합니다. 사이드 패널에서 실시간 조작 기록을 보고 채팅으로 페이지 이동, 클릭, 입력과 내용 읽기를 요청합니다.

• AI의 브라우저 조작 관찰
• 채팅으로 페이지 이동과 입력 요청
• 품질 검사와 디자인 검토 중 조작 확인

UI/UX 설계를 검토할 때 에이전트가 도입 후보를 찾도록 돕는 카탈로그 항목입니다. 검색 데이터와 템플릿은 없으며 실제 사용에는 원본 배포 파일 전체가 필요합니다.

• UI/UX 설계 참고 후보 찾기
• 필요한 파일의 설치 상태 확인
• 원본 배포처의 설치 방법 확인