Type '@', open the tool menu, filter it by typing, and commit an inline app chip
Study the source, inspect the editable build, then adapt the treatment to your own content.
What the source does
In the left chat pane a composer is typed quickly: 'Can y' at ~f2, 'Can you build' at ~f6, and the moment '@' lands (~f10) a white menu card pops above the composer listing generic actions (Add, Files and folders, Goal, Plan mode, ...). Typing 'insta' (~f11-14) swaps it for a shorter, filtered list of matching apps with the first row highlighted. At ~f18 the highlighted app becomes a green inline chip in the composer and the menu vanishes; ' grocery list?' is typed after the chip by ~f30 and holds. The right pane's orange grocery checklist is static.
Mention trigger: a typed '@' opens a command menu, further characters filter it, and selecting converts the typed token into a persistent inline chip.
Phase notes
- Frame 0 — Typing begins
- Frame 10 — '@' opens the generic menu
- Frame 14 — Menu filters to matching apps
- Frame 18 — Selection becomes an inline chip; menu closes
- Frame 30 — Trailing words typed
- Frame 36 — End
Use this example
- Watch the source and draft at normal speed. Compare the order of actions, the held states, and the transition into the result.
- Download the project and read its README before changing inputs. The package includes its implementation and declared dependencies.
- Replace the sample content through the package's documented input or content builder. Keep source footage in the research comparison.
- Render your adaptation and inspect text fit, framing, intermediate states, and entry and exit frames.
The source and remake are different assets. The original code-based illustration remains editable; source footage is a research reference. Read the retained findings below before using the choreography.
Recorded limits
- Visual fidelity is an authored draft judgement from sampled source frames; no independent blind review or native Resolve execution.