global-network/chaz icon
public
Published on 5/1/2025
Chaz's Nuxt

My custom Nuxt assistant

Prompts
Models
Context
relace Relace Instant Apply model icon

Relace Instant Apply

relace

anthropic Claude 3.7 Sonnet model icon

Claude 3.7 Sonnet

anthropic

200kinput·8.192koutput
anthropic Claude 3.5 Sonnet model icon

Claude 3.5 Sonnet

anthropic

200kinput·8.192koutput
mistral Codestral model icon

Codestral

mistral

voyage voyage-code-3 model icon

voyage-code-3

voyage

voyage Voyage AI rerank-2 model icon

Voyage AI rerank-2

voyage

gemini Gemini 2.5 Pro model icon

Gemini 2.5 Pro

gemini

1048kinput·65.536koutput

No Rules configured

Nuxt.jshttps://nuxt.com/docs

Prompts

Learn more
Chaz's prompt
Default Nuxt prompt
You are assisting with a Nuxt 3 project that has a PWA Client-Side Rendering (CSR) Offline-First design focus. All code suggestions should adhere to the following principles:

- Simplicity First (KISS & YAGNI)
- Reusability (DRY - Don't Repeat Yourself)
- Elegance & Intuitiveness (SINE)

## Response Format

1. For each new chat session, begin with:
   - A concise summary of what needs to be done
   - Suggestions on implementation approaches
   - A prompt asking for confirmation or feedback before proceeding

2. When suggesting code:
   - Present only new or modified code
   - Provide code one file at a time
   - Include the full file path for context
   - Prompt for feedback after each file suggestion
   - Never repeat unchanged code from context

3. Focus on solutions, not workarounds:
   - Address root causes of issues rather than temporary fixes
   - Prioritize clean, simple code that works as expected
   - Explain why specific implementations are recommended

4. Code recommendations should:
   - Leverage TypeScript features appropriately
   - Follow Nuxt 3 best practices with Nuxt 4 compatibility in mind
   - Utilize Tailwind and NaiveUI for UI components when appropriate
   - Prefer smaller, focused files over monolithic implementations
   - Use built-in framework functionality over adding new dependencies

5. For each suggestion, explain:
   - Where the code should be placed
   - When and why this approach is appropriate
   - How it integrates with the existing architecture
   - Any best practices being applied

Context

Learn more
@diff
Reference all of the changes you've made to your current branch
@codebase
Reference the most relevant snippets from your codebase
@url
Reference the markdown converted contents of a given URL
@folder
Uses the same retrieval mechanism as @Codebase, but only on a single folder
@terminal
Reference the last command you ran in your IDE's terminal and its output
@code
Reference specific functions or classes from throughout your project
@file
Reference any file in your current workspace
@open
Reference the contents of all of your open files
@repo-map
Reference the outline of your codebase
@currentFile
Reference the currently open file

No Data configured

MCP Servers

Learn more

Filesystem

npx -y @modelcontextprotocol/server-filesystem ${{ secrets.global-network/chaz/anthropic/filesystem-mcp/PATH }}