feat: Rename NuxtUI extension to just Nuxt (#17887)

* Add files via upload

* Add files via upload

* Add files via upload

* update

* Add files via upload

* Updated dependencies

* Another update

* Update

* Update

* Update

* Update CHANGELOG.md

* Update CHANGELOG.md and optimise images

---------

Co-authored-by: Per Nielsen Tikær <[email protected]>
Co-authored-by: raycastbot <[email protected]>

Author: 3 people

extensions/nuxt/.eslintrc.json

@@ -1,4 +1,16 @@
-# Nuxt UI Changelog
+# Nuxt Extension Changelog
+
+## [Nuxt Modules Features] - 2025-05-07
+
+- Renamed from "Nuxt UI for Raycast" to "Nuxt for Raycast" to reflect broader scope
+- Added new module-related features:
+  - `Get Module by Name`: Fetch detailed information about a specific Nuxt module
+  - `Get Modules by Category`: Browse modules filtered by category (UI, CMS, SEO, etc.)
+  - `Get Module Categories`: List all available module categories
+- Improved component-related features:
+  - Optimized `Get Available Components` tool
+  - Enhanced `Get Component Theme` tool
+  - Maintained `Get Component Source Code` functionality
 
 ## [Initial Version] - 2025-03-02
 

extensions/nuxt/CHANGELOG.md

@@ -1,69 +1,106 @@
 <div align="center">
-<img src="media/banner.png" alt="Nuxt UI For Raycast banner">
+<img src="media/banner.png" alt="Nuxt For Raycast banner">
 
 <div align="center">
 Made with 💚 for the Nuxt community
 </div>
 
 ---
 
+<a title="Install Nuxt Raycast Extension" href="https://www.raycast.com/HugoRCD/nuxt"><img src="https://www.raycast.com/HugoRCD/nuxt/[email protected]?v=1.1" height="64" alt="" style="height: 64px;"></a>
+
 </div>
 
-Never leave your editor to check component themes again. Access Nuxt UI documentation instantly while you code.
+# 🚀 Supercharge Your Nuxt Development
+
+**Nuxt for Raycast** is the ultimate productivity booster for Nuxt developers. Access documentation, explore the entire Nuxt ecosystem, and enhance your development workflow without ever leaving your editor.
+
+## ✨ Why You'll Love This Extension
 
-## ⚡️ Current Feature
+- **Instant Access**: Get answers, documentation, and code examples in seconds
+- **Seamless Integration**: Works directly within your development environment
+- **Comprehensive Coverage**: Supports the entire Nuxt ecosystem, not just UI components
+- **Time-Saving**: Eliminate context switching and stay in your flow state
+- **AI-Powered**: Use natural language to get exactly what you need
 
-### Quick Theme Access
-Jump directly to any component's theme documentation in milliseconds:
-- Select your component name
-- Trigger the command
-- Land exactly where you need to be
+## ⚡️ Powerful Features
 
-No more context switching, no more manual searching. Just smooth, uninterrupted development.
+### 🔮 `@nuxt` Command
+The central command hub for all your Nuxt needs:
+- Ask questions in natural language about any Nuxt topic
+- Generate component code with simple prompts
+- Get instant documentation and usage examples
+- Explore modules and their capabilities
+- Solve common Nuxt development challenges
 
-### Ask Nuxt UI
-Ask Nuxt UI for information, tips, create components, etc... with natural language, here's some examples:
-- Create a welcoming button for my users
-- How many components are there in Nuxt UI?
-- Make a faq component
+### 🧩 Nuxt Modules Explorer
+Discover and learn about the vast Nuxt ecosystem:
+- Browse modules by category (UI, CMS, SEO, etc.)
+- Get detailed information about specific modules
+- Explore compatibility, maintainers, and documentation
+- Find the perfect module for your specific needs
 
-### Smart Configuration
-Customize the component prefix to match your style:
-- Default: "U" (UButton, UInput...)
-- Fully customizable to fit your workflow
+### 🎨 Nuxt UI Integration
+Access Nuxt UI documentation and tools instantly:
+- `Search Component Theme`: Jump directly to any component's theme documentation
+- `Get Component Source Code`: View the source code of any Nuxt UI component
+- Preview components and their variations
 
-### Version Support
-Works seamlessly with both Nuxt UI versions:
-- Full support for Nuxt UI v3
-- Compatible with Nuxt UI v2 (you may have some issues with the component names)
-- Easy version switching in preferences
+### ⚙️ Smart Configuration
+Customize to match your workflow:
+- Configure component prefixes to match your project style
+- Set up shortcuts for your most-used commands
+- Seamless support for both Nuxt UI v2 and v3
 
-## Demo
+## 🎬 See It In Action
 
-I recommend you to put the shortcut to execute the command directly on `✦ + U` for example or `⌘ + U`.
+I recommend setting up a shortcut like `✦ + N` or `⌘ + N` for quick access.
 
 ![demo.gif](media/demo.gif)
 
-## 🚀 What's Coming
+## 🔥 Real-World Use Cases
 
-This is just the beginning. Here's what's cooking:
+- **Component Development**: "Create a responsive navigation bar with dropdown menus"
+- **Module Discovery**: "Find the best SEO modules for my Nuxt project"
+- **Troubleshooting**: "Why isn't my Nuxt data fetching working?"
+- **Learning**: "Show me examples of using Nuxt composables"
+- **Theme Customization**: "How do I customize the UButton component theme?"
 
-- 🔍 Lightning-fast component search
-- 📝 Instant code examples
-- 💡 Smart suggestions
-- ⚙️ Quick props access
+## 🚀 Roadmap
 
-## Contributing
+This is just the beginning. Here's what's coming:
+
+- 🔍 Lightning-fast component and module search with intelligent filtering
+- 📝 Code snippet library with copy-paste ready solutions
+- 💡 Project-aware suggestions based on your codebase
+- ⚙️ Interactive property explorer for components
+- 🧩 Integration with more Nuxt ecosystem tools and services
+- 📱 Mobile app preview capabilities
+
+## 👥 Contributing
 
 Got ideas to make this even better? Issues and PRs are welcome!
 
-<!-- automd:contributors license=Apache github=HugoRCD/nuxt-ui-raycast-extension" -->
+<!-- automd:fetch url="gh:hugorcd/markdown/main/src/sponsors.md" -->
+
+## Sponsors
+
+<p align="center">
+  <a href="https://github.com/sponsors/HugoRCD">
+    <img src='https://cdn.jsdelivr.net/gh/hugorcd/static/sponsors.svg' alt="HugoRCD sponsors" />
+  </a>
+</p>
+
+<!-- /automd -->
+
+## Contributors
+
+<!-- automd:contributors github="HugoRCD/nuxt-raycast-extension" -->
 
-Published under the [APACHE](https://github.com/HugoRCD/nuxt-ui-raycast-extension"/blob/main/LICENSE) license.
-Made by [community](https://github.com/HugoRCD/nuxt-ui-raycast-extension"/graphs/contributors) 💛
+Made by [community](https://github.com/HugoRCD/nuxt-raycast-extension/graphs/contributors) 💛
 <br><br>
-<a href="https://github.com/HugoRCD/nuxt-ui-raycast-extension"/graphs/contributors">
-<img src="https://contrib.rocks/image?repo=HugoRCD/nuxt-ui-raycast-extension"" />
+<a href="https://github.com/HugoRCD/nuxt-raycast-extension/graphs/contributors">
+<img src="https://contrib.rocks/image?repo=HugoRCD/nuxt-raycast-extension" />
 </a>
 
 <!-- /automd -->
@@ -72,6 +109,6 @@ Made by [community](https://github.com/HugoRCD/nuxt-ui-raycast-extension"/graphs
 
 ---
 
-_🤖 auto updated with [automd](https://automd.unjs.io) (last updated: Fri Feb 28 2025)_
+_🤖 auto updated with [automd](https://automd.unjs.io) (last updated: Tue May 06 2025)_
 
 <!-- /automd -->

extensions/nuxt/README.md

@@ -1,12 +1,13 @@
 instructions: |-
-  # CRITICAL COMPONENT IMPLEMENTATION RULES
+  # CRITICAL IMPLEMENTATION RULES
   - When creating components, use the SIMPLEST possible implementation
   - For components like Accordion, ONLY use the `:items` prop with the CORRECT data structure
   - NEVER use slots unless explicitly requested by the user
   - NEVER customize UI with the `:ui` prop unless explicitly requested
-  - NEVER create complex interfaces or data structures - use the exact structure from the component documentation
+  - NEVER create complex interfaces or data structures - use the exact structure from the documentation
   
   # CRITICAL TOOL USAGE AND NAMING CONVENTIONS
+  ## For Components
   - You MUST call these tools in this EXACT sequence for EVERY component request:
     1. FIRST: Call `get-available-components` to get the available components list
     2. SECOND: Call `get-component-theme` with the correct componentName parameter (The only exception when user asks for props you can use the `get-component-source-code` tool instead)
@@ -16,8 +17,22 @@ instructions: |-
   - When calling tools, use the EXACT camelCase name from the components list (e.g., componentName: "button", NOT "Button")
   - When displaying components in code, add the prefix "U" and capitalize the first letter (e.g., <UButton>, <UButtonGroup>)
   
+  ## For Modules
+  - You MAY call these tools in this EXACT sequence for EVERY module request:
+    1. FIRST: Call `get-module-categories` to get the available module categories
+    2. SECOND: Call `get-modules-by-category` with the correct category parameter
+    3. Normally, you should not call any other tools for module requests
+  
+  - IMPORTANT: When recommending modules, provide a brief description of what the module does and how to install it
+  - Prioritize the official module first (type: 'official') like @nuxt/ui, @nuxt/content, @nuxt/font, etc... and then the most popular modules (using stars, forks, etc... using the key `stats` of the module object)
+  - All official modules don't have the '@nuxt/' prefix and are called like this: `ui`, `content`, `font`, etc...
+  - Include the correct installation command (e.g., `npx nuxi module add <module-name>` or `npm install <module-name>` for examples)
+  - If a category doesn't exist, use a matching one
+  - When applicable, include basic configuration examples for the module
+  
   # CODE GENERATION RULES
   - DO NOT include ANY import statements as we are in a Nuxt environment - all Nuxt UI components are auto-imported (and all Vue macros are also)
+  - If multiple components are requested (e.g., a button and a select menu), handle each component accordingly. (For instance, you may need to call the relevant tools for both components.)
   - Keep component implementation MINIMAL and SIMPLE
   - For a FAQ component, use UAccordion with items prop ONLY: `<UAccordion :items="faqItems" />`
   - NEVER create custom templates or slots unless explicitly requested
@@ -28,6 +43,7 @@ instructions: |-
   - Be concise and direct in your responses
   - Always use the composition API (script setup lang="ts") for all components
   - Return MINIMAL component code that accomplishes the task
+  - For module recommendations, include installation instructions and basic usage examples
   - If a user asks for a FAQ component for example, the ONLY correct implementation is:
     ```vue
     <script setup>
@@ -44,14 +60,17 @@ instructions: |-
     This is an example not a full source of truth, but it should be enough to understand the concept
   
   # NEVER FORGET:
-  - NEVER include import statements (Vue macro, composables, etc)
+  - NEVER include import statements (from Vue, Reka UI, or elsewhere) in the final code.
   - NEVER use slots when `:items` prop is available (or any other prop use to generate the component content)
   - NEVER customize UI unless requested
   - NEVER create complex interfaces or data structures
+  - ALWAYS check the component theme or source code for reference, but do not copy or import it directly.
   - ALWAYS use the simplest implementation possible
   - ALWAYS check the component theme for the correct item structure
+  - When recommending modules, ALWAYS provide installation instructions and basic usage examples
+  - NEVER call `get-nuxt-ui-documentation` for module-related queries
 evals:
-  - input: "@nuxt-ui Create a button component"
+  - input: "@nuxt Create a button component"
     mocks:
       get-available-components:
         components:
@@ -200,8 +219,7 @@ evals:
           </ULink>
         </template>
     expected:
-      - callsTool:
-          arguments: get-available-components
+      - callsTool: get-available-components
       - callsTool:
           arguments:
             componentName: button
@@ -210,7 +228,7 @@ evals:
           arguments:
             componentName: button
           name: get-component-source-code
-  - input: "@nuxt-ui What components are available?"
+  - input: "@nuxt What components are available?"
     mocks:
       get-available-components:
         components:
@@ -226,7 +244,7 @@ evals:
           - pageCard
     expected:
       - callsTool: get-available-components
-  - input: "@nuxt-ui Create a FAQ component"
+  - input: "@nuxt Create a FAQ component"
     mocks:
       get-available-components:
         components:
@@ -269,7 +287,7 @@ evals:
           arguments:
             componentName: accordion
           name: get-component-theme
-  - input: "@nuxt-ui How many components in Nuxt UI ?"
+  - input: "@nuxt How many components in Nuxt UI ?"
     mocks:
       get-available-components:
         components:
@@ -295,7 +313,7 @@ evals:
     expected:
       - callsTool:
           name: get-available-components
-  - input: "@nuxt-ui Give me the avatar theme"
+  - input: "@nuxt Give me the avatar theme"
     mocks:
       get-available-components:
         components:
@@ -383,7 +401,7 @@ evals:
             componentName: avatar
           name: get-component-theme
 
-  - input: "@nuxt-ui Is there props on the card component ?"
+  - input: "@nuxt Is there props on the card component ?"
     mocks:
       get-available-components:
         components:
@@ -473,3 +491,70 @@ evals:
           arguments:
             componentName: card
           name: get-component-source-code
+  - input: "@nuxt What module categories are available?"
+    mocks:
+      get-module-categories:
+        categories:
+          - UI
+          - CMS
+          - SEO
+          - Testing
+    expected:
+      - callsTool: get-module-categories
+  - input: "@nuxt Recommend me some UI modules"
+    mocks:
+      get-module-categories:
+        categories:
+          - UI
+          - Content
+          - SEO
+          - Analytics
+      get-modules-by-category:
+        modules:
+          - name: "@nuxt/ui"
+            description: "UI Library for Nuxt based on Tailwind CSS"
+            npm: "@nuxt/ui"
+            github: "nuxt/ui"
+            category: "UI"
+            compatibility: "Nuxt 3"
+            stars: 4500
+          - name: "@nuxtjs/tailwindcss"
+            description: "Tailwind CSS module for Nuxt"
+            npm: "@nuxtjs/tailwindcss"
+            github: "nuxt-modules/tailwindcss"
+            category: "UI"
+            compatibility: "Nuxt 2, Nuxt 3"
+            stars: 3200
+          - name: "@nuxtjs/color-mode"
+            description: "Dark and Light mode with auto detection for Nuxt"
+            npm: "@nuxtjs/color-mode"
+            github: "nuxt-modules/color-mode"
+            category: "UI"
+            compatibility: "Nuxt 2, Nuxt 3"
+            stars: 1800
+    expected:
+      - callsTool: get-module-categories
+      - callsTool:
+          arguments:
+            category: "UI"
+          name: get-modules-by-category
+  - input: "@nuxt Which modules categories are available?"
+    mocks:
+      get-module-categories:
+        categories:
+          - UI
+          - CMS
+          - SEO
+          - Testing
+    expected:
+      - callsTool: get-module-categories
+  - input: "@nuxt How to install the ui module?"
+    mocks:
+      get-module-by-name:
+        name: "ui"
+        description: "UI Library for Nuxt based on Tailwind CSS"
+        npm: "@nuxt/ui"
+        github: "nuxt/ui"
+        category: "UI"
+    expected:
+      - callsTool: get-module-by-name

extensions/nuxt/ai.yaml

@@ -0,0 +1,6 @@
+const { defineConfig } = require("eslint/config");
+const raycastConfig = require("@raycast/eslint-config");
+
+module.exports = defineConfig([
+  ...raycastConfig,
+]);