portal / frontend
AGENTS.md293 starsChanged 3 months agoMITView on GitHub
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Do not add useCallback; React Compiler handles memoization.
- Very specific: line 18
Only handleBPSChange uses optimistic update with rollback.
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Frontend AGENTS.md
Frontend-Backend Contracts
- Browser requests use the Go relay API directly through same-origin
/api/*,/sdk/*, and/discovery*paths. - Relay path constants are owned by
../types/paths.goand mirrored insrc/lib/apiPaths.ts. - JSON control-plane responses use the
{ ok, data?, error?: { code, message } }envelope. - Admin auth uses bearer tokens returned by
/api/admin/auth/login;src/lib/apiClient.tsattaches them to admin and policy requests. VITE_PORTAL_API_BASE_URLis the only built-in API origin setting. Leave it empty for same-origin deployment.- Lease and policy wire fields use snake_case. Go types in
../types/own the contract mirrored bysrc/types/api.ts. - Lease metadata parsing and UI defaults are owned by
src/lib/metadata.ts. - Landing-page visibility comes from
landing_page_enabledin the Go relay public and policy state.
Frontend Conventions
- Do not add
useCallback; React Compiler handles memoization. - Feature state lives in page-level hooks and is prop-drilled. Theme is the exception.
- Only
handleBPSChangeuses optimistic update with rollback. Other admin actions await the API and refresh state.
Other versions1 project uses a version of this.
Word for word · 1
- gosuda/portal-tunnel★ 293100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

