ııı motion.mdVideo style specification
Manus / V049

Scheduled Tasks 2.0 (Manus) — Scheduled Tasks 2.0 — a…

Place a scheduling request on a calendar, then show how it runs repeatedly. The calendar handles timing; task lists and logs handle execution.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 41.87 seconds
Motion and composition example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Scheduled Tasks 2.0 (Manus) — Scheduled Tasks 2.0 — a… · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f8f6}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>
Visual elementsCalendar gridTask cardChat inputSchedule toggleExecution record
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Establish temporal coordinates with the calendar

Begin with a monthly or weekly view showing task density; distinguish selection from the current date. Give dates, short task names, and times separate hierarchy rather than filling each cell with sentences.

Use light backgrounds and subtle grids, with accents for task blocks and current selection. Keep a consistent sans-serif interface and consider tabular numerals for dates.

02

Create a recurring task from chat

After the request, open frequency, time, and task settings. Confirm before placing the event on the calendar; do not insert unrelated pages between creation and the new task appearing.

Put recurrence frequency in the schedule and this run's completion in its history; they cannot share one status label.

InformationLocation
Recurrence and scheduled timeTask configuration and calendar
This run's start timeRun log
This run's resultCompletion status and output
Task collectionList or card view
03

Keep the same task when switching views

Carry the same task name or selection color through calendar, list, and card views. Return from logs to the task collection to show that results belong to the same schedules.

Adapt to weekly reports, inventory, or project reminders, keeping task content, recurrence, and execution results consistent.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 3.00 seconds
3.00s
Composition reference at 14.00 seconds
14.00s
Composition reference at 18.00 seconds
18.00s
Composition reference at 29.00 seconds
29.00s
Composition reference at 38.00 seconds
38.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to design reviews or content scheduling, preserving calendar→settings→records
  • Times and names may change, but recurrence and results must correspond

Production constraints

Calendar grid / Task card / Chat input / Schedule toggle / Execution record

  • Start with the calendar's overall distribution, then push in on one task to explain its settings
  • turn chat content into a task card while preserving its name and execution schedule
  • show execution history after creation to demonstrate that this is more than a one-off conversation