cashew-labs

Create a code-based implementation spec in the specs/ directory for a significant feature, fix, or refactor. Use when the user asks to plan, spec, scope, or phase work before implementation and the plan should cover top-level Mermaid flows, important types,…

Read-only Libretto workflow for diagnosing live browser state without clicks, typing, navigation, or mutation requests.

Browser automation CLI for building, maintaining, and running browser automation workflows by inspecting live pages and prototyping interactions.

Automate user-installed Electron desktop apps (Slack, Discord, VS Code, Notion, Figma, Spotify, etc.) via CDP using this repo's Libretto CLI. Use when the task is to control a local desktop app on the user's machine, not this repo's own Electron app.…

errore is Go-style error handling for TypeScript: return errors instead of throwing them. Instead of Go's two-value tuple (val, err), functions return a single Error | T union. Instead of checking err != nil, you check instanceof Error. TypeScript narrows the…

Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take…

Create a visual explanation of the current session diff as a single HTML page and show it in a native Glimpse window. Use when the user wants a visual walkthrough of local code changes instead of a plain text diff.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase…

SolidJS framework development skill for building reactive web applications with fine-grained reactivity. Use when working with SolidJS projects including: (1) Creating components with signals, stores, and effects, (2) Implementing reactive state management,…

Interact with the running VSCode extension via Playwright. Use when automating, testing, or debugging the OpenCode webview UI.

Create a spec sheet for the given feature/fix request in specs/ directory. Use when planning a significant new feature or complex fix.

Browser automation CLI using Playwright. Use when automating browser workflows, filling forms, clicking elements, scraping pages, or debugging web issues.

Review a spec for under-specified areas, bugs, and adherence to the generate-spec skill. Use when asked to review, critique, or check a spec.

Update AGENTS.md files based on session learnings about a topic. Use when documenting patterns, commands, or conventions discovered during development.

Stage all changes and commit with appropriate message, showing changed files and edits. Use when you need to create a git commit.

Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.

Drive and test the running Halo Electron debug renderer with the development CLI, or inspect an extension in an isolated browser using the workspace CLI.

Apply repository design and testing conventions when writing, refactoring, or reviewing TypeScript packages, services, state, tests, or runtime hosts. Includes package-level E2Es and fixture design.

Access, inspect, interact with, create, edit, run, and verify Halo workspace extensions using the bundled browser, React, oRPC, Tandem, and connected-tool SDK.

Conventions and design constraints for consuming the Maui design system. Use when building UI with Maui tokens, components, or purse-styles in an app that depends on Maui. Before designing or implementing new UI, read the closest example under src/apps/ or…

Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.

Explain implemented changes through annotated call stack diffs and prose, store the markdown in a temp directory, and serve it with tkstack.

Research and collaboratively design a significant feature, fix, or refactor, then write a phased implementation spec in specs/ and serve it with tkstack. Use when the user asks to plan, spec, scope, or phase work before implementation.

Create a spec sheet for the given feature/fix request in specs/ directory. Use when planning a significant new feature or complex fix.