「screen」の検索結果

Verifies UK case-law citations, pinpoint references and quotations against the official public register — The National Archives' Find Case Law — and statutory references against legislation.gov.uk, before a document that cites them is relied on, served or filed. Every check returns a graded verdict: VERIFIED, MISMATCH (the citation resolves to a different case — the classic AI miscitation), NOT ON REGISTER, OUTSIDE COVERAGE (the register cannot answer — absence proves nothing), or UNCHECKABLE (a law-report citation). The grading exists because there are two ways to get this wrong: citing a case that does not exist, and accusing a real case of not existing. Use when asked to check citations, verify a case exists, confirm a quotation is verbatim, check a pinpoint paragraph, audit a draft's authorities, screen a document for hallucinated cases, or check a statutory provision is in force. Not a substitute for reading the judgment: existence is not authority.

日本語の概要は準備中です。原文の説明を表示しています。

Screen incoming NDAs and classify them as GREEN (standard), YELLOW (needs review), or RED (significant issues). Use when a new NDA comes in from sales or business development, when assessing NDA risk level, or when deciding whether an NDA needs full counsel review.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a security incident, data breach, or actively exploited vulnerability raises the question "who must we notify, where, and by when?" Screens one incident across the EU reporting regimes — NIS2, GDPR, DORA, and the Cyber Resilience Act — determines which duties fire for each involved entity's roles, resolves the receiving authority per regime and member state from served national law, and produces a deadline table in which every duty, authority, and deadline is cited from official publisher text fetched live through the Ansvar Gateway MCP connector. Never answers from model memory.

日本語の概要は準備中です。原文の説明を表示しています。

Turns a legal question, a set of draft questions, or source material such as a statute, jury instruction, rubric, contract checklist, or coding manual into a battery of narrow questions that TypeSafe's Jev, a fast classifier that returns probabilities rather than prose, can answer reliably across many documents. The skill breaks conclusions such as negligence, felony murder, or standing into element-level questions, writes the governing rule into each question, and delivers the questions alone, in Jev's request format or in plain English. Built for legal work that asks the same questions of many texts: coding statutes across jurisdictions, coding opinions or case files for empirical research, checking contracts against a review checklist, screening intake narratives, and grading student work against a rubric. Use when asked to write Jev questions, build a classifier for legal documents, or turn a legal test into yes-or-no questions. Running the questions requires Jev access; writing them does not.

日本語の概要は準備中です。原文の説明を表示しています。

Use for due diligence, legal-financial risk review, investment or business transaction checklists, and preliminary screening where facts, documents, assumptions, legal uncertainty, debt/equity, assets/liabilities, contracts, tax, regulatory, compliance, technology/product, and financial-model issues must be separated clearly.

日本語の概要は準備中です。原文の説明を表示しています。

Elite incident response and legal compliance guidance for data breaches under GDPR Articles 33 & 34. Use when: (1) User reports a data breach or security incident — including "is this even a personal data breach?" triage, (2) User asks about breach notification obligations or deadlines, (3) User mentions "72 hours", Art. 33, Art. 34, or notification requirements, (4) Discussion involves security incidents affecting personal data, (5) User needs breach risk assessment using ENISA methodology, (6) User mentions "Data Breach" or "Incident" or "Data Leakage" or "Ransomware" or "Exfiltration", (7) User needs to determine Controller vs Processor obligations, (8) Cross-border breach scenarios requiring Lead SA determination, (9) User needs a mitigation playbook or immediate response recommendations, (10) User needs audit-ready breach documentation (.docx) or an EDPB-template-aligned breach notification / evidence file — including follow-up and withdrawal notifications, (11) Breach involves an AI system requiring AI Act Art. 73 serious incident screening.

日本語の概要は準備中です。原文の説明を表示しています。

