Skip to content

EvoCoder – Audit Agents.md vs Repo, reconcile mismatches, integrate /codex/ usage #1536

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
punk6529 wants to merge 2 commits into from
Closed

EvoCoder – Audit Agents.md vs Repo, reconcile mismatches, integrate /codex/ usage #1536

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5808159
EvoCoder iteration 1
Oct 13, 2025
f1ed86c
EvoCoder iteration 2
Oct 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# AGENTS.md – Codex Configuration for Next.js Frontend

## Codex Workflow

- Review [codex/STATE.md](codex/STATE.md) before starting new work to confirm ticket ownership and status.
- Track every piece of work with a ticket in [codex/tickets](codex/tickets), keeping the front matter and board entry in sync as progress is made.
- Log meaningful events and decisions inside the ticket with timestamped notes; avoid editing tickets marked **Done**.
- Consult [codex/plans](codex/plans) for active planning documents and update them when sprint scope changes.
- See [codex/agents.md](codex/agents.md) for the full Codex agent contract and operational details.

## Setup

```bash
Expand Down Expand Up @@ -57,9 +65,8 @@ If `npm run test` fails due to low coverage on a modified file, write meaningful

## Next.js Directory Structure

The project supports both the classic `pages/` folder and Next.js `app/` router.
Legacy routes remain under `pages/`, while all **new** pages must be created
inside the `app/` directory.
This project now ships exclusively on the Next.js `app/` router. All routes live
inside the `app/` directory—do not introduce a legacy `pages/` tree.

Routes in `app/` should export a `generateMetadata` function using the helper
`getAppMetadata`:
Expand Down