# My Nuxt Blog (Nuxt 3) — Agent Notes

## Project Summary
- Nuxt 3 blog using `@nuxt/content` for Markdown articles.
- TailwindCSS for styling.
- `@nuxtjs/i18n` enabled with `zh` (default) and `en`, strategy `prefix`.

## Key Commands
- Install: `npm install`
- Dev: `npm run dev`
- Build: `npm run build`
- Preview: `npm run preview`
- Generate (SSG): `npm run generate`

## Important Files & Folders
- `nuxt.config.ts`: Nuxt modules, content + i18n configuration.
- `app.config.ts`: Blog metadata (title/description/author/language).
- `content/articles/`: Markdown posts served by `@nuxt/content`.
- `pages/`: Route pages (including dynamic post page `pages/[...slug].vue`).

## Content (Markdown)
- Articles live in `content/articles/*.md`.
- Syntax highlighting theme is configured in `nuxt.config.ts` (`github-light` / `github-dark`).
- TOC depth is configured to 3.

## i18n
- Locales: `zh-CN` and `en-US`.
- Default locale: `zh`.
- Strategy: `prefix` (URLs are prefixed with locale).
- Browser language detection uses cookie `blog_lang` and redirects on root.
- Vue I18n config is in `i18n.config.ts`.

## TypeScript
- Strict mode enabled via root `tsconfig.json` extending Nuxt-generated config.

## Working Conventions (Repo-Specific)
- Prefer Composition API with `<script setup lang="ts">` in pages/components.
- Keep changes aligned with existing Nuxt patterns; avoid introducing new libraries unless already present in `package.json`.
- Do not add secrets or API keys to the repo.