mirror of
https://github.com/nexu-io/open-design.git
synced 2026-08-03 06:05:05 +08:00
a0a3ad1299
- Replaced the `community/` directory with `spec/`, which now serves as the portable plugin specification and authoring kit, including documentation, templates, and examples for contributors. - Added new files for agent development, contributing guidelines, and a comprehensive README for the plugin spec kit. - Updated existing documentation to reflect the new structure and clarify authoring rules for plugins. - Introduced multiple example plugins under the new `spec/examples/` directory, showcasing various use cases and workflows for plugin authors. This update enhances the clarity and accessibility of the plugin development process, providing a robust framework for contributors and external agents.
27 lines
923 B
Markdown
27 lines
923 B
Markdown
---
|
|
name: create-hyperframes-launch
|
|
description: Use this plugin when the user wants a HyperFrames-ready HTML motion composition, launch animation, kinetic typography clip, product reveal, or social video made from code.
|
|
license: MIT
|
|
metadata:
|
|
author: open-design-spec
|
|
version: "0.1.0"
|
|
od:
|
|
mode: hyperframes
|
|
scenario: video
|
|
---
|
|
|
|
# Create HyperFrames Launch
|
|
|
|
## Workflow
|
|
|
|
1. Clarify duration, aspect ratio, product, text beats, and motion style.
|
|
2. Plan the composition as scenes with exact timings.
|
|
3. Create HyperFrames-ready HTML with named layers, restrained animation, and render notes.
|
|
4. Keep composition source organized under a cache or source folder and return the rendered artifact or render instructions.
|
|
5. Critique timing, legibility, and whether the composition can render deterministically.
|
|
|
|
## Output Contract
|
|
|
|
Produce `hyperframes-plan.md` and a render-ready composition folder or rendered video.
|
|
|