script-kit-next

Agent-facing DevTools for Script Kit GPUI: use protocol, MCP, and CLI primitives to inspect, control, measure, debug, benchmark, and prove real app UI behavior from bug reports without defaulting to prewritten agentic-testing recipes.

Manage the Notes window — creating, searching, editing, and automating notes via the SDK and automation protocol.

Use the local agy CLI as a fast Script Kit GPUI app inspector by prompting it to drive existing script-kit-devtools primitives, capture logs, and produce a compact investigation result from a user bug report or inspection prompt.

Add Actions Menu commands to scripts and scriptlet bundles with setActions() and companion .actions.md files.

Configure external MCP servers for scripts and Agent Chat. Use when the user wants to add, remove, enable, disable, or inspect MCP servers in Script Kit.

Create or update scriptlet bundles for text expansions, snippets, shell commands, and lightweight helpers in a single markdown file.

Start and manage Agent Chat conversations from scripts, including typed context parts, streaming status, and chat lifecycle operations.

Update Script Kit configuration files — hotkeys, theme, layout, dictation, Claude Code, and workspace settings.

Create mdflow-backed agent files for Script Kit. Compatibility path — prefer creating skills (SKILL.md under a plugin's skills/ directory) for new reusable AI work.

Create or update TypeScript scripts for Script Kit. Use when the user wants to write a new script, edit an existing script, or understand Script Kit's SDK and metadata system.

Diagnose and fix common Script Kit issues. Use when the user reports bugs, crashes, missing features, or unexpected behavior in Script Kit GPUI.

Based on existing docs styles and specific API implementations, and referencing same name stories, generate comprehensive documentation for the new component.

Generate a comprehensive story for a new component for as example.

How to write a new component of GPUI Component.