跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
视频与音频

html-to-interaction-prompts

Convert a supplied HTML page or generated HTML reference into a screenshot-backed article containing multiple reusable interaction prompts. Use when the user provides an HTML file, exported page, generated-page.html, or local/live reference and asks to extract animation/interactions, create prompts, capture screenshots for each prompt, add them to an article, or commit the resulting article/assets.

MengTo · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add MengTo/Skills --skill html-to-interaction-prompts

技能说明


name: html-to-interaction-prompts description: Convert a supplied HTML page or generated HTML reference into a screenshot-backed article containing multiple reusable interaction prompts. Use when the user provides an HTML file, exported page, generated-page.html, or local/live reference and asks to extract animation/interactions, create prompts, capture screenshots for each prompt, add them to an article, or commit the resulting article/assets.

HTML To Interaction Prompts

Goal

Turn an HTML reference into an article-ready prompt pack: identify the important interactions, capture the right visual evidence, write flexible prompts, insert screenshots under each prompt title, verify the article renders, and commit only the intended files.

Daily UI Inspiration Capture Contract

When this skill is used for a daily UI inspiration workflow:

  • Each daily inspiration article must contain exactly 5 inspirations, not 20.
  • Do not ship a screenshot gallery or append 20 shallow prompts.
  • Each of the 5 inspirations must include a representative local still image, an embedded local MP4 video, multiple local screenshots or motion frames, motion/interaction notes, source metadata, and one super detailed AI-builder prompt.
  • If the source is a Framer template or any other live website, record the actual landing page or preview URL while scrolling through the website itself. A marketplace cover image, thumbnail, screenshot pan, or static asset slideshow is not acceptable live-video evidence.
  • For Framer, inspect the marketplace detail page for Full Live Preview or the embedded previewUrl, save that URL as pageUrl, and record the MP4 from that page.
  • For live websites, save one full landing-page scroll screenshot as a single tall image. Then cut section-by-section screenshots from that exact full image so the article includes both the whole page and each section separately.
  • Section crops must be contiguous and pixel-complete relative to the full-page image. Do not miss pixels between sections, do not use arbitrary viewport screenshots as section substitutes, and only allow overlap when sticky elements make it unavoidable.
  • Include as many section crops as the page has meaningful sections. At minimum include the hero, each major middle section in page order, and the footer. Use purpose-based labels when possible, such as proof, features, process, gallery, pricing, faq, or final-cta; otherwise use ordered labels like section-02.
  • In content.md, match the established daily capture article structure from recent examples. Use ### Full-Page And Section Evidence, render the full-page screenshot as a normal Markdown image, then use #### Section Crops and render each crop as a normal Markdown image in top-to-bottom order. Do not rename this block to Local Evidence, do not use text links, filename lists, Markdown tables, raw HTML grids, or crop-coordinate captions for this block.
  • Do not put crop-coordinate captions under screenshots in content.md; keep crop coordinate details in manifest.json.
  • Extract multiple motion frames from the live website video. The frames should show real page states across scroll, not repeated crops of the same cover image.
  • If live capture is blocked, prefer replacing the candidate with another live website. Only create a local fallback video from still evidence when replacement is impossible or the source is image-only, and state the fallback reason in content.md and manifest.json.
  • The prompt for each inspiration should be long enough to paste into an AI builder directly. It should include reference boundaries, anti-patterns, core idea, design system, layout rules, motion system, section-by-section anatomy, conversion/footer, responsive behavior, accessibility, performance, and reduced-motion guidance.
  • Each prompt must describe the landing page section by section. Cover the global shell, header/navigation, hero, proof strip, feature/service modules, product/demo/media section, process/how-it-works, gallery/case-study/work section when present, testimonials/social proof, pricing/package/comparison when present, FAQ, final CTA, footer, and mobile behavior.
  • For every major section, specify the purpose, layout anatomy, visual details, animation, interaction states, scroll behavior, recommended implementation library/API, and reduced-motion fallback.
  • For Framer/live websites, each prompt must include a Live-site evidence note explaining that the still, MP4, and frames were captured from the actual pageUrl, not from a cover image.
  • The manifest must have itemCount: 5 and exactly 5 items.
  • Keep all media inside articles/YYYY-MM-DD-ui-inspiration-capture/.

Workflow

  1. Inspect the real source first.

    • Read the HTML, CSS, and scripts. Search for interaction terms such as mousemove, pointermove, canvas, webgl, ScrollTrigger, requestAnimationFrame, hover, sticky, pin, parallax, magnetic, glow, shader, and animation.
    • Treat source behavior as truth. Do not infer exact effects from a screenshot alone when the HTML is available.
    • Check the current git status before editing. Dirty worktrees are normal; keep staging narrow.
  2. Decide the prompt list.

    • Split prompts by reusable interaction idea, not by implementation line count.
    • If one user bullet contains two distinct effects, split it only when that makes the article more useful.
    • Name each section by the interaction concept: for example, Hero Particle Field That Follows The Mouse, Cursor Glow Hover On Cards, or Scroll Behavior And Section Reveal System.
  3. Write reusable prompts.

    • Keep prompts flexible enough for any brand, color system, card size, layout, or content model.
    • Focus on core idea, technology, implementation shape, interaction behavior, scroll choreography, performance, and accessibility.
    • Avoid hard-coded values unless the user explicitly asks for exact recreation. Do not lock
阅读完整来源 ↗