raycast-extensions

To build a Raycast extension, you create a new project and adapt structured templates that provide ready-to-use patterns for commands, List/Form/Grid views, and @raycast/api integrations, significantly reducing initial boilerplate and setup time.

Available patterns for Raycast extension development include ready-to-use templates for commands, List/Form/Grid views, hooks like useFetch, AI integration, and manifest-based workflows. These blueprints enforce a standard project structure and align with best practices.

Yes, you can use the useFetch hook and AI integration in your Raycast extension. The provided development patterns include ready-made blueprints for implementing hooks like useFetch and integrating AI capabilities within your React and TypeScript project.

Yes, a manifest file is required to develop a Raycast extension. The provided patterns enforce a standard extension manifest alongside a project structure that includes a SKILL.md frontmatter and optional references or assets directories for documentation.

The best way to reduce boilerplate when creating Raycast commands is to use a structured blueprint that provides ready-made patterns for commands and UI views, allowing you to adapt existing templates rather than writing @raycast/api integrations from scratch.