markeron
AGENTS.md1.2k starsChanged 5 months agoMITView on GitHub
Index for AI agents and contributors. Prefer these docs over guessing project conventions. Human-oriented setup: CONTRIBUTING.md Or before release: npm run release:check Validate pinned Node against lockfile deps: npm run check:engines
- Installs packages
Trending
Quiet since July.thin dataabout the whole repository
Who's talking about ifer47/markeron
- ScoopInstaller/Scoop“[Bug] checkver github mode not working for url ending with #/dl.7z”GitHub · Jul 14, 2026
- ScoopInstaller/Extras“[Request]: MarkerOn”GitHub · Jul 14, 2026
The biggest 2 of 2 mentions linking to the repository that our crawl found. Each line is their own headline.
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 repository9 other files it gives its agents.
- .cursor/rules/commit-conventions.mdcCursor rule
- .cursor/rules/cross-platform-ui-styles.mdcCursor rule
- .cursor/rules/i18n.mdcCursor rule
- .cursor/rules/node-toolchain.mdcCursor rule
- .cursor/rules/release-workflow.mdcCursor rule
- cross-platform-tauri-uiSkill
- grill-meSkill
- releaseSkill
- tauri-config-ipcSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 60
Do not: use Tailwind opacity classes in Vue for borders/text/backgrounds — use semantic classes in src/style.css.
- Very specific: line 61
Do not: add UI strings in only one locale — sync en.ts and zh-CN.ts.
- Distinctive: line 63
Only create git commits when the user asks.
≈ “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
Agent Guide — MarkerOn
Index for AI agents and contributors. Prefer these docs over guessing project conventions.
Quick start
nvm use # Node 24.15.0, npm 11.12.1
npm install
npm run dev # Tauri + frontendHuman-oriented setup: CONTRIBUTING.md
When to read what
| Task | Doc |
| Release / version bump / tag | .cursor/skills/release/SKILL.md + .cursor/rules/release-workflow.mdc |
| Commit message / czg / hook failures | .cursor/rules/commit-conventions.mdc |
| Vue/CSS, Mac vs Windows UI | .cursor/skills/cross-platform-tauri-ui/SKILL.md + .cursor/rules/cross-platform-ui-styles.mdc |
| Translations (en + zh-CN) | .cursor/rules/i18n.mdc |
| Settings, config.json, IPC commands | .cursor/skills/tauri-config-ipc/SKILL.md |
| Node / npm version pin | .cursor/rules/node-toolchain.mdc |
Project layout
src/ Vue 3 frontend (overlay + settings)
src-tauri/src/ Rust backend (Tauri, tray, shortcuts, config)
.cursor/rules/ Cursor rules (*.mdc)
.cursor/skills/ Cursor skills (workflows)Common commands
| Command | Purpose |
npm run dev | Dev app |
npm run build:fe | Typecheck + Vite build |
npm test | Vitest |
npm run lint / format:check | oxlint / prettier |
npm run commit | Interactive Conventional Commit |
npm run release patch | Only way to publish a version |
Pre-merge checks (match CI)
npm test && npm run lint && npm run format:check && npx vue-tsc --noEmit
cd src-tauri && cargo fmt --check && cargo clippy -- -D warnings && cargo testOr before release: npm run release:check
Validate pinned Node against lockfile deps: npm run check:engines
Agent defaults
- Do not manually bump versions or create release tags — use
npm run release. - Do not use Tailwind opacity classes in Vue for borders/text/backgrounds — use semantic classes in
src/style.css. - Do not add UI strings in only one locale — sync
en.tsandzh-CN.ts. - Do not skip commit hooks (
--no-verify) unless the user explicitly requests it. - Only create git commits when the user asks.
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.