U.S. customs and trade-law research assistant for HTS classification, CROSS ruling research, CIT/CAFC decision briefing, duty compilation (General + Special + Chapter 99 + AD/CVD + MPF/HMF), country of origin determination, FTA qualification, and end-to-end import compliance review. Triggers on product classification, tariff questions, customs rulings, trade remedy screening (Section 301/232/201), Partner Government Agency admissibility, and UFLPA forced-labor analysis. Produces attorney-reviewable draft work product with an enforced HTSUS authority hierarchy and explicit evidence ledger.

日本語の概要は準備中です。原文の説明を表示しています。

Complete sanctions and export control analysis tool — individual designations, sectoral sanctions, dual-use goods, payment systems (SWIFT/USD), and extraterritorial regimes (EAR/ITAR/ FDPR US, ECL China). Triggers: "is X sanctioned?", "can I do business with X?", "can I sell Y to Z?", "pétrole Russie", "biens à double usage", "gel des avoirs", "sanctions internationales", "liste OFAC", "liste UE", "double usage", "embargo", "licence d'exportation", "SWIFT", "paiement en dollars", "US goods", "FDPR", "EAR", "ITAR", "BIS", "ECL chine", "no re-export clause", "sanctions sectorielles", "puis-je travailler avec X?", or any transaction involving a foreign person, product, sector, destination country, or payment in USD/EUR. Always adapt to user profile. Always run for any sanctions or export control query — even vague or exploratory ones.

日本語の概要は準備中です。原文の説明を表示しています。

Builds a litigation chronology from the disclosure bundle itself — every entry attributed to its source document, behind a CPR 31.22 implied-undertaking check, because documents disclosed in English proceedings may only be used for those proceedings. Adds a privilege screen and case-theory significance tagging, so the output is court-facing work product, not a loose timeline. Use when the user asks to build a chronology or timeline from a disclosure bundle, a matter file, or witness statements, or says 'build the chron', 'what happened when', or needs a Statement of Facts ready timeline.

日本語の概要は準備中です。原文の説明を表示しています。

When you want to brainstorm and check available .com domains for a new project — brand naming, aftermarket pricing (HugeDomains / Afternic / Sedo / Dan), USPTO trademark screening, and social handle availability. Built on Laura Roeder's "work backwards from availability" method. Combines Vercel CLI, whois, Domainr, Namecheap, and agent-browser, each for what it reliably does. Workflow: budget → brainstorm → availability check → whois cross-check → price → aftermarket sweep (plus liveness probe and drop-watch) → bucket → negotiate → trademark + socials → buy. Triggers on "/domain," "find a domain," "check domain availability," "brainstorm a domain," "what .com is available for X," "domain hunt," "name my project," "is X.com available," "aftermarket price on X.com," "trademark check for X."

日本語の概要は準備中です。原文の説明を表示しています。

Expert blueprint for scene loading, transitions, async (background) loading, instance management, and caching. Covers fade transitions, loading screens, dynamic spawning, and scene persistence. Use when implementing level changes OR dynamic content loading. Keywords scene, loading, transition, async, ResourceLoader, change_scene, preload, PackedScene, fade.

日本語の概要は準備中です。原文の説明を表示しています。

Expert blueprint for performance profiling and optimization (frame drops, memory leaks, draw calls) using Godot Profiler, object pooling, visibility culling, and bottleneck identification. Use when diagnosing lag, optimizing for target FPS, or reducing memory usage. Keywords profiling, Godot Profiler, bottleneck, object pooling, VisibleOnScreenNotifier, draw calls, MultiMesh.

日本語の概要は準備中です。原文の説明を表示しています。

Expert blueprint for mobile platforms (Android/iOS) covering touch controls, virtual joysticks, responsive UI, safe areas (notches), battery optimization, and app store guidelines. Use when targeting mobile releases or implementing touch input. Keywords mobile, Android, iOS, touch, InputEventScreenTouch, virtual joystick, safe area, battery, app store, orientation.

日本語の概要は準備中です。原文の説明を表示しています。

