raycast
Skill1 starsChanged 11 days agoMITView on GitHub
Raycast extension development standards. Use when writing or modifying Raycast extensions. Run lintro first, then Raycast's toolchain (npm run lint) which takes precedence for extension-specific rules.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- adriangrantdotorg/Raycast-Skilltheir own version, first seen Nov 4, 2026
- adriangrantdotorg/Raycast-AI-Skilltheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- adriangrantdotorg/Raycast-AI-Skill★ 10same name
- adriangrantdotorg/Raycast-Skill★ 10same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-codeSkill
- analyze-projectSkill
- analyze-testsSkill
- audit-mergesSkill
- babysit-prSkill
- backlogSkill
- branchSkill
- coderabbitSkill
- commitSkill
- greptileSkill
- implement-issuesSkill
- issueSkill
- jiraSkill
- lintro-addSkill
- lintro-reviewSkill
- lintro-verifySkill
- lintSkill
- properizeSkill
- pr-raycastSkill
- prSkill
- rebaseSkill
- reconcileSkill
- scorecardSkill
- stand-ciSkill
- stand-generalSkill
- stand-odinSkill
- stand-pySkill
- stand-rustSkill
- stand-tsSkill
- sweep-prsSkill
- test-apiSkill
- test-shellSkill
- testSkill
- test-ui-qsfSkill
- test-uiSkill
- turbo-addSkill
- turbo-testSkill
- turbo-verifySkill
- which-prSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use when writing or modifying a Raycast extension.
- Very specific: line 72
Verify before asking to open a PR (full workflow in pr-raycast).
- Very specific: line 102
Add yourself to contributors in package.json.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Raycast Extension Development
Scope
Use when writing or modifying a Raycast extension. To open or prepare a PR to
raycast/extensions, use pr-raycast instead.
Overrides global lint/commit defaults in extension directories.
Official resources
Linting & Formatting
Order: lintro first → Raycast last. Raycast wins on conflicts.
# 1. Repo root (when lintro is configured)
uv run lintro fmt && uv run lintro chk
# 2. extensions/<name>/ — required before commit
npm run lint
npm run fix-lint && npm run lint # only if lint failed
npm run build # distribution build; CI uses npm
bun run dev # local dev onlyPrettier: printWidth: 120, singleQuote: false. ESLint: @raycast/eslint-config.
Package Management
- Local dev:
bun install,bun run <script> - CI/store validation:
npm run lint,npm run build
Project Structure
src/
├── <command>.tsx
├── components/
├── hooks/
├── lib/
└── types/One command file per package.json commands entry. Extract testable logic to lib/.
Vitest optional; manual test via bun run dev.
Code patterns
getPreferenceValues<Preferences.<Command>>()— never manualPreferencesinterfacestrash()for user file deletion;fs/promisesonly (no sync fs, no AppleScript)execFilewith arg arrays — no shell string interpolation for paths
Constraints
- Max 12 keywords; MIT license; US English UI strings
- Max filename length 255 (macOS)
Store readiness checklist
Verify before asking to open a PR (full workflow in pr-raycast).
package.json
- Fields:
name,title,description,icon,author,platforms,categories,license: MIT - Scripts:
build,dev,lint,fix-lint,publish(npx @raycast/api@latest publish) - Command titles: Title Case (Apple Style Guide)
package-lock.jsoncommitted; no bun/yarn/pnpm lockfiles
Assets
Icon (guide, Icon Maker)
- 512×512 PNG in
assets/; readable on light and dark UI; not default Raycast icon
Screenshots (specs)
metadata/{extension-name}-{N}.png, 2000×1250 PNG, max 6 (≥3 recommended)- Window Capture + Save to Metadata in dev mode; one theme; no sensitive data
Docs
CHANGELOG.md: top entry uses{PR_MERGE_DATE}; accurate features onlyREADME.md: required if setup needed; README media inmedia/, notmetadata/
Contributing to extensions you don't own
Add yourself to contributors in package.json; update CHANGELOG.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

