amplifier-unified / web-client
AGENTS.md5 starsChanged todayMITView on GitHub
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Read README for the current HTTP/SSE boundary, pinned upstream vision/contracts and build/test scopes. The repository is private; preserve its visibility. Unified selects a client revision and qualifies its packaged pairing; source work here does not publish or adopt a new default automatically. Author browser behavior in src/, standalone pages in public/, client checks in tests/, and build/preparation tools in scripts/.…
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 31,439 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.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- components/AGENTS.mdAGENTS.md
- amplifier-shellSkill
- appearance-authoringSkill
- coordinate-workSkill
- unified-appSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
Read README for the current HTTP/SSE boundary, pinned upstream vision/contracts and build/test scopes.
- Distinctive: line 20
Keep each assertion with its owner.
- Distinctive: line 44
Keep one explicit paired server revision in artifact evidence.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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
Working on the web client
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it.
Read README for the current HTTP/SSE boundary, pinned upstream vision/contracts and build/test scopes. The repository is private; preserve its visibility. Unified selects a client revision and qualifies its packaged pairing; source work here does not publish or adopt a new default automatically.
Author browser behavior in src/, standalone pages in public/, client checks in
tests/, and build/preparation tools in scripts/. dist/, .build-inputs/,
generated public branding/licenses and dependencies are disposable output. Do not
edit them or load them into routine source review. Change canonical catalogs,
SDK and branding with their Unified owner, then select a fresh exported lock here.
npm test owns client unit checks; test:artifact-assets checks built output.
Named browser journeys and the client registry exercise synthetic client peers;
test:artifact exercises an installed artifact. Unified owns actual host/browser,
producer, release and example checks in tests/web and assembly in scripts/.
Keep each assertion with its owner. Shared generic helper APIs retain one
implementation with injected test-framework facades, not copied implementations.
A fixture pass is not actual-server, provider, release or cross-version acceptance.
For interaction work, follow upstream CX8 and the client vision: design for ordinary information workers and consumers, with familiar labels, accessible controls and low cognitive load. UX is like golf: fewer strokes win, without losing authority, feedback or recovery.
Temporary dual-repository maintenance
While private, maintain both this canonical source and Unified's committed
components/web-client snapshot and source record. Canonical-only or copy-only
changes are not release-ready. Author here, then mechanically refresh the whole
snapshot from the exact reviewed, accepted commit, or make a named integration
handoff with exact revisions and pending work. Do not hand-edit the copy or import
unreviewed moving-main extras. Follow the README workflow;
only an explicitly approved delivery transition updating both repositories'
guidance retires this obligation, not public availability alone.
The delivery copy and prepared source (.build/web-client) are consumers, not
alternative authoring locations; preserve unknown local experiments.
Keep one explicit paired server revision in artifact evidence. Do not add a
compatibility registry, runtime asset override or automatic fallback. Follow the
workspace's owned-DTU rules for builds/browser work and remove obsolete owned
copies when their review purpose ends; preserve useful finite evidence.
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.