'screen' 검색 결과

Observe the user's screen via screenpipe, detect repeated research workflows, match them against existing scientific-agent-skills, and draft new skills (or composition recipes that chain existing ones) for the patterns not yet covered. Use when the user asks to analyze their recent work and propose skills based on what they actually do. Requires the screenpipe daemon (https://github.com/screenpipe/screenpipe) running locally on port 3030 — the skill has no other data source and will refuse to run if screenpipe is unreachable. All detection runs locally; only redacted cluster summaries reach the LLM.

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

Use this skill when a new product feature, vendor, AI use, monitoring tool or change in processing raises the question "do we need a DPIA", or someone asks "DPIA screening", "is this high risk processing", "data protection impact assessment threshold", "privacy impact screening for this feature", "does our AI feature need a DPIA" or "document why we did not do a DPIA". Describes the processing with numbers, tests it against the GDPR cases, the supervisory authority's list and the EDPB-endorsed criteria, reaches a reasoned outcome (required, recommended, not required) with a re-screen trigger, and keeps a screening log for accountability.

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

Reads one export transaction, order or shipment description and returns a DRAFT export review pack: parties to screen with a screening checklist, an item classification worksheet, a red-flag review, licence-determination questions and open items. Use when the user asks to "prepare the export review for this order", "pre-check this shipment for export control", "who do we need to screen on this deal", "build the classification worksheet for this item" or "assemble the trade-compliance file for this technology transfer". Do not use for vendor security or due-diligence screening of a supplier's questionnaire answers; use vendor-risk-screening-brief instead. Never classifies, screens, clears, decides licence need or releases a shipment; trade compliance does. Drafts for human review; never approves, authorises or signs off.

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

Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (`asc screenshots frame`), and screenshot upload (`asc screenshots upload`). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition, or screenshot-to-upload pipelines.

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

When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.

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

Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (`asc screenshots frame`), and screenshot upload (`asc screenshots upload`). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition, or screenshot-to-upload pipelines.

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

