attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user…
Build a local, offline motion-design editor app (After Effects / Screen Studio-lite) with scenes, layers, keyframes, spring easing, presets, stagger, a cursor layer, timeline, undo/redo, save/open, and deterministic MP4 export via Playwright + ffmpeg. The deliverable is the
$ npx -y skills add CoWork-OS/CoWork-OS --skill motion-editor --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/motion-editorContext preview
The summary Claude sees to decide when to auto-load this skill.
Build a local, offline motion-design editor app (After Effects / Screen Studio-lite) with scenes, layers, keyframes, spring easing, presets, stagger, a cursor layer, timeline, undo/redo, save/open, and deterministic MP4 export via Playwright + ffmpeg. The deliverable is the
name: motion-editor description: "Build a local, offline motion-design editor app (After Effects / Screen Studio-lite) with scenes, layers, keyframes, spring easing, presets, stagger, a cursor layer, timeline, undo/redo, save/open, and deterministic MP4 export via Playwright + ffmpeg. The deliverable is the editor itself, not a video." version: "1.0.0" license: MIT metadata: author: CoWork OS Contributors <info@coworkosapp.com>
Confirm the target folder and the user's OS (adapt shortcuts: Ctrl on Windows/Linux, Cmd on macOS). Phases span many steps: keep a `PROGRESS.md` in the project noting what's built and which verifications passed. If an essential ambiguity remains, ask the user — the requirements below take priority over any outside source.
<goal> Build a local motion-design editor app. The deliverable is the EDITOR ITSELF, not a video. Do NOT invent a video concept, create demo content, or render anything automatically. On first launch, open an empty project. Rendering happens only when the user clicks Export. </goal>
<environment>
</environment>
<architecture>
</architecture>
<data_model>
Text props: content, fontFamily, fontSize, fontWeight, lineHeight, letterSpacing, align, color.
</data_model>
<phase_1_core> Build and verify ALL of this before starting Phase 2: 1. Project settings: duration, aspect ratio (16:9, 9:16, 1:1, 4:5, custom), resolution, fps. Changing them never deletes layers. 2. Asset import (button + drag&drop): PNG, JPG, WebP, SVG, fonts (TTF/OTF/WOFF2). Originals copied byte-for-byte, never modified. 3. Add text and shapes. Scenes: create, duplicate, rename, reorder, delete. 4. Layers panel: reorder, show/hide, lock, rename, duplicate, delete. 5. Preview: click to select, drag to move, handles to scale/rotate, Shift to constrain. Selection stays synced across preview, timeline, and properties panel. 6. Timeline: scene blocks with draggable boundaries, layer bars with draggable start/end, keyframe diamonds draggable in time, playhead scrubbing, zoom. 7. Properties panel: transform, opacity, typography, alignment, spacing, color; per-property keyframe toggle at playhead; easing picker with live curve preview. Plain-language labels; tooltip on every non-obvious control explaining what it changes. 8. Playback: play/pause, replay, loop, Space, frame step with ←/→, time + frame counter. Any parameter change updates the preview instantly. 9. Undo/redo (Ctrl/Cmd+Z, Ctrl/Cmd+Shift+Z) for every edit; one drag = one history step. 10. Save/Open: project folder `<name>.motion/` with project.json + assets/. Unsaved-changes dot in title + warning on close. Missing assets show a placeholder with a "Relink" button. Also export/import the whole project as a single .zip. </phase_1_core>
<phase_2_advanced>
</phase_2_advanced>
<export>
</export>
<out_of_scope_v1> Audio, video clips as layers, scene transitions, blur/effects, AI generation, cloud sync. Mark them as "Not available" in UI if referenced anywhere; no dead buttons. </out_of_scope_v1>
<verification> Actually run these, do not just claim them:
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Use when Codex is already in the attack-path-analysis phase of a security scan or the user…
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing…
Use when Codex is already in the finding-discovery phase of a security scan or the user…
Use when the user explicitly asks to fix and verify a validated or plausible security…
Use when the user asks for a security review of a pull request, commit, branch diff,…
Use when the user asks for a repository-wide or scoped-path security scan.