Expert patterns for 2D/3D camera control including smooth following (lerp, position_smoothing), camera shake (trauma system), screen shake with frequency parameters, deadzone/drag for platformers, look-ahead prediction, and camera transitions. Use for player cameras, cinematic sequences, or multi-camera systems. Trigger keywords: Camera2D, Camera3D, SpringArm3D, position_smoothing, camera_shake, trauma_system, look_ahead, drag_margin, camera_limits, camera_transition.

日本語の概要は準備中です。原文の説明を表示しています。

Expert patterns for scaling mobile games to desktop including mouse/keyboard controls, increased resolution and graphical fidelity, expanded UI layouts, settings menus, window management, and platform-specific features. Use when creating desktop ports or cross-platform releases. Trigger keywords: mouse_controls, keyboard_shortcuts, resolution_scaling, graphics_settings, fullscreen_toggle, window_modes, Steam_integration, desktop_optimization.

日本語の概要は準備中です。原文の説明を表示しています。

Expert blueprint for mobile platforms (Android/iOS) covering touch controls, virtual joysticks, responsive UI, safe areas (notches), battery optimization, and app store guidelines. Use when targeting mobile releases or implementing touch input. Keywords mobile, Android, iOS, touch, InputEventScreenTouch, virtual joystick, safe area, battery, app store, orientation.

日本語の概要は準備中です。原文の説明を表示しています。

Expert blueprint for scene loading, transitions, async (background) loading, instance management, and caching. Covers fade transitions, loading screens, dynamic spawning, and scene persistence. Use when implementing level changes OR dynamic content loading. Keywords scene, loading, transition, async, ResourceLoader, change_scene, preload, PackedScene, fade.

日本語の概要は準備中です。原文の説明を表示しています。

Expert blueprint for performance profiling and optimization (frame drops, memory leaks, draw calls) using Godot Profiler, object pooling, visibility culling, and bottleneck identification. Use when diagnosing lag, optimizing for target FPS, or reducing memory usage. Keywords profiling, Godot Profiler, bottleneck, object pooling, VisibleOnScreenNotifier, draw calls, MultiMesh.

日本語の概要は準備中です。原文の説明を表示しています。

Expert patterns for 2D/3D camera control including smooth following (lerp, position_smoothing), camera shake (trauma system), screen shake with frequency parameters, deadzone/drag for platformers, look-ahead prediction, and camera transitions. Use for player cameras, cinematic sequences, or multi-camera systems. Trigger keywords: Camera2D, Camera3D, SpringArm3D, position_smoothing, camera_shake, trauma_system, look_ahead, drag_margin, camera_limits, camera_transition.

日本語の概要は準備中です。原文の説明を表示しています。

Expert patterns for scaling mobile games to desktop including mouse/keyboard controls, increased resolution and graphical fidelity, expanded UI layouts, settings menus, window management, and platform-specific features. Use when creating desktop ports or cross-platform releases. Trigger keywords: mouse_controls, keyboard_shortcuts, resolution_scaling, graphics_settings, fullscreen_toggle, window_modes, Steam_integration, desktop_optimization.

日本語の概要は準備中です。原文の説明を表示しています。

Classify a console screen (list/record/form), build it on @temps-sdk/ds templates and the shared shadcn primitives in @temps-sdk/ui, and follow the console's status vocabulary and status colour rules. Use for any new or changed console UI in web/src, and when building or extending web/packages/ds itself.

日本語の概要は準備中です。原文の説明を表示しています。

Meta-skill that generates new design language skills. Works on Claude Code and Codex. Use when the user says 'create a design skill', 'generate design language', 'new design system skill', 'design skill inspired by X', 'design skill from this screenshot', '/hue', or 'use hue'. Also triggers for 'remix my design skill' or 'make my skill more X'.

日本語の概要は準備中です。原文の説明を表示しています。

Use when implementing cameras — smooth follow, screen shake, camera zones, and transitions for 2D and 3D

日本語の概要は準備中です。原文の説明を表示しています。

Visual specialist for full audits. Captures screenshots, evaluates above-the-fold signals, and checks mobile rendering basics.

日本語の概要は準備中です。原文の説明を表示しています。