docs: reframe agent guidance#628
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 20e7f10f97
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## Adding a New Page | ||
| - `src/pages/` - Vocs file-based routes | ||
| - `src/pages/docs/` - main docs site | ||
| - `src/pages/protocol/tips/` - TIP pages read by `TipsList` |
There was a problem hiding this comment.
This newly added Project Structure entry points agents at src/pages/protocol/tips/, but the TIP files in this repo live under src/pages/docs/protocol/tips/, and TipsList imports only ../pages/docs/protocol/tips/tip-*.mdx (src/components/TipsList.tsx:4). Following this guidance to add a TIP would create it in an un-routed, un-globbed directory, so it would not appear on /docs/protocol/tips.
Useful? React with 👍 / 👎.
1 participant
Motivation
AGENTS.mdwas very stale and needed clearer guidance for agents updating Tempo docs.Updating this to be much more like mpp.dev's agents.md which has scaled pretty well