Cline rules for Nuxt

# Cline and Roo rules

Project rules for Cline and Roo Code in this Nuxt repository.
Use the project's commands. Do not invent a package manager, and do not run destructive shell commands.

## Tool use

- Read the files you will change before editing them.
- Prefer a focused patch over rewriting a whole file.
- Run the test command from this file after a behavior change, or say why you could not.
- Do not delete generated folders, lockfiles, or migrations unless the task says so.

## Stack

This repository is a Nuxt 3 app. Data for a page comes from useAsyncData or a server route. Auto-imports match the project. Do not add a second meta-framework.

## Layout

- Pages live in `pages/` or the app directory the project uses. Components live in `components/`.
- Server routes live in `server/api`. Server-only utilities live in `server/utils`.
- Do not import server code into a Vue component.

## Commands

- Dev server: `npm run dev`
- Build: `npm run build`
- Typecheck: `npm run typecheck`

Use the script the repo already defines when it differs from the command above.

## Conventions

- Load page data with `useAsyncData` or `useFetch` against a server route.
- Mutations go through server routes. Validate the body there.
- Respect the project's auto-import style. Do not mix a manual import convention in one file.
- Use `<script setup>` and the Composition API.
- Runtime config splits public and private keys the way nuxt.config already does.
- Match the UI library already installed.

## Testing

Add or update tests when behavior changes.

Test the server route handler or a pure composable. Cover one bad payload.

## Style

- Optimize for the next reader over the shortest diff.
- Comment only when the why is non-obvious.
- Name things the way neighboring files already do.
- Do not reformat code you did not change.

## Errors

- Fail at the boundary. Do not swallow errors.
- Throw a createError with a status code for expected failures so the error page can render.

## Scope

- Do the requested task. Do not refactor unrelated code.
- Match the rigor already in the repo. Fix what you touch.
- Ask one clarifying question only when the task cannot be finished without it. Otherwise state the assumption and continue.

## Avoid

- Do not fetch in `onMounted` for data the server can load.
- Do not read a private runtime config key in a component.
- Do not disable SSR to dodge a window access bug.
- Do not add Pinia if the page can keep local state.

## Done when

- The requested behavior works.
- `npm run build` succeeds and the page loads with JavaScript disabled if it is a content page.
- The diff stays inside the task.
- You list anything you could not run.