「shots」の検索結果

Use when your context carries "The approved design this task builds" - comparing the running UI with the approved hand-off and mockup at each width and state, evidence screenshots attached to the task, Blocker/High/Medium/Nitpick findings and which of them fail the round

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

Convert image files into Word, Excel, PPT, PDF, HTML, RTF, CSV, TXT, or JSON with ComPDF. Use for screenshots, scans, receipts, forms, and photo-based business documents that need editable or structured output.

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

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

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

Browser automation CLI for AI agents. Use when needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. TRIGGER when user requests to "open a website", "fill out a form", "click a button", "take a screenshot", "debug this in browser", "scrape data from a page", "test this web app", "login to a site", "frontend UI/UX aesthetics", "automate browser actions", or any task requiring programmatic web interaction.

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

Start a new prospect's intake, with or without their files in hand — a request naming a new prospect and attaching no documents is a normal starting point, because Step 1 searches the connected tools or asks the advisor to upload. Cleans and normalizes their account files (statements, exports, screenshots) into a consolidated view, then hands back a plain-English prospect summary, a detailed analyst handoff the full proposal gets built from, and a friendly "what to expect" memo, offered as a Gmail draft on approval. Does not produce the proposal, recommend an allocation, or quote fees. Triggers on "prospect intake", "/prospect-intake", "new prospect intake", "clean up [prospect]'s statements", "process [prospect]'s files", "what to expect note for [prospect]" — and on how an advisor raises a new prospect before any file exists: "I met with a potential client/customer", "[name] is interested in becoming a client", "I have a new prospect", "how should I proceed with [name]".

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

Save a site or section as local files (markdown, screenshots). Use for "download the site", offline docs, or a local copy for reference.

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

Compare two images pixel-by-pixel and get a visual diff. Use when the user wants to compare their implementation against a design, spot differences between two screenshots, or verify visual regression.

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

Extract color palettes from images (screenshots, Figma exports, design mockups) to help implement matching UI. Use when the user shares a screenshot, design image, or asks to "match these colors", "extract colors from this image", "implement this design", or "get the color palette".

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

Read this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for "computer use". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before a conversation is linked there may be no such tools, only an enable__mcp__remote-devices__Claude_Browser tool, which links it. It covers getting linked, picking the right tool, the access flow, and what to do when computer use is off or out of reach. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.

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

Designs Android testing with Espresso, UI Automator, Robolectric, and Compose. Use when planning device matrices, emulator CI, Compose test migration, screenshots, or flakes.

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

Automating iOS UI via XCUITest and fastlane snapshot pipelines for App Store screenshots. Not for cross-platform E2E (Voyager), iOS feature impl (Native), or unit tests (Radar).

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

Generating pixel-accurate HTML/CSS code from image mockups (PNG/JPG/screenshots) and performing visual verification for faithful reproduction. Use when mockup-to-code generation is needed.

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

Use when users request Android competitor research, systematic feature or interface mapping, evidence screenshots, interaction coverage, comparison-ready product dossiers, or Android system-boundary verification without APK decompilation.

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

Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack)

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

Create distinctive, production-grade frontend interfaces with high design quality using Mobile First strategy. Analyzes design systems from screenshots, generates Tailwind CSS + Shadcn UI configurations, and retrofits existing projects. Optimized for Claude Opus 4.5 with structured decision trees and self-verification checkpoints.

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

Vitest testing framework patterns and best practices. Use when writing unit tests, integration tests, configuring vitest.config, mocking with vi.mock/vi.fn, using snapshots, or setting up test coverage. Triggers on describe, it, expect, vi.mock, vi.fn, beforeEach, afterEach, vitest.

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

Test PydanticAI agents using TestModel, FunctionModel, VCR cassettes, and inline snapshots. Use when writing unit tests, mocking LLM responses, or recording API interactions.

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

Provision and drive a `pu` box — an Incus container used as a clean Linux host for CI, builds, and evidence capture. Use when you need to run something on a fresh remote box instead of the user's machine: `nix run` a build, run CI against a real host, capture screenshots/video off-machine, or reproduce on a pristine environment. Covers create/connect/scp/destroy, running remote commands, copying artifacts back, and the no-egress failure mode. Triggers on "pu box", "spin up a box", "run this on a box", "ephemeral host", "pu create/connect/destroy".

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

Semi-automated fact-checking, source credibility evaluation, misinformation detection, prebunking, and evidence-ledger based claim verification. Use when a user asks to verify a claim, article, social post, screenshot, URL, quote, data point, compare sources, detect manipulation, evaluate source reliability, or generate an HTML fact-check card/share-safe correction. Supports text, URLs, screenshots/images, two-source comparison, and topic-level prebunking in Bulgarian, English, Russian, EU policy, health, science, and geopolitical contexts. Trigger phrases: "is this true?", "is this fake?", "fact check this", "compare these sources", "проверка на факти", "истина ли е", "дезинформация ли е", "сравни тези източници".

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

确认漏洞后产出正式 SRC/0day 提交稿 DOCX 报告的收口 skill。仅在漏洞已确认、准备成稿时使用——负责查重、过分层验证门、按固定 DOCX 骨架生成报告（Heading 2 章节 + Step 式 PoC + 内嵌真实截图）、语义化命名、放对目录、处理驳回追加。不负责挖掘/验证漏洞本身。TRIGGER：用户说"写报告/出报告/成稿/提交稿/生成漏洞报告"，或漏洞已验证到位准备交付时；或 /report。EN: Turns confirmed vulnerabilities into submission-ready DOCX reports for SRC/0day platforms (verification gates, fixed layout, step-style PoC, mandatory real screenshots). Trigger on "write report" or /report.

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

Marketingbilder rechtebewusst planen, erzeugen, bearbeiten, optimieren und prüfen. Nutze diesen Skill für Bildbriefings, Produktscreenshots und Mock-ups, generative Bilder, Stock- und Lizenzrouten, Bildbearbeitung, Formate und Komprimierung sowie deutsche Alt-Texte. Klärt Herkunft und Nutzungsrechte vor der Produktion, beachtet Persönlichkeits-, Marken- und Urheberrecht, verlangt Kennzeichnung wo nötig und schließt erfundene Produktansichten und unbelegte Bildaussagen aus. Nicht gedacht für Logos, Design-Systeme und Layoutarbeit.

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

Use when installing or operating the independent Univer Workspace CLI application (`univer-workspace-cli`) for remote Workspace files, Personal or Team Spaces, task Worktrees, Sheet/Doc/Slide/Base/Board Units, Facade authoring, inspection, verification, import/export, screenshots, or review handoff. Do not use for local targets handled by `univer`.

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

Use when installing or operating Univer CLI for .univer files, spreadsheets, documents, slides, Base databases, Board canvases, cross-Unit embedding, worktrees, Facade authoring, inspection, verification, import/export, screenshots, or viewer handoff.

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

Verify claims, quotes, timelines, and findings against supplied source files and return a source map with verified, conflicting, not found, and manual-review statuses. Use when the user asks to fact-check a memo, audit, timeline, executive summary, research packet, or project brief against PDFs, XML, HTML, notes, screenshots, exported chat logs, or other supplied files before sending, publishing, or relying on the result.

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