Skip to content

nexu-io/openmotion / library/skills/openmotion-flat-card-explainer

openmotion-flat-card-explainer

Unverified

OpenMotion — Make a SaaS explainer from flat UI cards: scattered windows show the problem, a cursor tidies them, a simple board shows the product working. Use for workflow, task and collaboration tools.

OpenMotion · Flat Card Explainer

Build the video as a native OpenMotion HTML/CSS/JS composition through the installed OpenMotion production Skill: create or open the project, author the composition, save with revision protection and preview. This library Skill adds creative direction only; it registers no MCP Tool or production route. Treat palette, font and timing values below as starting points; a supplied Brandkit or the user's brand wins. For missing images, voice or music, first discover providers and model IDs with openmotion_media_use, then generate with openmotion_assets_use; get the user's consent before any paid generation. Never invent quotes, numbers, specs or dates.

Status: recipe / draft. No executable template or rendered comparison yet.

Use for: showing how a SaaS product works in 3–4 steps without screen recordings.

Look

ElementStarting value
BackgroundVery light grey #F2F2F6 with a white centre glow
CardsFlat white windows with an indigo #5458E8 title bar, yellow #F7C744 text bars and pink #F0507A blocks; radius 8 px, soft drop shadow
TypeGeometric sans in italics for captions (500, 54–60 px) with the key words in extra bold indigo or pink
UISimplified boards, lists and avatars rebuilt from the user's product; real labels, no lorem ipsum
CursorDark arrow cursor with a white outline that performs every action

Motion

  • Problem: 6–8 cards pop in across the frame (60 ms stagger) and drift slowly.
  • Gather: the cursor arrives and the cards fly into one neat stack (600 ms each, power3 in-out, 50 ms stagger).
  • Show: the stack opens into the product view; the cursor drags one item to its next state in ~700 ms and a check mark pops.
  • Close: the view scales away and the call to action rises with a hand-drawn underline drawn in 500 ms.

Inputs

Required: product name, the 3–4 workflow steps, real board or list labels, call to action. Optional: screenshots to copy the layout from, brand colours.

Avoid

Pixel-perfect UI with tiny unreadable text, more than one cursor action per step, captions longer than six words, invented customer numbers.

Review

Card labels are readable at 1×; the cursor reaches each target before acting; captions never overlap cards.

Provenance

Written for OpenMotion after surveying publicly listed workflow names and descriptions in ChatCut's preset gallery (November 2026). Original text; no ChatCut prompts, source code, templates or media are included. Apache-2.0, like the rest of the repository.

brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 319kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 196kUpdated Claude CodeCodexVerifiedInstall