Results for “screen-capture”

Automate browser tasks, scrape websites, fill forms, capture screenshots, and extract structured data from web pages using Playwright.

Tests local web applications by writing native Python Playwright scripts, with helpers for server lifecycle management, DOM inspection, and screenshot capture.

Automates iOS screenshot capture and upload: builds and launches the app on a simulator with xcodebuild/simctl, drives UI with AXe, frames screenshots with Koubou, and uploads them via the asc CLI.

Takes screenshots of any website by sending its URL to a free cloud API, returning PNG or JPEG images with options for full-page capture, viewport size, dark mode, and more.

Runs a headless-Chromium sweep at phone/tablet widths to catch off-screen overflow, tiny touch targets, clipped text, and oversized modals, then reports each offender with a screenshot and a concrete fix.

Record polished UI demo videos using Playwright with visible cursor, natural pacing, and storytelling flow.

Classify whether a ticket is frontend or UI work. Use when deciding whether design-aware planning, visual verification, UI tests, or screenshot capture applies.

Crawl and extract web content for AI with Crawl4AI — async browser-based crawling with clean Markdown output, CSS/XPath/LLM extraction strategies, chunking, screenshot capture, session reuse for SPAs, and Docker deployment.

Secure and powerful Playwright browser automation for testing websites, checking deploys, taking screenshots, filling forms, validating login flows, responsive QA, deploy QA, accessibility smoke checks, and browser-based verification. Use when Nick asks to test a page, verify a deployment, automate browser interactions, capture screenshots, inspect console errors, check mobile/desktop rendering, or run real Chromium-based browser checks.

Tests and debugs web applications in real browsers using Chrome DevTools MCP, enabling DOM inspection, console error capture, network analysis, performance profiling, and visual verification with live runtime data.

Runs adversarial UI tests in a real browser using the browse CLI, analyzing git diffs to test only changed areas or exploring the full app to find bugs in functionality, accessibility, responsive layout, and UX.

Review a built frontend against its chosen direction, catch drift back to generic AI defaults, enforce state coverage, ethical patterns, UX heuristics, and polish, and check contrast with APCA (not the legacy WCAG ratio). Produces specific, prioritized fixes — never vibes-based feedback. Works with pasted screenshots or Playwright MCP automated capture. Load when the user asks to review a UI, audit a design, check if a frontend looks generic or vibecoded, evaluate visual quality or polish, says "review this UI", "is this design good", "audit my frontend", "does this feel like [product]", "design QA", or when frontend-design routes here. Sub-skill of frontend-design.

Drive Moli (`moli`), Lexmount's open-source headless browser for AI agents, built around on-demand rendering: real JavaScript, DOM, and CSS by default, with layout and pixels computed only when explicitly requested via `--layout`. Use when the user wants to fetch/extract a live JavaScript-rendered page as Markdown/HTML/JSON/semantic-tree, capture a screenshot or PDF, run a small bounded crawl, start a CDP/WebDriver automation server for Playwright/Puppeteer, replace a Chromium/ChromeDriver dependency, or diagnose readiness/network/frame issues on a rendered page. Triggers on: "moli fetch", "moli serve", "headless browser for agents", "on-demand rendering browser", "CDP server without Chrome", "structure-first web scraping", "Lexmount browser", "moli-webfetch", "moli-cdp-server".