agentleFS
ifer47ifer47/markeron/AGENTS.md

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

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the ifer47/markeron repository that our weekly crawl found: only 2 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about ifer47/markeron

The biggest 2 of 2 mentions linking to the repository that our crawl found. Each line is their own headline.

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
  1. Very specific:

    Do not: use Tailwind opacity classes in Vue for borders/text/backgrounds — use semantic classes in src/style.css.

    line 60
  2. Very specific:

    Do not: add UI strings in only one locale — sync en.ts and zh-CN.ts.

    line 61
  3. Distinctive:

    Only create git commits when the user asks.

    line 63

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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 + frontend

Human-oriented setup: CONTRIBUTING.md

When to read what

TaskDoc
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

CommandPurpose
npm run devDev app
npm run build:feTypecheck + Vite build
npm testVitest
npm run lint / format:checkoxlint / prettier
npm run commitInteractive Conventional Commit
npm run release patchOnly 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 test

Or 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.ts and zh-CN.ts.
  • Do not skip commit hooks (--no-verify) unless the user explicitly requests it.
  • Only create git commits when the user asks.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.