/init

touch AGENTS.md

# AGENTS.md

## Commands
- Install: `pnpm install`
- Dev: `pnpm dev`
- Lint: `pnpm lint`
- Typecheck: `pnpm typecheck`
- Test: `pnpm test`

## Working rules
- Keep changes focused on the requested task.
- Do not add production dependencies without approval.
- Do not edit generated files.
- Run the smallest relevant test before reporting completion.

~/.codex

~/.codex/AGENTS.override.md

~/.codex/AGENTS.md

repo/
├── AGENTS.md
├── apps/
│   ├── web/
│   │   └── AGENTS.md
│   └── mobile/
│       └── AGENTS.override.md
└── packages/

# ~/.codex/AGENTS.md

## Personal working agreements
- Prefer concise implementation summaries.
- Ask before adding production dependencies.
- Do not run destructive Git commands.
- Report commands that were actually executed.
- Mark unverified claims explicitly.

mkdir -p ~/.codex
$EDITOR ~/.codex/AGENTS.md

codex --ask-for-approval never "Summarize the current instructions."

# Repository guidance

## Project overview
- This is a Nuxt 3 content website.
- Main app: `apps/web`.
- Shared UI: `packages/ui`.

## Commands
- Install: `pnpm install`
- Dev: `pnpm --filter web dev`
- Lint: `pnpm lint`
- Typecheck: `pnpm typecheck`
- Unit tests: `pnpm test`
- E2E: `pnpm test:e2e`

## Architecture
- Route pages belong in `apps/web/pages`.
- Reusable business logic belongs in `apps/web/composables`.
- Generic UI belongs in `packages/ui`.

## Code style
- Use TypeScript strict mode.
- Prefer named exports for shared utilities.
- Keep public functions documented.

## Constraints
- Do not edit generated files in `.nuxt/` or `dist/`.
- Do not change public API response shapes without approval.
- Do not add dependencies when an existing utility is sufficient.

## Verification
- Run focused tests during implementation.
- Before completion run lint and typecheck for changed packages.
- Report any checks that could not run.

repo/
├── AGENTS.md
├── app/
│   └── AGENTS.md
└── server/
    └── AGENTS.md

## Flutter app rules
- Use Riverpod for new state management.
- Use go_router for navigation.
- Run `flutter analyze` after Dart changes.
- Run the nearest widget/unit tests.
- Do not modify generated `*.g.dart` files directly.

## Server rules
- Use Spring Boot conventions already present in the module.
- Keep controllers thin; business logic belongs in services.
- Run `./gradlew test` for affected modules.
- Database changes require a migration and rollback notes.

# services/payments/AGENTS.override.md

## Payments rules
- Never change idempotency behavior without a regression test.
- Do not rotate or print secrets.
- Use `make test-payments` instead of the repository-wide test command.
- Any schema migration must include a rollback plan.

- Run `pnpm test -- auth` after changing authentication code.

- Authentication is a process by which a system identifies a user...

- Before changing the payment state machine, read `docs/payments/state-machine.md`.

## Common mistakes to avoid
- The repository uses pnpm, not npm or yarn.
- `src/api/generated` is generated; edit the OpenAPI source instead.
- Do not run the full E2E suite during small UI iterations; run the focused spec first.

- Run tests before completion.

- Unit tests: `pnpm test`
- Focused test: `pnpm vitest run path/to/file.test.ts`
- Typecheck: `pnpm typecheck`

# AGENTS.md

## Repository layout
- `apps/web`: customer-facing Nuxt app
- `apps/admin`: internal React app
- `services/api`: FastAPI service
- `packages/ui`: shared design system

## Package manager
- Use `pnpm` only.
- Run commands from repository root unless a section says otherwise.

## Scope
- Avoid cross-package changes unless required by the task.
- If changing a shared package, identify all affected consumers.

## Verification
- Web: `pnpm --filter web test`
- Admin: `pnpm --filter admin test`
- API: `uv run pytest`
- Shared typecheck: `pnpm typecheck`

## Generated content
- Do not edit `openapi/generated` or `*.g.dart` directly.

# services/api/AGENTS.md

- Use `uv` for Python dependencies.
- Keep endpoints thin and put domain logic in `app/services`.
- New endpoints require schema tests and authorization tests.

codex --cd services/api --ask-for-approval never \
  "List the instruction sources you loaded and summarize the effective rules."