# AGENTS.md Template For Split Frontend Repo

## Repo role
- This repo owns the storefront and admin UI surface.
- It consumes backend contracts from the paired backend repo.

## Frontend scope
- Storefront routes, account routes when needed, and admin routes or admin app.
- Design system, responsive rules, motion rules, and accessibility baseline.

## Data contract rules
- Do not invent backend fields without documenting the contract.
- Keep request and response assumptions aligned with the backend repo.

## Asset workflow
- Define source imagery, placeholder policy, and external generation prompt policy.

## Delivery rules
- Keep mobile storefront quality high.
- Keep admin workflows efficient and reliable.