> ## Documentation Index
> Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure project instructions

> Customize agent behavior with an AGENTS.md file.

Use project instructions when Veryfront Agent needs project-specific rules.

Veryfront Agent already understands Veryfront. Use `AGENTS.md` for local commands, architecture rules, naming conventions, release constraints, and product context.

Do not put secrets or credentials in `AGENTS.md`.

## Add instructions

In your project root, create `AGENTS.md`:

```md title="AGENTS.md" theme={null}
# Project instructions

## Code style

- Use TypeScript for new code.
- Match existing file and component patterns.
- Keep user-facing copy short and direct.

## Commands

- Run tests before opening a pull request.
- Run the project lint command after changing shared code.

## Architecture

- Keep route code separate from shared library code.
- Put reusable UI in the existing component directories.
- Do not add dependencies without approval.
```

## Keep instructions specific

| Include                           | Avoid                               |
| --------------------------------- | ----------------------------------- |
| Test and lint commands            | General TypeScript or React lessons |
| Naming and folder conventions     | Veryfront framework basics          |
| Deployment or release constraints | Secrets or credentials              |
| Product-specific rules            | Long process documents              |
| Known architecture boundaries     | Temporary notes that expire quickly |

## Make rules actionable

| Weak                      | Better                                                                |
| ------------------------- | --------------------------------------------------------------------- |
| Write good tests.         | Run `npm test` after changing shared logic.                           |
| Follow the design system. | Use components from `components/ui/` before adding new UI primitives. |
| Be careful with auth.     | Do not change auth middleware without updating `tests/auth.test.ts`.  |
| Keep copy concise.        | Keep user-facing copy under two sentences per state.                  |

## Check the result

Ask Veryfront Agent to summarize the active project instructions:

```text theme={null}
Summarize the project instructions you are following.
```

If it misses a rule, make the rule shorter and more direct.

## Update instructions

Review `AGENTS.md` after major project changes.

Update it when commands, deployment targets, folder ownership, or product constraints change.

## What to include

| Situation              | Add this                                    |
| ---------------------- | ------------------------------------------- |
| New test command       | The exact command and when to run it.       |
| New folder convention  | The owning folder and what belongs there.   |
| New release rule       | The release target and required validation. |
| New product constraint | The rule and an example of when it applies. |

## Next

| Goal                     | Page                      |
| ------------------------ | ------------------------- |
| Add reusable workflows   | [Skills](/docs/agent/skills)   |
| Understand Agent context | [Veryfront Agent](/docs/agent) |