Loading...
Loading...
Found 1,339 Skills
Processes videos and image sequences to compile scroll-, pointer-, drag-, and state-driven web motion effects; includes local media-processing scripts and a runtime. New asset generation uses the host tools.
View or change project config — effective merged values, or set locally in project.local.yaml.
Turn a script, outline, shot list, blog post or theme into a video cut from the user's own real footage (not AI-generated): rough cut, assembly edit, string-out, script to video, montage, highlight reel, recap, sizzle reel. Picks the best clip per line with alternatives, saves an editable project and exports MP4. Local with Reelary on Mac or Windows. Trigger on "rough cut", "assembly edit", "first cut", "script to video", "turn this script into a video", "make a video from my blog post", "text to video with my footage", "montage", "highlight reel", "recap video", "best moments", "year in review video", "trip video from my clips", "wedding highlights", "edit my footage into a video". Not for AI video generation, color grading or effects.
Makes a painted or illustrated character turn its head to follow the visitor's cursor, looking like one continuous painting that moves, without a 3D model or face tracking. Generates head-pose keyframes with an image-editing model and head-turn clips with an image-to-video model, then builds a pose grid on one fixed body (selected by measured head position, aligned, masked, with optical-flow in-betweens) and plays it with a spring-driven canvas player that also blinks. Use when someone wants a hero character, mascot or portrait whose eyes or face follow the mouse, a "look at the cursor" effect, or an illustration that reacts to the visitor.
Reverse-engineer how a video was made—classify each shot as live action / AI-generated / 3D rendering / 2D animation / stop-motion animation / code-template rendering / screen-recording screenshot / static-image push-in / push-out / still frame, and determine whether live-action footage was AI-processed (face swap, lip sync, stylization). Identify post-production overlays (sentence-by-sentence subtitle timelines, decorative text, titles, stickers / GIF / memes, picture-in-picture) and the user's genuine assets. Break down the voiceover, background music, sound effects (which visual event each one hits), and editing rhythm, then provide an executable remake plan (with capsule-cinema integration). Use this when the user provides a reference video and asks "How was this video made? / Is it AI? / What assets were used? / How can I remake it?"
Model game shapes, volumes, influence, procedural objects, and effects with signed distance functions, implicit functions, scalar fields, vector fields, and deformation fields. Use when building SDF primitives, field composition, raymarching inputs, organic procedural shapes, offsets, Booleans, deformation, or field-driven gameplay.
Vẽ dần nét SVG (stroke-draw) theo cuộn trang hoặc khi vào viewport — đo `path.getTotalLength()`, set `stroke-dasharray`/`stroke-dashoffset`, animate dashoffset từ length về 0. Gọi khi user nói "vẽ svg khi cuộn", "svg stroke draw", "logo vẽ dần", "path animation reveal", "stroke-dashoffset", hoặc /svg-stroke-reveal. KHÁC `skills/scroll-effects` (7 hiệu ứng cuộn chung — reveal/stagger/highlight/nav/top/toc/parallax, KHÔNG có stroke-draw) — skill này chuyên biệt cho SVG `<path>` có NÉT VẼ (logo, chữ ký, biểu đồ đường, hành trình).
Write idiomatic, robust, maintainable Rust. Use this skill whenever you write, review, refactor, debug, or explain Rust code: new crates, modules, functions, structs, traits, error types, async code, unsafe or FFI code, Cargo.toml, tests, or rustdoc. Trigger on any mention of Rust, cargo, crates, .rs files, the borrow checker, lifetimes, traits, clippy, or rustfmt, even when the user does not ask for "best practices" or "idiomatic" code. Synthesized from the Google Rust Style Guide, the Rust API Guidelines, Effective Rust, Rust Design Patterns, and Microsoft's Pragmatic Rust Guidelines.
Add a licensed soundtrack to any video for $0 with beat-matched music, Openverse sound effects, -16 LUFS mastering, and FFmpeg verification. Searches 5.2M free CC0/CC-BY/public-domain audio files (no API key), aligns cuts to the kick-drum beat grid with librosa, peak-normalizes SFX one-shots, verifies the exported MP4 with ebur128 and cue frame grabs, and auto-writes credits.txt. Trigger when the user says "add sound to this video", "add music to my video", "add sound effects", "find free SFX", "sound design this clip", "my video needs audio", or "add audio to my ad".
Use when writing or refactoring code, before creating files - enforces separation of pure business logic (Functional Core) from side effects (Imperative Shell) using FCIS pattern with mandatory file classification
Detect React and TypeScript maintainability smells across the whole component, hook, and module, explain the cost of each, and propose a fix with a source link. Covers prop and API design (naming, booleans, callbacks, variants, controlled state, generics, refs, styling, JSDoc), state and data flow (redundant state, stale closures, context and ref misuse), effects and lifecycle, component structure and hooks, rendering correctness (keys, mutation, impure renders, hydration, the leaked 0 from &&), accessibility and focus management, async handlers, error boundaries, unsafe HTML, TypeScript discipline (any, casts, untyped catch, exhaustiveness), and a cross-file duplication pass. Defers memoization and re-render performance to react-compiler and color literals to theme-colors. Use when reviewing or writing React components or hooks, auditing for maintainability, or asked to sniff, smell-check, lint, or clean up a codebase, folder, file, or pasted snippet. Respects native HTML attributes and library conventions.
Use when packaging Spree 6 React dashboard customizations as a redistributable npm plugin (optionally paired with a Rails extension gem) that other Spree stores install — scaffolding with `npx @spree/cli plugin new`, file routes and route collisions, peerDependencies against `@spree/dashboard-core`/`-ui`, prebuilt vs source publishing, `sideEffects`, the `spree.dashboard.plugin` package.json marker, auto-discovery via `virtual:spree-dashboard-plugins` vs an explicit whitelist, Tailwind class scanning, `definePlugin(config)` factories, Changesets, and the backend gem half. Common phrasings include "publish a dashboard plugin", "npm package for the Spree admin", "spree plugin new", "share admin screens across stores", "plugin not showing up", "Dashboard route collision", "plugin styles missing", "marketplace extension with admin UI".