screenshot-intake

Convert website screenshots or live URLs into structured build specifications.

7|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/PMDevSolutions/Aurelius --skill screenshot-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: screenshot-intake
Source: https://github.com/PMDevSolutions/Aurelius/tree/main/.claude/skills/screenshot-intake
Command: npx skills add https://github.com/PMDevSolutions/Aurelius --skill screenshot-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the tedious manual work of documenting UI structure, components, and content from website screenshots or live URLs, removing guesswork from converting visual references into actionable development plans.

Core Features & Use Cases

  • Automated Page Capture: Supports live URL capture via Chrome DevTools or Playwright MCP, or validation of user-provided screenshot files, with multi-viewport and multi-page handling.
  • AI-Powered UI Analysis: Uses vision models to extract layout patterns, reusable components, text content, and visual hierarchy from captured screenshots.
  • Standardized Build Spec Generation: Produces a consistent build-spec.json file that downstream development pipelines use to scaffold, test, and build production-ready applications.
  • Use Case: A product team wants to replicate a competitor's web app workflow. Provide the competitor's URL, and the skill will automatically capture all pages, identify every UI component and text element, and generate a complete build plan for your engineering team to implement.

Quick Start

Use the screenshot-intake skill to generate a complete build specification from the provided website URL or screenshot files.

Frequently Asked Questions about screenshot-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a website screenshot into a build spec for frontend development?

Converting website screenshots into a build spec requires automated page capture and AI-powered UI analysis to extract layout patterns, reusable components, and text content, ultimately generating a standardized build-spec.json file for development pipelines.

Can I capture live URLs and identify multi-page routes automatically?

Yes, capturing live URLs via Chrome DevTools or Playwright MCP supports multi-viewport and multi-page handling, automatically identifying UI components and multi-page routes for comprehensive app scaffolding.

What is the best way to clone an existing web interface without original design files?

The best way to clone a web interface without design files is applying vision models to analyze screenshots, detect UI components, and produce a structured application build specification for test-driven development and code generation pipelines.

Does screenshot-to-code generation work with downstream test-driven development pipelines?

Screenshot-to-code generation produces a consistent build-spec.json file that downstream development pipelines use to scaffold, test, and build production-ready applications compatible with test-driven development workflows.

Do I need Chrome DevTools or Playwright MCP to capture live URLs for UI analysis?

You need Chrome DevTools or Playwright MCP for automated live URL capture, but you can also validate and process user-provided screenshot files directly if you already have static images for UI component detection.