wenlan / preview
AGENTS.md351 starsChanged 4 months agoApache-2.0View on GitHub
Browser-only harness for inspecting app UI with Tauri APIs shimmed. The root path can proxy live daemon calls; /preview/ uses fixtures for page-detail citation states. - Run with pnpm exec vite --config tooling/vite.preview.config.ts. - Use /preview/ for deterministic fixture states; use / only when a live daemon on :7878 is part of the check. - Keep fixture command responses shaped like the real Tauri wrappers consume. - Add mocks in mocks/core.ts only for commands the preview actually renders. - Preserve…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- 7xuanlu/wenlanword for word, first seen Jul 14, 2026
Other versions1 project uses a version of this.
Word for word · 1
- 7xuanlu/wenlan★ 358100% 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 32,671 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- app/AGENTS.mdAGENTS.md
- e2e/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- src/AGENTS.mdAGENTS.md
- app/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- e2e/CLAUDE.mdCLAUDE.md
- preview/CLAUDE.mdCLAUDE.md
- scripts/CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- proveSkill
- run-wenlan-appSkill
- run-wenlanSkill
- verifySkill
The file
We split this AGENTS.md into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 22
Use /preview/ for deterministic fixture states.
- Distinctive: line 24
Keep fixture command responses shaped like the real Tauri wrappers consume.
- Very specific: line 25
Add mocks in mocks/core.ts only for commands the preview actually renders.
- Distinctive: line 31
Do not let fixture data drift into product code.
- Distinctive: line 32
Do not make preview-only commands look like validated backend behavior.
- Distinctive: line 33
Do not add network calls to fixture mode.
- Distinctive: line 34
Do not ignore console warnings for unmocked invokes when adding UI surfaces.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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
AGENTS.md - preview/
OVERVIEW
Browser-only harness for inspecting app UI with Tauri APIs shimmed. The root
path can proxy live daemon calls; /preview/ uses fixtures for page-detail
citation states.
WHERE TO LOOK
| Task | Location | Notes |
| Add preview state | fixtures.ts | keep shapes aligned with src/lib/tauri.ts |
| Change preview UI | main.tsx | fixture selectors and theme toggle live here |
| Mock Tauri invoke | mocks/core.ts | fixture mode switch plus live daemon fallback |
| Live app preview | mocks/live-invoke.ts | proxies daemon calls through /daemon |
| Vite aliases | ../tooling/vite.preview.config.ts | plugin API shims and port 1421 |
CONVENTIONS
- Run with
pnpm exec vite --config tooling/vite.preview.config.ts. - Use
/preview/for deterministic fixture states; use/only when a live daemon on:7878is part of the check. - Keep fixture command responses shaped like the real Tauri wrappers consume.
- Add mocks in
mocks/core.tsonly for commands the preview actually renders. - Preserve the page-detail citation variants unless the corresponding UI states are removed from the product.
ANTI-PATTERNS
- Do not let fixture data drift into product code.
- Do not make preview-only commands look like validated backend behavior.
- Do not add network calls to fixture mode; use the live root path for that.
- Do not ignore console warnings for unmocked invokes when adding UI surfaces.
COMMANDS
pnpm exec vite --config tooling/vite.preview.config.tsDoes 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.

