agentcut 0.2.26 → 0.2.27
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +177 -177
- package/dist/studio/agents/claude.js +3 -2
- package/dist/studio/agents/claude.js.map +1 -1
- package/dist/studio/chat.js +1 -1
- package/dist/studio/chat.js.map +1 -1
- package/dist/studio/cli.js +24 -24
- package/dist/studio/download.d.ts +24 -0
- package/dist/studio/download.js +234 -0
- package/dist/studio/download.js.map +1 -0
- package/dist/studio/host.js +8 -0
- package/dist/studio/host.js.map +1 -1
- package/dist/studio/housekeeping.d.ts +2 -2
- package/dist/studio/housekeeping.js +18 -17
- package/dist/studio/housekeeping.js.map +1 -1
- package/dist/studio/release-cursor.js +21 -21
- package/dist/studio/release-video.js +10 -10
- package/dist/studio/tools.js +7 -0
- package/dist/studio/tools.js.map +1 -1
- package/package.json +56 -56
- package/template/AGENTS.md +14 -14
- package/template/components/README.md +70 -70
- package/template/components/before-after/BeforeAfter.tsx +89 -89
- package/template/components/catalog.ts +107 -107
- package/template/components/cinematic/Device3D.tsx +324 -324
- package/template/components/cinematic/devices3d/display-model.ts +184 -184
- package/template/components/cinematic/devices3d/iphone-model.ts +643 -643
- package/template/components/cinematic/devices3d/macbook-model.ts +608 -608
- package/template/components/cinematic/devices3d/models.ts +657 -657
- package/template/components/cinematic/devices3d/runtime.ts +267 -267
- package/template/components/cinematic/math.ts +100 -100
- package/template/components/color/grade-effect.ts +650 -650
- package/template/components/color/grade.ts +512 -512
- package/template/components/color/looks.ts +154 -154
- package/template/components/countdown/Countdown.tsx +166 -166
- package/template/components/dot-trace-title/DotTraceTitle.tsx +181 -181
- package/template/components/dot-trace-title/meta.json +51 -51
- package/template/components/generate/GenerateReveal.tsx +381 -381
- package/template/components/hook-card/HookCard.tsx +554 -554
- package/template/components/index.ts +199 -199
- package/template/components/lib.ts +191 -191
- package/template/components/line-diagram/LineDiagram.tsx +205 -205
- package/template/components/line-diagram/meta.json +215 -215
- package/template/components/list-card/ListCard.tsx +104 -104
- package/template/components/live-clip.ts +75 -75
- package/template/components/looks.tsx +1447 -1447
- package/template/components/loops/LoopCanvas.tsx +132 -132
- package/template/components/loops/engine.ts +184 -184
- package/template/components/loops/library.ts +667 -667
- package/template/components/loops/library2.ts +777 -777
- package/template/components/motion-loop/MotionLoop.tsx +37 -37
- package/template/components/motion-loop/meta.json +311 -311
- package/template/components/props.ts +73 -73
- package/template/components/quote-card/QuoteCard.tsx +71 -71
- package/template/components/style-layer.tsx +233 -233
- package/template/components/styles.ts +113 -113
- package/template/components/types.ts +66 -66
- package/template/components/word-pop/WordPop.tsx +59 -59
- package/template/components/word-stack/WordStack.tsx +122 -122
- package/template/presets/charcoal-sketch/PROMPT.md +48 -48
- package/template/presets/charcoal-sketch/scripts/duck_music.py +34 -34
- package/template/presets/punk-cut-paper/scenes/Motif.tsx +376 -376
- package/template/presets/punk-cut-paper/scenes/Photo.tsx +73 -73
- package/template/presets/punk-cut-paper/scenes/Ransom.tsx +119 -119
- package/template/runtime/composition.tsx +1189 -1189
- package/template/runtime/helpers.tsx +230 -230
- package/template/runtime/index.tsx +22 -22
- package/template/runtime/types.ts +315 -315
- package/template/skill/SKILL.md +186 -187
- package/template/skill/references/broll.md +44 -44
- package/template/skill/references/browser-export.md +61 -61
- package/template/skill/references/cinematic.md +206 -206
- package/template/skill/references/color.md +79 -79
- package/template/skill/references/craft.md +97 -97
- package/template/skill/references/editing-styles.md +57 -57
- package/template/skill/references/feature-launch.md +34 -34
- package/template/skill/references/footage.md +72 -72
- package/template/skill/references/format.md +142 -142
- package/template/skill/references/how-to.md +146 -146
- package/template/skill/references/launch-direction.md +89 -89
- package/template/skill/references/loops.md +151 -151
- package/template/skill/references/mcp-external.md +19 -19
- package/template/skill/references/performance.md +93 -93
- package/template/skill/references/person-cutout.md +19 -19
- package/template/skill/references/presets.md +60 -60
- package/template/skill/references/product-launch.md +134 -134
- package/template/skill/references/release-capture.md +53 -53
- package/template/skill/references/sound.md +167 -166
- package/template/skill/references/style-spy.md +160 -160
- package/template/skill/references/website-howto.md +45 -45
- package/template/starter/.studio/chat.json +1 -1
- package/template/starter/layers.json +46 -46
- package/template/starter/notes.md +4 -4
- package/template/starter/project.json +13 -13
- package/template/starter/scenes/Title.tsx +38 -38
|
@@ -1,89 +1,89 @@
|
|
|
1
|
-
# Launch direction: from brief to checked shots
|
|
2
|
-
|
|
3
|
-
Use this with `product-launch.md` or `feature-launch.md` for a new film or a major revision.
|
|
4
|
-
For a small edit, keep the existing direction and check the changed shots. The user's script,
|
|
5
|
-
reference, selected style and format take priority. Keep decisions in the project's `notes.md`.
|
|
6
|
-
This guide uses Agentcut tools and frame timing; it does not require another video engine.
|
|
7
|
-
|
|
8
|
-
## Choose a story that the images can tell
|
|
9
|
-
|
|
10
|
-
Compare two possible stories using the available evidence, not just two opening titles. For example,
|
|
11
|
-
show a finished result and then how it was made, or follow one real input through an action to its
|
|
12
|
-
result. Pick the clearest story and record why. Continue without an approval stop unless the user
|
|
13
|
-
asked to choose a direction. Do not repeat this exercise for an approved script or storyboard.
|
|
14
|
-
|
|
15
|
-
Keep the same recognizable file, query, project or other subject through the demonstration when
|
|
16
|
-
the source supports it. A viewer should see what changed. Unrelated screens with benefit labels
|
|
17
|
-
do not explain a workflow. Do not fabricate a failure in the old workflow to create tension.
|
|
18
|
-
|
|
19
|
-
## Turn the direction into build decisions
|
|
20
|
-
|
|
21
|
-
Before building scenes, add a compact direction and shot table to `notes.md`:
|
|
22
|
-
|
|
23
|
-
- **Look:** actual background and text colors, accent use, font files/families, weights, text sizes,
|
|
24
|
-
margins and product framing for each output format. Use selected style tokens where available.
|
|
25
|
-
Replace vague words such as "premium" with these choices. Keep meaningful product status colors.
|
|
26
|
-
- **Motion:** entrance, camera and exit durations in frames, easing or spring settings, and the
|
|
27
|
-
settled reading window. Choose motion by purpose; do not give every element the same entrance.
|
|
28
|
-
- **Avoid for this film:** identify likely distractions, such as repeated feature cards, tiny UI
|
|
29
|
-
inside a large empty stage, or decoration that competes with proof. This is specific to the brief;
|
|
30
|
-
do not ban a color, material or effect that the user's style needs.
|
|
31
|
-
|
|
32
|
-
| Frames [start, end) | What the viewer learns | Source and visible change | Framing and main move | Exact words and settled read frames | Sound cue | Link to next shot |
|
|
33
|
-
| --- | --- | --- | --- | --- | --- | --- |
|
|
34
|
-
|
|
35
|
-
Fill one row per shot. Use real asset paths and source ranges, not placeholder evidence. Keep the
|
|
36
|
-
table aligned with the timeline after timing changes. Plan the final readable frame before `end`.
|
|
37
|
-
Do not add claims, voice or captions just to fill the table.
|
|
38
|
-
|
|
39
|
-
For each demonstration, establish where the task happens, bring the relevant action into clear
|
|
40
|
-
view, then show its result in context. These can be parts of one shot. A pan across a still image
|
|
41
|
-
can explain a layout; it cannot prove an interaction. Keep real footage for the action.
|
|
42
|
-
|
|
43
|
-
## Prove the visual direction early
|
|
44
|
-
|
|
45
|
-
Build the opening and the main proof shot first, in story order when possible. Capture their
|
|
46
|
-
settled frames in each output format with `agentcut_capture_frames`. Inspect actual words, assets,
|
|
47
|
-
framing and contrast before extending that treatment to the rest of the film. A full storyboard
|
|
48
|
-
approval step is optional, only when requested; these are working checks in the live project.
|
|
49
|
-
|
|
50
|
-
The first frame should give the viewer useful visual context unless the brief calls for darkness.
|
|
51
|
-
Give the product enough space for the relevant action to read. At small display size, crop closer
|
|
52
|
-
or reduce the words before reducing text size. A full app view establishes context; its incidental
|
|
53
|
-
labels do not all need to be readable. Essential labels and results do.
|
|
54
|
-
|
|
55
|
-
## Make motion carry the story
|
|
56
|
-
|
|
57
|
-
- Give each shot one main movement. Delay or reduce secondary motion so it does not compete.
|
|
58
|
-
Let essential titles and UI settle while the viewer reads. Idle floating is not a demonstration.
|
|
59
|
-
- Contrast short transitions with longer action and result holds. As a starting estimate, allow
|
|
60
|
-
about `0.5 + 0.3 * wordCount` seconds for a short line after it settles. Validate with the actual
|
|
61
|
-
layout and audience; dense UI needs more time. Cut words or decoration to meet a fixed duration.
|
|
62
|
-
- Connect shots through a visible action, a continuing subject, matching framing or a deliberate
|
|
63
|
-
cut. Name the connection in the shot table. Do not require a transition quota or a new effect at
|
|
64
|
-
every cut. A clear hard cut is useful when a morph would distort the evidence.
|
|
65
|
-
- Keep important labels sharp during the reading window. Motion blur belongs to movement, not
|
|
66
|
-
the proof hold. Use the existing component catalog and `cinematic.md` tools where suitable.
|
|
67
|
-
Follow `browser-export.md`; a browser-only effect is not proof that an export works.
|
|
68
|
-
- Use source action times, narration timings or analyzed music cues. For a regular beat grid,
|
|
69
|
-
calculate each frame from its beat index and round once; repeated rounded intervals cause drift.
|
|
70
|
-
|
|
71
|
-
## Review the cuts and the meaning
|
|
72
|
-
|
|
73
|
-
Keep the main skill's full picture, sound and performance review. Add these checks to it:
|
|
74
|
-
|
|
75
|
-
1. Inspect frame 0, the settled proof and the final readable frame in each format. Read the shot
|
|
76
|
-
sequence as a new viewer. Without the headline, is the promised change still visible?
|
|
77
|
-
2. For each cut at frame `c`, sample `c - 1` and `c`, plus nearby frames across the transition.
|
|
78
|
-
Clamp samples to the video bounds. For a longer move, sample intermediate frames too. Look for
|
|
79
|
-
blank gaps, duplicated subjects, jumps in labels, obscured results and conflicting motion.
|
|
80
|
-
3. Inspect essential words and UI at a small display size, about 360 px wide where available.
|
|
81
|
-
If a tool cannot show that size, record this limit; do not claim a small-screen check passed.
|
|
82
|
-
4. Record concrete issues as `frame / variant / issue / change / recheck result` in `notes.md`.
|
|
83
|
-
Fix wrong claims, unreadable evidence and broken transitions before decorative details. Recheck
|
|
84
|
-
changed shots using `efficient-review.md`; timing or shared changes require broader checks.
|
|
85
|
-
|
|
86
|
-
At hand-off, state what was checked and any remaining weak shot or missing evidence. A build pass
|
|
87
|
-
only proves the project compiles. Do not describe a film as visually verified without viewing its
|
|
88
|
-
captures, or say sound was heard when it was only measured.
|
|
89
|
-
|
|
1
|
+
# Launch direction: from brief to checked shots
|
|
2
|
+
|
|
3
|
+
Use this with `product-launch.md` or `feature-launch.md` for a new film or a major revision.
|
|
4
|
+
For a small edit, keep the existing direction and check the changed shots. The user's script,
|
|
5
|
+
reference, selected style and format take priority. Keep decisions in the project's `notes.md`.
|
|
6
|
+
This guide uses Agentcut tools and frame timing; it does not require another video engine.
|
|
7
|
+
|
|
8
|
+
## Choose a story that the images can tell
|
|
9
|
+
|
|
10
|
+
Compare two possible stories using the available evidence, not just two opening titles. For example,
|
|
11
|
+
show a finished result and then how it was made, or follow one real input through an action to its
|
|
12
|
+
result. Pick the clearest story and record why. Continue without an approval stop unless the user
|
|
13
|
+
asked to choose a direction. Do not repeat this exercise for an approved script or storyboard.
|
|
14
|
+
|
|
15
|
+
Keep the same recognizable file, query, project or other subject through the demonstration when
|
|
16
|
+
the source supports it. A viewer should see what changed. Unrelated screens with benefit labels
|
|
17
|
+
do not explain a workflow. Do not fabricate a failure in the old workflow to create tension.
|
|
18
|
+
|
|
19
|
+
## Turn the direction into build decisions
|
|
20
|
+
|
|
21
|
+
Before building scenes, add a compact direction and shot table to `notes.md`:
|
|
22
|
+
|
|
23
|
+
- **Look:** actual background and text colors, accent use, font files/families, weights, text sizes,
|
|
24
|
+
margins and product framing for each output format. Use selected style tokens where available.
|
|
25
|
+
Replace vague words such as "premium" with these choices. Keep meaningful product status colors.
|
|
26
|
+
- **Motion:** entrance, camera and exit durations in frames, easing or spring settings, and the
|
|
27
|
+
settled reading window. Choose motion by purpose; do not give every element the same entrance.
|
|
28
|
+
- **Avoid for this film:** identify likely distractions, such as repeated feature cards, tiny UI
|
|
29
|
+
inside a large empty stage, or decoration that competes with proof. This is specific to the brief;
|
|
30
|
+
do not ban a color, material or effect that the user's style needs.
|
|
31
|
+
|
|
32
|
+
| Frames [start, end) | What the viewer learns | Source and visible change | Framing and main move | Exact words and settled read frames | Sound cue | Link to next shot |
|
|
33
|
+
| --- | --- | --- | --- | --- | --- | --- |
|
|
34
|
+
|
|
35
|
+
Fill one row per shot. Use real asset paths and source ranges, not placeholder evidence. Keep the
|
|
36
|
+
table aligned with the timeline after timing changes. Plan the final readable frame before `end`.
|
|
37
|
+
Do not add claims, voice or captions just to fill the table.
|
|
38
|
+
|
|
39
|
+
For each demonstration, establish where the task happens, bring the relevant action into clear
|
|
40
|
+
view, then show its result in context. These can be parts of one shot. A pan across a still image
|
|
41
|
+
can explain a layout; it cannot prove an interaction. Keep real footage for the action.
|
|
42
|
+
|
|
43
|
+
## Prove the visual direction early
|
|
44
|
+
|
|
45
|
+
Build the opening and the main proof shot first, in story order when possible. Capture their
|
|
46
|
+
settled frames in each output format with `agentcut_capture_frames`. Inspect actual words, assets,
|
|
47
|
+
framing and contrast before extending that treatment to the rest of the film. A full storyboard
|
|
48
|
+
approval step is optional, only when requested; these are working checks in the live project.
|
|
49
|
+
|
|
50
|
+
The first frame should give the viewer useful visual context unless the brief calls for darkness.
|
|
51
|
+
Give the product enough space for the relevant action to read. At small display size, crop closer
|
|
52
|
+
or reduce the words before reducing text size. A full app view establishes context; its incidental
|
|
53
|
+
labels do not all need to be readable. Essential labels and results do.
|
|
54
|
+
|
|
55
|
+
## Make motion carry the story
|
|
56
|
+
|
|
57
|
+
- Give each shot one main movement. Delay or reduce secondary motion so it does not compete.
|
|
58
|
+
Let essential titles and UI settle while the viewer reads. Idle floating is not a demonstration.
|
|
59
|
+
- Contrast short transitions with longer action and result holds. As a starting estimate, allow
|
|
60
|
+
about `0.5 + 0.3 * wordCount` seconds for a short line after it settles. Validate with the actual
|
|
61
|
+
layout and audience; dense UI needs more time. Cut words or decoration to meet a fixed duration.
|
|
62
|
+
- Connect shots through a visible action, a continuing subject, matching framing or a deliberate
|
|
63
|
+
cut. Name the connection in the shot table. Do not require a transition quota or a new effect at
|
|
64
|
+
every cut. A clear hard cut is useful when a morph would distort the evidence.
|
|
65
|
+
- Keep important labels sharp during the reading window. Motion blur belongs to movement, not
|
|
66
|
+
the proof hold. Use the existing component catalog and `cinematic.md` tools where suitable.
|
|
67
|
+
Follow `browser-export.md`; a browser-only effect is not proof that an export works.
|
|
68
|
+
- Use source action times, narration timings or analyzed music cues. For a regular beat grid,
|
|
69
|
+
calculate each frame from its beat index and round once; repeated rounded intervals cause drift.
|
|
70
|
+
|
|
71
|
+
## Review the cuts and the meaning
|
|
72
|
+
|
|
73
|
+
Keep the main skill's full picture, sound and performance review. Add these checks to it:
|
|
74
|
+
|
|
75
|
+
1. Inspect frame 0, the settled proof and the final readable frame in each format. Read the shot
|
|
76
|
+
sequence as a new viewer. Without the headline, is the promised change still visible?
|
|
77
|
+
2. For each cut at frame `c`, sample `c - 1` and `c`, plus nearby frames across the transition.
|
|
78
|
+
Clamp samples to the video bounds. For a longer move, sample intermediate frames too. Look for
|
|
79
|
+
blank gaps, duplicated subjects, jumps in labels, obscured results and conflicting motion.
|
|
80
|
+
3. Inspect essential words and UI at a small display size, about 360 px wide where available.
|
|
81
|
+
If a tool cannot show that size, record this limit; do not claim a small-screen check passed.
|
|
82
|
+
4. Record concrete issues as `frame / variant / issue / change / recheck result` in `notes.md`.
|
|
83
|
+
Fix wrong claims, unreadable evidence and broken transitions before decorative details. Recheck
|
|
84
|
+
changed shots using `efficient-review.md`; timing or shared changes require broader checks.
|
|
85
|
+
|
|
86
|
+
At hand-off, state what was checked and any remaining weak shot or missing evidence. A build pass
|
|
87
|
+
only proves the project compiles. Do not describe a film as visually verified without viewing its
|
|
88
|
+
captures, or say sound was heard when it was only measured.
|
|
89
|
+
|
|
@@ -1,151 +1,151 @@
|
|
|
1
|
-
# Motion loops, brand palettes and variety
|
|
2
|
-
|
|
3
|
-
Agentcut ships a library of 44 seamless **motion loops** (all live at agentcut.synteq.app/loops),
|
|
4
|
-
each a pure function of time on a 12 s cycle (the frame at 12 s is the frame at 0 s), drawn from the
|
|
5
|
-
brand's colours. Use them so no video sits on a dead flat colour, and so every video looks different.
|
|
6
|
-
|
|
7
|
-
## Use one
|
|
8
|
-
|
|
9
|
-
- **As a clip** (the user can edit it in the inspector): component `motion-loop` on a track under the
|
|
10
|
-
content, e.g. `{ "component": "motion-loop", "props": { "loop": "dot-wave", "tone": "light",
|
|
11
|
-
"accent": "#f97316", "accent2": "#ec4899", "seed": 7 } }`. `agentcut_components` with
|
|
12
|
-
`id: "motion-loop"` lists every loop.
|
|
13
|
-
- **Inside a scene** (behind a cinematic Stage, on a card, in a split):
|
|
14
|
-
`import { LoopCanvas } from "agentcut/components"` →
|
|
15
|
-
`<LoopCanvas loop="iso-cubes" accent={brand} accent2={brand2} tone="dark" seed={3} />`. Without
|
|
16
|
-
`width`/`height` it is frame-sized and stretches to its parent, so use it full-frame (or in a box
|
|
17
|
-
with the frame's aspect). In any other box pass that box's size in px, e.g. on a `Plane` (a great
|
|
18
|
-
card in 3D): `<Plane width={800} height={500}><LoopCanvas loop="dot-wave" width={800} height={500} /></Plane>`;
|
|
19
|
-
then it draws at exactly that size and never distorts. Put it first inside `<Stage>` instead of
|
|
20
|
-
`<Backdrop>`, or on a Plane far behind the devices (`z: -800`) so it parallaxes with the camera.
|
|
21
|
-
- Props: `tone` `dark` (deep brand-tinted background, brand motif), `accent` (solid brand colour,
|
|
22
|
-
ink or paper motif), `light` (paper background, ink motif, brand as the second colour); `speed`
|
|
23
|
-
(seamless at any speed inside a clip; a clip that repeats needs length × speed to be a multiple of
|
|
24
|
-
12 s); `seed` (another layout of the same loop); `transparent` (shapes over footage or a Stage);
|
|
25
|
-
`blur` (motion-blur sub-frames in captures and exports, 4 default for both `motion-loop` and
|
|
26
|
-
`LoopCanvas`, 8 for fast loops, 1 for none; the live preview always draws 1). An unknown `loop` id
|
|
27
|
-
warns in the console and falls back to `gradient-blobs`.
|
|
28
|
-
|
|
29
|
-
## The library
|
|
30
|
-
|
|
31
|
-
Backgrounds: `perspective-grid` (grid floor streaming to a glowing horizon: tech, retro, gaming),
|
|
32
|
-
`dot-wave` (dots swelling in a diagonal wave: calm product), `flow-lines` (breathing signal lines: data,
|
|
33
|
-
finance), `gradient-blobs` (living mesh gradient: the safe premium backdrop), `stripes-scroll` (bold
|
|
34
|
-
diagonal stripes: loud promos, sport, sales), `concentric-pulse` (rings on the beat: reveals, music),
|
|
35
|
-
`checker-twist` (tiles twisting in a wave: playful, design), `halftone-sweep` (halftone with light
|
|
36
|
-
bands: editorial, print), `terrain-ridges` (ridgelines rolling in: moody, music, night), `starfield-warp`
|
|
37
|
-
(warp streaks: hype, speed), `bokeh-drift` (soft rising lights: dreamy, lifestyle, behind devices),
|
|
38
|
-
`iso-cubes` (isometric blocks rising: infrastructure, dev tools), `ribbon-weave` (thick waving
|
|
39
|
-
ribbons: fluid, consumer), `tile-mosaic` (tiles flipping colour: marketplaces, many features).
|
|
40
|
-
|
|
41
|
-
Symmetry: `kaleidoscope` (8-way mirrored drift: music, festivals, hypnotic), `mandala-bloom` (petal rings
|
|
42
|
-
turning both ways: wellness, elegant), `spirograph` (a pen tracing a spirograph: precision, design),
|
|
43
|
-
`mirror-tiles` (four-way mirrored arc tiles turning: design, architecture), `radial-burst` (retro sunburst:
|
|
44
|
-
announcements, sales, pop).
|
|
45
|
-
|
|
46
|
-
Morphing: `shape-morph` (circle → square → triangle → star with squash: transformation, versatility),
|
|
47
|
-
`morph-grid` (a grid of shapes morphing in a wave: systems, modular), `shape-shuffle` (three shapes
|
|
48
|
-
hopping and becoming each other: choices, onboarding), `metaballs` (liquid blobs merging: fluid, AI).
|
|
49
|
-
|
|
50
|
-
Games: `snake-game` (pixel snake eating food: gaming, retro, 'level up'), `falling-blocks` (blocks stack and
|
|
51
|
-
clear: building, organizing), `pong` (paddles rallying: back-and-forth, versus), `life-gliders`
|
|
52
|
-
(Game of Life gliders: code, dev tools, emergence).
|
|
53
|
-
|
|
54
|
-
Physics: `newtons-cradle` (momentum, cause and effect), `clock-gears` (automation, workflows),
|
|
55
|
-
`liquid-fill` (progress, growth, drinks), `domino-wave` (chain reactions, automation).
|
|
56
|
-
|
|
57
|
-
Generative: `vortex` (particles spiralling into a core: AI, gravity), `lissajous-trail` (a comet tracing
|
|
58
|
-
a Lissajous figure: signals, elegance), `bubble-pop` (bubbles rising and popping: playful, social).
|
|
59
|
-
|
|
60
|
-
Shapes (one centered subject, use `transparent` over other layers): `orbit-rings` (AI, platforms),
|
|
61
|
-
`morph-blob` (assistants, organic), `bouncing-ball` (playful, loading), `spinner-petals` (blooming,
|
|
62
|
-
wellness), `stacked-squares` (layers, structure), `ripple-drop` (impact, calm), `cube-spin`
|
|
63
|
-
(products, blocks), `dna-helix` (science, health, data), `pie-burst` (analytics, sharing),
|
|
64
|
-
`wave-bars` (audio, voice, podcasts).
|
|
65
|
-
|
|
66
|
-
## "Generated by an agent" effects
|
|
67
|
-
|
|
68
|
-
- `dot-trace-title` (component): a headline traced in dots by a scan line that resolves into the type.
|
|
69
|
-
For AI features, agents, "built for you" moments. Lines take `*starred*` words or a `*starred phrase*`
|
|
70
|
-
for the accent; `size` is a share of the frame's short side (× 0.9), `dot` is px at 1080p (scales).
|
|
71
|
-
- `GenerateReveal` (scenes, from `agentcut/components`): a screenshot or photo builds itself the way an
|
|
72
|
-
agent would generate it: dotted wireframes per UI block (with the agent's cursor), a dotted fill made of
|
|
73
|
-
the image's own pixels, then the real pixels resolve block by block, with an optional agent log. When
|
|
74
|
-
the build ends (`from + duration`) the whole image cross-fades in over ~10 frames, so the end state is
|
|
75
|
-
exactly the screenshot, including areas no box covers.
|
|
76
|
-
`<GenerateReveal src={asset("assets/app.png")} width={1440} height={900} from={0} duration={120}
|
|
77
|
-
boxes={[[0,0,0.16,1],[0.18,0.1,0.79,0.08], …]} log={["Laying out the sidebar", …]} accent={brand} />`
|
|
78
|
-
- `width`/`height`: the box in px; the image covers it (crop like `object-fit: cover`). Inside a
|
|
79
|
-
cinematic `Screen` (as its children) the Screen's `width` and `aspect` define the box: pass
|
|
80
|
-
`width={W} height={W / aspect}` with the same values, or the build won't fill the screen.
|
|
81
|
-
- `boxes`: the UI's blocks `[x, y, w, h]` as fractions of the image in build order; measure them from
|
|
82
|
-
the image like hero regions (values are clamped to 0–1). Leave out for photos (one block).
|
|
83
|
-
- `mode`: `"ui"` (wireframe → dots → pixels) or `"image"` (tone sketch → colour dots → photo).
|
|
84
|
-
- `dot` (pitch in box px, default 9), `accent`, `log` (one line per block reads best; Geist Mono, loaded
|
|
85
|
-
and held for you), `logPosition`, `radius`, `background`.
|
|
86
|
-
- `resolution`: pixel ratio of the dots canvas, default 2 in renders/exports (sharp under a camera
|
|
87
|
-
push-in) and 1 in the live preview; lower it for very large boxes. A Plane's blurred and reflected
|
|
88
|
-
copies draw it at 0.5 automatically.
|
|
89
|
-
- The dotted fill reads the image's pixels, so it needs a same-origin asset (`asset(…)`) or a CORS-enabled
|
|
90
|
-
URL. Otherwise it logs a warning and builds without the dotted fill (wireframes, log and pixel reveal
|
|
91
|
-
still play); it never stops the export. A missing image still fails the render (its `<Img>`).
|
|
92
|
-
Use it once per video, as the hook or the "watch it build" moment.
|
|
93
|
-
|
|
94
|
-
## Brand palette first
|
|
95
|
-
|
|
96
|
-
1. Find the brand colours before you design: the logo, the product UI in the screenshots, the
|
|
97
|
-
website, `project.json`. Write them in notes.md: primary, secondary, and the brand's own dark and
|
|
98
|
-
light (often in the UI).
|
|
99
|
-
2. Build every look from them: `accent` = primary, `accent2` = secondary (or a complement: the primary's
|
|
100
|
-
opposite hue at lower saturation), tone per shot. Text on the loop: ink on `light`, paper on `dark`,
|
|
101
|
-
whichever reads on `accent`.
|
|
102
|
-
3. Two or three colours per frame, never a rainbow. One accent moment per shot.
|
|
103
|
-
|
|
104
|
-
## Variety (every video, every take)
|
|
105
|
-
|
|
106
|
-
- Never the same loop twice in a row, and at least three different loops or looks in a 15–30 s video.
|
|
107
|
-
- Alternate tones between shots (dark → light → accent …) or hold one tone and vary the loop: decide,
|
|
108
|
-
then write the rotation in the shot list.
|
|
109
|
-
- Change `seed` when you reuse a loop, and pick loops by mood (the list above), not by habit: before
|
|
110
|
-
you choose, write the two you used in the last video in notes.md (if any) and pick others.
|
|
111
|
-
- Mix layers: a background loop, the hero (screens, devices, type), and sometimes a shape loop as an
|
|
112
|
-
accent (transparent, small, in a corner or behind a title) or kinetic shapes on a Plane in depth.
|
|
113
|
-
- Shape loops are great section openers and end cards: a centered shape with the brand name below it.
|
|
114
|
-
|
|
115
|
-
## Write a new loop (when nothing fits)
|
|
116
|
-
|
|
117
|
-
Write it in the scene as a draw function and pass it to `LoopCanvas`:
|
|
118
|
-
|
|
119
|
-
```tsx
|
|
120
|
-
import { LoopCanvas, type LoopDraw } from "agentcut/components";
|
|
121
|
-
const sparks: LoopDraw = (ctx, w, h, t, P, M, seed) => {
|
|
122
|
-
const u = h / 100;
|
|
123
|
-
for (let i = 0; i < 60; i++) {
|
|
124
|
-
const p = M.phase(t, 3, M.rand(i, seed)); // a 3 s cycle, staggered per element
|
|
125
|
-
ctx.fillStyle = M.rgba(i % 4 ? P.fg : P.fg2, 1 - p);
|
|
126
|
-
ctx.beginPath();
|
|
127
|
-
ctx.arc(M.rand(i, 1) * w, h - p * h, u * (0.5 + 2 * M.rand(i, 2)), 0, M.TAU);
|
|
128
|
-
ctx.fill();
|
|
129
|
-
}
|
|
130
|
-
};
|
|
131
|
-
// <LoopCanvas loop={sparks} accent={brand} tone="dark" />
|
|
132
|
-
```
|
|
133
|
-
|
|
134
|
-
Rules that keep it seamless and premium:
|
|
135
|
-
- The frame depends on `t` only: no `Math.random`, `Date` or state between frames; randomness from
|
|
136
|
-
`M.rand(i, salt)`. Every period divides 12 (1, 1.5, 2, 3, 4, 6, 12) via `M.phase(t, period, offset)`;
|
|
137
|
-
scrolls move whole pattern repeats per period; anything indexed by cycle wraps with `M.mod`.
|
|
138
|
-
- Colours only from `P` (`bg fg fg2 mid accent accent2 paper ink`) with `M.rgba` / `M.mixColor`.
|
|
139
|
-
- Sizes from `u = h / 100` (shapes: `Math.min(w, h) / 100`), counts from `w`, so it works in wide and
|
|
140
|
-
mobile.
|
|
141
|
-
- Designed motion: eases from `M.ease` (`outBack`, `spring`, `inOutCubic`…), anticipation and
|
|
142
|
-
overshoot, short holds; constant speed only for scrolls and streams. `M.win(p, a, b)` chains
|
|
143
|
-
wind-up, action and settle inside a cycle; put the loop point inside a hold.
|
|
144
|
-
- Keep a frame under ~2,000 primitives; glows are radial gradients, never `ctx.filter`.
|
|
145
|
-
- Check it: capture frames inside one cycle and either side of the 12 s point.
|
|
146
|
-
|
|
147
|
-
A loop worth keeping for other videos: save it in the workspace library
|
|
148
|
-
(`library/loops/<name>.ts`, exporting the draw function) with a one-line description at the top, and
|
|
149
|
-
list it in `library/loops/README.md`. Later videos import it by relative path from their scene:
|
|
150
|
-
`import { sparks } from "../../../library/loops/sparks";` (scenes live in `projects/<slug>/scenes/`).
|
|
151
|
-
Read `library/loops/README.md` before writing a new loop: one may already exist.
|
|
1
|
+
# Motion loops, brand palettes and variety
|
|
2
|
+
|
|
3
|
+
Agentcut ships a library of 44 seamless **motion loops** (all live at agentcut.synteq.app/loops),
|
|
4
|
+
each a pure function of time on a 12 s cycle (the frame at 12 s is the frame at 0 s), drawn from the
|
|
5
|
+
brand's colours. Use them so no video sits on a dead flat colour, and so every video looks different.
|
|
6
|
+
|
|
7
|
+
## Use one
|
|
8
|
+
|
|
9
|
+
- **As a clip** (the user can edit it in the inspector): component `motion-loop` on a track under the
|
|
10
|
+
content, e.g. `{ "component": "motion-loop", "props": { "loop": "dot-wave", "tone": "light",
|
|
11
|
+
"accent": "#f97316", "accent2": "#ec4899", "seed": 7 } }`. `agentcut_components` with
|
|
12
|
+
`id: "motion-loop"` lists every loop.
|
|
13
|
+
- **Inside a scene** (behind a cinematic Stage, on a card, in a split):
|
|
14
|
+
`import { LoopCanvas } from "agentcut/components"` →
|
|
15
|
+
`<LoopCanvas loop="iso-cubes" accent={brand} accent2={brand2} tone="dark" seed={3} />`. Without
|
|
16
|
+
`width`/`height` it is frame-sized and stretches to its parent, so use it full-frame (or in a box
|
|
17
|
+
with the frame's aspect). In any other box pass that box's size in px, e.g. on a `Plane` (a great
|
|
18
|
+
card in 3D): `<Plane width={800} height={500}><LoopCanvas loop="dot-wave" width={800} height={500} /></Plane>`;
|
|
19
|
+
then it draws at exactly that size and never distorts. Put it first inside `<Stage>` instead of
|
|
20
|
+
`<Backdrop>`, or on a Plane far behind the devices (`z: -800`) so it parallaxes with the camera.
|
|
21
|
+
- Props: `tone` `dark` (deep brand-tinted background, brand motif), `accent` (solid brand colour,
|
|
22
|
+
ink or paper motif), `light` (paper background, ink motif, brand as the second colour); `speed`
|
|
23
|
+
(seamless at any speed inside a clip; a clip that repeats needs length × speed to be a multiple of
|
|
24
|
+
12 s); `seed` (another layout of the same loop); `transparent` (shapes over footage or a Stage);
|
|
25
|
+
`blur` (motion-blur sub-frames in captures and exports, 4 default for both `motion-loop` and
|
|
26
|
+
`LoopCanvas`, 8 for fast loops, 1 for none; the live preview always draws 1). An unknown `loop` id
|
|
27
|
+
warns in the console and falls back to `gradient-blobs`.
|
|
28
|
+
|
|
29
|
+
## The library
|
|
30
|
+
|
|
31
|
+
Backgrounds: `perspective-grid` (grid floor streaming to a glowing horizon: tech, retro, gaming),
|
|
32
|
+
`dot-wave` (dots swelling in a diagonal wave: calm product), `flow-lines` (breathing signal lines: data,
|
|
33
|
+
finance), `gradient-blobs` (living mesh gradient: the safe premium backdrop), `stripes-scroll` (bold
|
|
34
|
+
diagonal stripes: loud promos, sport, sales), `concentric-pulse` (rings on the beat: reveals, music),
|
|
35
|
+
`checker-twist` (tiles twisting in a wave: playful, design), `halftone-sweep` (halftone with light
|
|
36
|
+
bands: editorial, print), `terrain-ridges` (ridgelines rolling in: moody, music, night), `starfield-warp`
|
|
37
|
+
(warp streaks: hype, speed), `bokeh-drift` (soft rising lights: dreamy, lifestyle, behind devices),
|
|
38
|
+
`iso-cubes` (isometric blocks rising: infrastructure, dev tools), `ribbon-weave` (thick waving
|
|
39
|
+
ribbons: fluid, consumer), `tile-mosaic` (tiles flipping colour: marketplaces, many features).
|
|
40
|
+
|
|
41
|
+
Symmetry: `kaleidoscope` (8-way mirrored drift: music, festivals, hypnotic), `mandala-bloom` (petal rings
|
|
42
|
+
turning both ways: wellness, elegant), `spirograph` (a pen tracing a spirograph: precision, design),
|
|
43
|
+
`mirror-tiles` (four-way mirrored arc tiles turning: design, architecture), `radial-burst` (retro sunburst:
|
|
44
|
+
announcements, sales, pop).
|
|
45
|
+
|
|
46
|
+
Morphing: `shape-morph` (circle → square → triangle → star with squash: transformation, versatility),
|
|
47
|
+
`morph-grid` (a grid of shapes morphing in a wave: systems, modular), `shape-shuffle` (three shapes
|
|
48
|
+
hopping and becoming each other: choices, onboarding), `metaballs` (liquid blobs merging: fluid, AI).
|
|
49
|
+
|
|
50
|
+
Games: `snake-game` (pixel snake eating food: gaming, retro, 'level up'), `falling-blocks` (blocks stack and
|
|
51
|
+
clear: building, organizing), `pong` (paddles rallying: back-and-forth, versus), `life-gliders`
|
|
52
|
+
(Game of Life gliders: code, dev tools, emergence).
|
|
53
|
+
|
|
54
|
+
Physics: `newtons-cradle` (momentum, cause and effect), `clock-gears` (automation, workflows),
|
|
55
|
+
`liquid-fill` (progress, growth, drinks), `domino-wave` (chain reactions, automation).
|
|
56
|
+
|
|
57
|
+
Generative: `vortex` (particles spiralling into a core: AI, gravity), `lissajous-trail` (a comet tracing
|
|
58
|
+
a Lissajous figure: signals, elegance), `bubble-pop` (bubbles rising and popping: playful, social).
|
|
59
|
+
|
|
60
|
+
Shapes (one centered subject, use `transparent` over other layers): `orbit-rings` (AI, platforms),
|
|
61
|
+
`morph-blob` (assistants, organic), `bouncing-ball` (playful, loading), `spinner-petals` (blooming,
|
|
62
|
+
wellness), `stacked-squares` (layers, structure), `ripple-drop` (impact, calm), `cube-spin`
|
|
63
|
+
(products, blocks), `dna-helix` (science, health, data), `pie-burst` (analytics, sharing),
|
|
64
|
+
`wave-bars` (audio, voice, podcasts).
|
|
65
|
+
|
|
66
|
+
## "Generated by an agent" effects
|
|
67
|
+
|
|
68
|
+
- `dot-trace-title` (component): a headline traced in dots by a scan line that resolves into the type.
|
|
69
|
+
For AI features, agents, "built for you" moments. Lines take `*starred*` words or a `*starred phrase*`
|
|
70
|
+
for the accent; `size` is a share of the frame's short side (× 0.9), `dot` is px at 1080p (scales).
|
|
71
|
+
- `GenerateReveal` (scenes, from `agentcut/components`): a screenshot or photo builds itself the way an
|
|
72
|
+
agent would generate it: dotted wireframes per UI block (with the agent's cursor), a dotted fill made of
|
|
73
|
+
the image's own pixels, then the real pixels resolve block by block, with an optional agent log. When
|
|
74
|
+
the build ends (`from + duration`) the whole image cross-fades in over ~10 frames, so the end state is
|
|
75
|
+
exactly the screenshot, including areas no box covers.
|
|
76
|
+
`<GenerateReveal src={asset("assets/app.png")} width={1440} height={900} from={0} duration={120}
|
|
77
|
+
boxes={[[0,0,0.16,1],[0.18,0.1,0.79,0.08], …]} log={["Laying out the sidebar", …]} accent={brand} />`
|
|
78
|
+
- `width`/`height`: the box in px; the image covers it (crop like `object-fit: cover`). Inside a
|
|
79
|
+
cinematic `Screen` (as its children) the Screen's `width` and `aspect` define the box: pass
|
|
80
|
+
`width={W} height={W / aspect}` with the same values, or the build won't fill the screen.
|
|
81
|
+
- `boxes`: the UI's blocks `[x, y, w, h]` as fractions of the image in build order; measure them from
|
|
82
|
+
the image like hero regions (values are clamped to 0–1). Leave out for photos (one block).
|
|
83
|
+
- `mode`: `"ui"` (wireframe → dots → pixels) or `"image"` (tone sketch → colour dots → photo).
|
|
84
|
+
- `dot` (pitch in box px, default 9), `accent`, `log` (one line per block reads best; Geist Mono, loaded
|
|
85
|
+
and held for you), `logPosition`, `radius`, `background`.
|
|
86
|
+
- `resolution`: pixel ratio of the dots canvas, default 2 in renders/exports (sharp under a camera
|
|
87
|
+
push-in) and 1 in the live preview; lower it for very large boxes. A Plane's blurred and reflected
|
|
88
|
+
copies draw it at 0.5 automatically.
|
|
89
|
+
- The dotted fill reads the image's pixels, so it needs a same-origin asset (`asset(…)`) or a CORS-enabled
|
|
90
|
+
URL. Otherwise it logs a warning and builds without the dotted fill (wireframes, log and pixel reveal
|
|
91
|
+
still play); it never stops the export. A missing image still fails the render (its `<Img>`).
|
|
92
|
+
Use it once per video, as the hook or the "watch it build" moment.
|
|
93
|
+
|
|
94
|
+
## Brand palette first
|
|
95
|
+
|
|
96
|
+
1. Find the brand colours before you design: the logo, the product UI in the screenshots, the
|
|
97
|
+
website, `project.json`. Write them in notes.md: primary, secondary, and the brand's own dark and
|
|
98
|
+
light (often in the UI).
|
|
99
|
+
2. Build every look from them: `accent` = primary, `accent2` = secondary (or a complement: the primary's
|
|
100
|
+
opposite hue at lower saturation), tone per shot. Text on the loop: ink on `light`, paper on `dark`,
|
|
101
|
+
whichever reads on `accent`.
|
|
102
|
+
3. Two or three colours per frame, never a rainbow. One accent moment per shot.
|
|
103
|
+
|
|
104
|
+
## Variety (every video, every take)
|
|
105
|
+
|
|
106
|
+
- Never the same loop twice in a row, and at least three different loops or looks in a 15–30 s video.
|
|
107
|
+
- Alternate tones between shots (dark → light → accent …) or hold one tone and vary the loop: decide,
|
|
108
|
+
then write the rotation in the shot list.
|
|
109
|
+
- Change `seed` when you reuse a loop, and pick loops by mood (the list above), not by habit: before
|
|
110
|
+
you choose, write the two you used in the last video in notes.md (if any) and pick others.
|
|
111
|
+
- Mix layers: a background loop, the hero (screens, devices, type), and sometimes a shape loop as an
|
|
112
|
+
accent (transparent, small, in a corner or behind a title) or kinetic shapes on a Plane in depth.
|
|
113
|
+
- Shape loops are great section openers and end cards: a centered shape with the brand name below it.
|
|
114
|
+
|
|
115
|
+
## Write a new loop (when nothing fits)
|
|
116
|
+
|
|
117
|
+
Write it in the scene as a draw function and pass it to `LoopCanvas`:
|
|
118
|
+
|
|
119
|
+
```tsx
|
|
120
|
+
import { LoopCanvas, type LoopDraw } from "agentcut/components";
|
|
121
|
+
const sparks: LoopDraw = (ctx, w, h, t, P, M, seed) => {
|
|
122
|
+
const u = h / 100;
|
|
123
|
+
for (let i = 0; i < 60; i++) {
|
|
124
|
+
const p = M.phase(t, 3, M.rand(i, seed)); // a 3 s cycle, staggered per element
|
|
125
|
+
ctx.fillStyle = M.rgba(i % 4 ? P.fg : P.fg2, 1 - p);
|
|
126
|
+
ctx.beginPath();
|
|
127
|
+
ctx.arc(M.rand(i, 1) * w, h - p * h, u * (0.5 + 2 * M.rand(i, 2)), 0, M.TAU);
|
|
128
|
+
ctx.fill();
|
|
129
|
+
}
|
|
130
|
+
};
|
|
131
|
+
// <LoopCanvas loop={sparks} accent={brand} tone="dark" />
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
Rules that keep it seamless and premium:
|
|
135
|
+
- The frame depends on `t` only: no `Math.random`, `Date` or state between frames; randomness from
|
|
136
|
+
`M.rand(i, salt)`. Every period divides 12 (1, 1.5, 2, 3, 4, 6, 12) via `M.phase(t, period, offset)`;
|
|
137
|
+
scrolls move whole pattern repeats per period; anything indexed by cycle wraps with `M.mod`.
|
|
138
|
+
- Colours only from `P` (`bg fg fg2 mid accent accent2 paper ink`) with `M.rgba` / `M.mixColor`.
|
|
139
|
+
- Sizes from `u = h / 100` (shapes: `Math.min(w, h) / 100`), counts from `w`, so it works in wide and
|
|
140
|
+
mobile.
|
|
141
|
+
- Designed motion: eases from `M.ease` (`outBack`, `spring`, `inOutCubic`…), anticipation and
|
|
142
|
+
overshoot, short holds; constant speed only for scrolls and streams. `M.win(p, a, b)` chains
|
|
143
|
+
wind-up, action and settle inside a cycle; put the loop point inside a hold.
|
|
144
|
+
- Keep a frame under ~2,000 primitives; glows are radial gradients, never `ctx.filter`.
|
|
145
|
+
- Check it: capture frames inside one cycle and either side of the 12 s point.
|
|
146
|
+
|
|
147
|
+
A loop worth keeping for other videos: save it in the workspace library
|
|
148
|
+
(`library/loops/<name>.ts`, exporting the draw function) with a one-line description at the top, and
|
|
149
|
+
list it in `library/loops/README.md`. Later videos import it by relative path from their scene:
|
|
150
|
+
`import { sparks } from "../../../library/loops/sparks";` (scenes live in `projects/<slug>/scenes/`).
|
|
151
|
+
Read `library/loops/README.md` before writing a new loop: one may already exist.
|
|
@@ -1,19 +1,19 @@
|
|
|
1
|
-
# Working through MCP from outside the workspace
|
|
2
|
-
|
|
3
|
-
Use the same creative and review workflow whether you work inside Agentcut or through MCP.
|
|
4
|
-
Start with `agentcut_capabilities`, `SKILL.md` through `agentcut_guide`, then `agentcut_status`.
|
|
5
|
-
Supporting `references/*.md` files are available through `agentcut_guide` and MCP guide resources.
|
|
6
|
-
If you cannot read the helper's local disk, use `agentcut_list_files`, `agentcut_read_file`,
|
|
7
|
-
`agentcut_write_file` and `agentcut_copy_file`. These operate on the connected helper's workspace,
|
|
8
|
-
not your own current folder. Read before writing and pass the returned hash to preserve hand edits.
|
|
9
|
-
Use `baseHash: null` only for a new file. Call status after scene or timeline edits to check the build.
|
|
10
|
-
|
|
11
|
-
File scopes are `project`, `library` and read-only `toolkit`. Workspace `library/presets/...` is
|
|
12
|
-
scope `library`, path `presets/...`; `.agentcut/components/...` is scope `toolkit`, path
|
|
13
|
-
`components/...`; `.agentcut/runtime/...` is scope `toolkit`, path `runtime/...`. List preset files,
|
|
14
|
-
read their recipes and copy their scenes/assets into the project. Music, SFX and b-roll catalogs
|
|
15
|
-
use their existing search/add tools. Capture and contact-sheet calls return MCP images as well
|
|
16
|
-
as local paths, so visual review does not require a shared disk. Keep all creative and review steps.
|
|
17
|
-
For local app code, call `agentcut_sources`. Scope `source` reads only folders already allowed
|
|
18
|
-
with the helper's `--add-dir` option; pass the returned ID as `source` for list/read, or
|
|
19
|
-
`sourceRoot` for copy. Source folders stay read-only. MCP cannot grant itself new folder access.
|
|
1
|
+
# Working through MCP from outside the workspace
|
|
2
|
+
|
|
3
|
+
Use the same creative and review workflow whether you work inside Agentcut or through MCP.
|
|
4
|
+
Start with `agentcut_capabilities`, `SKILL.md` through `agentcut_guide`, then `agentcut_status`.
|
|
5
|
+
Supporting `references/*.md` files are available through `agentcut_guide` and MCP guide resources.
|
|
6
|
+
If you cannot read the helper's local disk, use `agentcut_list_files`, `agentcut_read_file`,
|
|
7
|
+
`agentcut_write_file` and `agentcut_copy_file`. These operate on the connected helper's workspace,
|
|
8
|
+
not your own current folder. Read before writing and pass the returned hash to preserve hand edits.
|
|
9
|
+
Use `baseHash: null` only for a new file. Call status after scene or timeline edits to check the build.
|
|
10
|
+
|
|
11
|
+
File scopes are `project`, `library` and read-only `toolkit`. Workspace `library/presets/...` is
|
|
12
|
+
scope `library`, path `presets/...`; `.agentcut/components/...` is scope `toolkit`, path
|
|
13
|
+
`components/...`; `.agentcut/runtime/...` is scope `toolkit`, path `runtime/...`. List preset files,
|
|
14
|
+
read their recipes and copy their scenes/assets into the project. Music, SFX and b-roll catalogs
|
|
15
|
+
use their existing search/add tools. Capture and contact-sheet calls return MCP images as well
|
|
16
|
+
as local paths, so visual review does not require a shared disk. Keep all creative and review steps.
|
|
17
|
+
For local app code, call `agentcut_sources`. Scope `source` reads only folders already allowed
|
|
18
|
+
with the helper's `--add-dir` option; pass the returned ID as `source` for list/read, or
|
|
19
|
+
`sourceRoot` for copy. Source folders stay read-only. MCP cannot grant itself new folder access.
|