with one click
with one click
How stagewise's agent history compression pipeline works — boundary selection, recency bias, chained compressions, and the SQLite-backed test harness for replaying real compressions in LLM playgrounds. Use when debugging, tuning, or extending history compression, when investigating context-window overflow, or when the user wants to probe compression quality against real chat histories.
Complete guide for the Figma plugin — REST API access, real-time selection monitoring via CDP, and the figma-app interactive UI. Read this IMMEDIATELY when the user asks to work with Figma.
Implement the most recent plan
Create a structured implementation plan before coding
Create or edit video with Remotion. First-party stagewise + Remotion skill. Contains full video-making process.
Use logging calls for in-depth debugging via local log files
| name | Preview |
| description | Create an interactive design-preview in the chat |
| user-invocable | true |
| agent-invocable | false |
Build a mini-app to fulfill the request. Use the apps/ directory and API.openApp() as documented in the Application Environment section.
apps/{appId}/index.html (+ optional styles.css, script.js).max-width: 100%; overflow-x: hidden).multiEdit, overwriteFile) for edits, then call API.openApp(appId) again to reload.index.html per app. Sibling assets resolve via relative paths (./styles.css).opts.height on openApp when the default 300px is wrong for the content.API.sendMessage / API.onMessage only when bidirectional communication is needed.