Results for “screen”

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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).

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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).

The English summary is being prepared. Showing the original description.

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).

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Map a mobile app journey across three or four phone frames in one HTML board. Simple gray content blocks, dashed arrows, numbered actions, and short annotations show how users move between screens before detailed visual design.

• Mapping onboarding through the home screen
• Reviewing the path from item details to confirmation
• Discussing screen transitions before visual design

Create or update Figma screens from code or written descriptions. Use design system components and design tokens, shared values for visual styling, to translate application pages into Figma designs.

• Turning application code into Figma screens
• Creating screens from written descriptions
• Updating screens with design system components

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

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

Find repeated tasks in recorded activity or starred examples, then describe their steps, exceptions, and human decisions. Assess a small automation candidate using captured evidence, available tools, permissions, and clear completion criteria.

• Finding recurring tasks in activity records
• Reviewing starred examples for workflow patterns
• Assessing a small automation candidate

Review recorded activity over a chosen period to understand sustained work and app switching. Get one evidence-based pattern and one small experiment for the next day, with uncertainty stated and no invented productivity scores.

• Reviewing sustained work over a chosen period
• Understanding app and window switching patterns
• Choosing a small experiment for tomorrow

Analyze a single discovery interview to understand actual behavior, needs, workarounds, and open questions. Receive a concise account tied to sources, separating participant actions from hypothetical intentions, interviewer suggestions, and interpretation.

• Summarize actual behavior from an interview
• Identify needs and current workarounds
• Prepare follow-up research questions

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