Starts and structures Raycast extension work: locate the extension folder, sync git, create a feature branch, install deps, and run dev from the extension directory (ray develop or npm run dev). Use when beginning work on a Raycast extension, after the user names an extension or says to start development, or when…
Checks out and runs Raycast extensions from github.com/raycast/extensions pull requests via sparse clone of the contributor fork, then npm install and dev. Use when reviewing extension PRs, testing a fork locally, or when the user shares a Raycast extensions PR URL or needs the checkout workflow.
Creates and reviews Raycast extensions against official Store requirements. Use when building new Raycast extensions, preparing for Store submission, reviewing package.json/manifest, or when the user asks about Raycast extension guidelines. Fetches latest docs to stay current.
Runs the workspace bootstrap script that git-inits cursor-rules and raycast-extensions when needed, copies cursor-rules skills into .cursor/skills/, and npm installs each Raycast extension under raycast-extensions/extensions/. Use when cloning or setting up this workspace, syncing skills after pulling cursor-rules…
★not rated 3 4mo agoA94 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: