llms.txt is an open proposal for a short Markdown file that lists a project's key docs and links, so AI tools can find them without crawling every page.

Where should llms.txt be deployed?

At /llms.txt on your documentation site, or in your repository root. Tools read it when they fetch it; nothing loads it automatically.

# Vue 3 & Nuxt 4 Composition API Specialist

> Modern Vue 3 and Nuxt 4 fullstack standards. Enforces <script setup lang='ts'>, the app/ directory, useFetch, and Nitro server endpoints.

## Quick Reference

- **Framework**: Vue 3 & Nuxt 4

- **Language**: TypeScript

- **Styling & UI**: Tailwind CSS

- **Database / Persistence**: Nitro / REST / Supabase

- **Architectural Philosophy**: modern

## Core Architectural Invariants

- **Feature-Colocated Structure**: Group components, hooks, tests, and utils inside domain feature folders.

- **Guard Clauses & Early Returns**: Exit early from functions to eliminate deeply nested if-else pyramids.

- **Accessible UI by Default**: Enforce semantic HTML, keyboard navigability, and proper ARIA roles.

## Operational Guardrails & Prohibited Patterns

- **Inspect Before Acting**: Always read and understand existing code and imports before suggesting changes.

- **Minimal Surgical Diffs**: Touch only lines relevant to prompt. Preserve existing comments and formatting.

- **Concise & Direct Tone**: Skip conversational pleasantries. Deliver focused diffs and a short rationale.

## Mandatory Project Directives

- Rely on Nuxt auto-imports; avoid manual import statements for standard composables.

- Use TypeScript interfaces for all component defineProps and defineEmits.

## Implementation Reference

### Preferred Patterns

```typescript

interface Props {

title: string;

}

const props = defineProps<Props>();

const { data: posts, status } = await useFetch('/api/posts');

</script>

```

### Discouraged Anti-Patterns

```typescript

// Discouraged: Options API with manual data/methods

export default {

props: ['title'],

data() { return { posts: [] }; },

mounted() { fetch('/api/posts').then(r => r.json()).then(d => this.posts = d); }

};

```

## Verification Commands & Workflows

1. Always use <script setup lang="ts">; ban legacy Vue 2 Options API syntax.

2. Keep application code in app/ (Nuxt 4's default): pages, components, composables, layouts. server/ and shared/ stay at the project root.

3. Fetch data via useAsyncData or useFetch with declarative keys; components using the same key share the same data.

4. Colocate server API handlers in server/api/ using defineEventHandler.

5. Manage global client state using Pinia stores.

## Context Documents & Specs

- [System Architecture](ARCHITECTURE.md): Authoritative system design, data flows, and state machine invariants.

- [AI Multi-Agent Spec](AGENTS.md): Universal specification for autonomous coding agent operations.

Frontend · Any LLM tool that fetches it

Vue 3 & Nuxt 4 llms.txt

An llms.txt for a Vue 3 & Nuxt 4 project: a short Markdown map of what it is and where the key docs and code live.

Path: llms.txt
Loads: Fetched on request
Format: Markdown index (.txt)
Used by: Any LLM tool that fetches it

All llms.txt presets and how llms.txt works

What this file tells the agent

An llms.txt gives language models and agents a short Markdown map of your Vue 3 & Nuxt 4 project: what it is and where the key docs and code live, so a tool that fetches it can go straight to the right files.

Always use `<script setup lang='ts'>` and the Composition API; ban legacy Options API.
Use `useFetch` or `useAsyncData` for server-side data fetching with unique cache keys.
Colocate server endpoints under `server/api/` with `defineEventHandler`.
Rely on Nuxt auto-imports; avoid manual import statements for standard Vue and Nuxt composables.

Install it in one command

01
Go to your project root
The file goes at llms.txt, relative to the root.
02
Download the file
Run the command on the right. It downloads this preset and writes the file.
03
Make sure it gets used
Nothing loads llms.txt automatically. Serve it at your site root, or point agents to it from CLAUDE.md or AGENTS.md.

$ curl -fsSL "https://www.devscratchpad.tech/api/raw/llms-txt/vue-nuxt" -o "llms.txt"

writes llms.txt

path

llms.txt

To write the file from your own code instead, use Read your code or Convert Legacy Rules in the editor above.

More for Vue 3 & Nuxt 4

Other formats

Other llms.txt presets

Questions

What is llms.txt?: llms.txt is an open proposal for a short Markdown file that lists a project's key docs and links, so AI tools can find them without crawling every page.
Where should llms.txt be deployed?: At /llms.txt on your documentation site, or in your repository root. Tools read it when they fetch it; nothing loads it automatically.

Target Standard & File Format

Identity & Activation Rules

Technology Stack Context

Engineering Philosophy

Architectural & Code Quality Conventions

Agent Behavioral Guardrails

Step-by-Step Workflow Procedures

Target File Location