Daily UI Inspiration Capture

Overview

Run the current project's daily UI inspiration workflow as an article-ready bundle, not a screenshot dump or README. Treat the active project runbook as source of truth, but keep the contract below as the default unless the user updates it.

Start

Work from the content/article project named by the user. If no project is named, use the current workspace and say which directory you used.

Before collecting, read:

• AGENTS.md, if present or supplied in the prompt
• scripts/ui-inspiration-capture-guidelines.md, if present
• the latest one or two articles/*-ui-inspiration-capture/content.md and manifest.json files for current shape

Check git status --short early. This repo is often dirty; keep changes scoped to the requested dated bundle or skill files.

For any browser work, use the Codex in-app browser only. Do not use Chrome. If a source blocks inspection, use the best available Codex-browser evidence or local asset fallback and say why.

Output Contract

Create a dated folder:

articles/YYYY-MM-DD-ui-inspiration-capture/

The folder should contain at minimum:

• content.md
• manifest.json
• local still images
• local video files or clear per-item video fallback reasons
• one full-page scroll screenshot per live website reference
• section-by-section crops from that full-page screenshot for the hero, every meaningful middle section, and the footer
• motion-frame images when video capture succeeds

Do not create README.md.

Collect exactly 5 final references. The newer 5-reference motion-study workflow supersedes older 20-image gallery runs.

Prefer live, inspectable landing pages and product sections. Framer Marketplace is a strong source. Dribbble is best effort; if blocked by WAF or poor assets, finish with stronger Framer or direct-page candidates instead of forcing brittle workarounds.

Selection