Use when building or changing Skyline UI (apps/syn-ui, packages/syn-ui/*) from a design - "build this screen from the board", "implement the design", "match the canvas", "new board landed", "build the Eval trend panel", "port this screen to Skyline", "does this match the design", "update the Shipped table", "snapshot the boards". Covers reading a `*.dc.html` board and the Skyline spec, building from them, comparing 1440px and 390px screenshots against the board, and recording the shipped screen. Do NOT use for small tweaks to a screen that has already shipped (change the code directly, no board needed), for the frozen React app apps/syn-dashboard-ui (never edit it), or for refreshing the CI screenshot baselines alone (see design/README.md).

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

Analyzes CRISPR drug-modifier (chemogenomic) screens with drugZ (Li & Hart 2019 Genome Med), a bidirectional Z-score method that identifies synthetic-lethal sensitizing genes and resistance-conferring suppressor genes from vehicle vs drug comparisons. Covers vehicle-anchored design (not Day-0), the bidirectional Z math giving 2-3x sensitivity over MAGeCK / STARS / edgeR / RIGER on drug screens, per-gene sumZ and normZ, synth (sensitizer) vs supp (suppressor) FDR, multi-dose handling, integration with control sgRNAs, and comparison with MAGeCK MLE with dose covariate. Use when running a drug-modifier CRISPR screen, identifying sensitizing or resistance genes for a drug candidate, choosing drugZ vs MAGeCK MLE for chemogenomic analysis, troubleshooting low-effect drug screens where MAGeCK lacks sensitivity, or designing a drug-screen layout (vehicle vs drug arms).

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

Designs and analyzes combinatorial CRISPR screens covering paired-Cas9 (Big Papi, Najm 2018), enhanced AsCas12a multiplex (enCas12a, DeWeirdt 2021), in4mer 4-guide-array Cas12a (Esmaeili Anvar N et al 2024 Nat Commun 15:3577) and the Inzolia paralog-pair library, paralog-buffering detection (Dede 2020 Genome Biol; Thompson 2021 Cell Reports 36:109597), genetic-interaction (GI) scoring as observed_double_LFC minus expected_additive_double_LFC, synthetic-lethal and synthetic-rescue interaction interpretation, the half-of-essentiality buffered by paralogs phenomenon, multiplex screen statistical analysis with MAGeCK MLE interaction terms, and the relationship to single-cell combinatorial Perturb-seq. Use when designing a paralog or pathway-pair screen, choosing between paired-Cas9 (Big Papi) and Cas12a multiplex (Inzolia), interpreting genetic interaction scores, identifying synthetic-lethal targets for drug development, or scaling beyond single-gene CRISPR screens.

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

Designs and analyzes combinatorial CRISPR screens covering paired-Cas9 (Big Papi, Najm 2018), enhanced AsCas12a multiplex (enCas12a, DeWeirdt 2021), in4mer 4-guide-array Cas12a (Esmaeili Anvar N et al 2024 Nat Commun 15:3577) and the Inzolia paralog-pair library, paralog-buffering detection (Dede 2020 Genome Biol; Thompson 2021 Cell Reports 36:109597), genetic-interaction (GI) scoring as observed_double_LFC minus expected_additive_double_LFC, synthetic-lethal and synthetic-rescue interaction interpretation, the half-of-essentiality buffered by paralogs phenomenon, multiplex screen statistical analysis with MAGeCK MLE interaction terms, and the relationship to single-cell combinatorial Perturb-seq. Use when designing a paralog or pathway-pair screen, choosing between paired-Cas9 (Big Papi) and Cas12a multiplex (Inzolia), interpreting genetic interaction scores, identifying synthetic-lethal targets for drug development, or scaling beyond single-gene CRISPR screens.

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

Analyzes CRISPR drug-modifier (chemogenomic) screens with drugZ (Li & Hart 2019 Genome Med), a bidirectional Z-score method that identifies synthetic-lethal sensitizing genes and resistance-conferring suppressor genes from vehicle vs drug comparisons. Covers vehicle-anchored design (not Day-0), the bidirectional Z math giving 2-3x sensitivity over MAGeCK / STARS / edgeR / RIGER on drug screens, per-gene sumZ and normZ, synth (sensitizer) vs supp (suppressor) FDR, multi-dose handling, integration with control sgRNAs, and comparison with MAGeCK MLE with dose covariate. Use when running a drug-modifier CRISPR screen, identifying sensitizing or resistance genes for a drug candidate, choosing drugZ vs MAGeCK MLE for chemogenomic analysis, troubleshooting low-effect drug screens where MAGeCK lacks sensitivity, or designing a drug-screen layout (vehicle vs drug arms).

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

모바일 앱의 화면 흐름을 가로로 나란히 놓은 스마트폰 틀 세네 개로 시각화합니다. 회색 임시 블록, 화살표, 번호가 붙은 동작명과 주석으로 이동 과정을 정리합니다.

• 시작 안내부터 홈까지 흐름 정리
• 상품 상세부터 확인까지 경로 검토
• 시각 디자인 전에 화면 전환 검토

코드나 글로 된 설명을 바탕으로 Figma 화면을 만들고 갱신합니다. 디자인 시스템의 구성 요소와 색상, 여백 등의 공통 설정으로 앱 화면을 재현합니다.

• 앱 코드를 Figma 디자인으로 옮깁니다
• 글로 된 설명에서 화면을 만듭니다
• 공통 구성 요소로 화면을 갱신합니다

Review image loading settings based on where images appear on a page. Identify offscreen images that should load later, keep important visible images loading promptly, and add image dimensions to reduce layout shifts.

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

• Reviewing lazy loading for images below the first screen
• Checking loading priority for hero images
• Adding dimensions to lazy-loaded images

Operate and test terminal apps without a display using named background sessions. Wait for visible screen changes, send keystrokes, reproduce Cline CLI bugs, capture text or PNG evidence, and write automated tests of interactive behavior.

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

• Reproducing Cline CLI interface bugs without a display
• Running an interactive process in the background
• Writing automated tests for terminal interactions

Guide web app testing with screen readers such as VoiceOver, NVDA, and JAWS. Check forms, dialogs, keyboard navigation, and spoken update notifications to identify accessibility problems across desktop and mobile browser combinations.

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

• Checking form labels and error announcements
• Testing dialog focus behavior
• Verifying announcements for changing content

Upload local screenshots, images, PDFs, archives, and videos to GitHub, then embed them in pull requests, issues, or comments. Use gh-attach to obtain attachment URLs and download existing GitHub attachments to a specified local destination.

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

• Attach before-and-after screenshots to a pull request
• Add an explanatory image to an issue
• Share PDFs or videos in comments

Design, refine, or review web and iOS interfaces using the product’s existing components and visual style. Consult relevant screen examples when useful, then inspect the result for layout problems, inaccessible controls, and broken interactions.

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

• Designing screens that fit an existing product
• Refining a dashboard or simplifying an interface
• Reviewing layouts and interactions before release

Automate terminal interactions and capture screenshots before and after commands run. Define scenarios in TypeScript to review CLI appearance, document command flows, or record changing output such as progress bars, with optional animated GIFs.

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

• Review CLI appearance changes in a pull request
• Capture slash command interactions
• Create screenshots for usage documentation

Build a daily or weekly worklog from recorded activity and checked outcomes. Separate plans, observed work, and verified completion, then summarize useful results and unfinished tasks with source links and clearly marked gaps or estimates.

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

• Preparing a daily work report
• Reviewing weekly outcomes and unfinished tasks
• Summarizing work time using recorded active minutes

Review a specific meeting’s notes and transcript to summarize decisions, commitments, named owners, and stated deadlines. Keep proposals and completed work separate, flag recording gaps, and draft a concise follow-up message when requested.

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

• Organizing decisions and commitments after a meeting
• Checking explicitly stated owners and deadlines
• Distinguishing agenda proposals from agreed work

Prepare a project handoff using recent work records and checks of current materials. Give the recipient a verified status, accessible artifact locations, blockers, and concrete next steps, while distinguishing delivered work from drafts and intentions.

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

• Handing a project over to another person
• Preparing context before resuming paused work
• Collecting artifact locations and supporting links

Turn recorded or starred procedures into reusable guides based on captured evidence. Organize prerequisites, steps, expected results, branches, and final checks, while clearly marking missing details and removing private information from examples.

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

• Turning recorded demonstrations into procedure guides
• Documenting starred work for future reuse
• Preparing instructions for colleagues

Reconstruct an incident timeline from recorded screens and conversations, supported by available logs and monitoring. Organize symptoms, changes, response actions, and recovery evidence while distinguishing observed facts from suspected causes.

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

• Reconstructing events around a system incident
• Reviewing response actions and recovery evidence
• Separating observed facts from suspected causes