Generate an AGENTS.md for your next project

# AGENTS.md

## Project Overview
This project is a Frontend SPA. A software project maintained with help from AI coding agents.

Use this file as the operating guide for AI coding agents working in this repository.

## Tech Stack
- Nuxt / Vue
- TypeScript
- Tailwind CSS

## Architecture
The preferred architecture style is Feature-based.

- Respect the existing module boundaries and folder conventions before adding new structure.
- Keep related code close to the feature or layer it belongs to.
- Avoid introducing new architectural patterns unless the change clearly requires it and the user approves.
- When uncertain, inspect similar existing implementations and follow the local precedent.

## Coding Standards
Keep communication direct and focused on the change, validation, and any important tradeoffs.

- Prefer strict TypeScript and avoid weakening types for convenience.
- Keep components small, focused, and easy to scan.
- Use meaningful names for variables, functions, components, files, and database objects.
- Avoid premature abstraction; duplicate small pieces until a pattern is clear.
- Follow existing patterns before introducing new libraries, folders, or conventions.
- Use tabs for indentation and preserve existing alignment in files that already use spaces.

## Agent Workflow
- Inspect the relevant files and surrounding patterns before making changes.
- Make minimal, targeted changes that directly address the request.
- Do not rewrite, rename, or reformat unrelated code.
- Ask for explicit approval before broad architecture or data model changes.
- Update AGENTS.md when project conventions, architecture, or agent instructions change.
- Never commit secrets, tokens, credentials, or private environment values.
- Preserve existing behavior unless asked otherwise.
- Follow established naming, formatting, and folder conventions.
- Explain tradeoffs when making non-obvious decisions.

## Testing & Validation
- Add or update unit tests for business logic and pure functions.
- Run the relevant test, lint, typecheck, or build commands before the final response.
- If validation cannot be run, explain why and describe the remaining risk.

## Documentation Rules
- Update README.md when setup, commands, environment variables, or usage changes.
- Update AGENTS.md when project conventions, architecture, or agent instructions change.
- Document new public APIs, components, or non-obvious behavior.

## Extra Agent Habits
- After making changes, suggest a conventional commit message that accurately summarizes the work.
- Mention the commands run for validation and summarize the result.
- Call out meaningful risks, assumptions, or areas that need user review.

## Initial Setup Prompts
These are one-time setup prompts for agents initializing the project. Complete relevant tasks early, then remove completed items from this section so the file stays current.

- Polish the project description in this file. If the current description is vague, ask clarifying questions before rewriting it.
- Create a `CLAUDE.md` file whose content is exactly `@AGENTS.md` so Claude-based agents reuse these instructions.
- Confirm the setup, development, test, and build commands from package/config files and update documentation if they differ from this file.

## Security Rules
- Never commit secrets.
- Use environment variables for credentials.
- Validate input at boundaries.
- Avoid logging sensitive data.

## UI / UX Rules
- Keep UI accessible.
- Use semantic HTML.
- Preserve responsive behavior.
- Avoid unnecessary visual complexity.

## SEO Rules
- Keep page titles and meta descriptions meaningful.
- Use semantic headings.
- Add Open Graph and Twitter metadata where appropriate.
- Avoid client-only rendering for SEO-critical content when possible.

## Performance Rules
- Avoid unnecessary dependencies.
- Lazy-load heavy UI where useful.
- Keep bundle size in mind.
- Prefer simple solutions first.

## Git & Pull Request Guidelines
- Keep changes scoped.
- Summarize what changed.
- Mention tests run.
- Call out follow-up work separately.

## Do Not Do Without Approval
- Do not introduce major dependencies.
- Do not change architecture broadly.
- Do not remove tests.
- Do not reformat unrelated files.
- Do not alter CI/CD or deployment settings unless asked.

## Maintenance
- Revisit this file when conventions change.
- Keep instructions specific to the actual codebase.
- Remove outdated rules.