agent-demos
AGENTS.md4 starsChanged 56 days agoMITView on GitHub
This repository maintains project-specific knowledge and conventions in docs/; start with docs/index.md and docs/DOCS.md, then follow links into docs/<domain>/DOCS.md, docs/<domain>/index.md, and docs/<domain>/<subdomain>.md as needed, treat docs/ as the source of durable non-obvious project practices, and use the installed $project-docs-system skill when initializing, maintaining, or updating this docs system. <!-- END:docs-system-rules -->
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 repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alertmanager-querySkill
- codebase-designSkill
- code-reviewSkill
- domain-modelingSkill
- grillingSkill
- grill-with-docsSkill
- implementSkill
- improve-codebase-architectureSkill
- investigating-with-observabilitySkill
- project-docs-systemSkill
- skill-creatorSkill
- stream-aggregation-helperSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- victorialogs-querySkill
- victoriametrics-cardinality-analysisSkill
- victoriametrics-querySkill
- victoriametrics-unused-metrics-analysisSkill
- victoriatraces-querySkill
- vm-trace-analyzerSkill
- wayfinderSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 10
Always use uv CLI first to manage Python environments instead of manually editing Python environment config.
- Very specific: line 13
Update AGENTS.md only when the user explicitly asks.
- Distinctive: line 17
Prefer Tailwind utilities, variants, and arbitrary properties alongside the component JSX.
- Distinctive: line 18
Keep global CSS for design tokens and base styles.
≈ “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
Repository Instructions
- Tell it like it is; don't sugar-coat responses.
- 永远不要出现“不是...,而是...”句式。
- 用户通常使用语音转文字输入,文本里可能有识别错误、同音误写或漏字。处理请求时应结合上下文判断真实意图,避免机械逐字执行。
- Prefer 高内聚低耦合,高可维护性,低复杂性的代码架构。按照功能分模块,单文件-浅模块-深模块的顺序定期重构迭代。
- Prefer TDD 红绿灯,但仅对核心的 10% 代码创建测试,当作核心契约使用。
- Prefer 提前抛出错误而不是 fallback,因为抛出错误会解决而 fallback 会掩盖错误。
- 适当补充介绍用户可能的“还不知道自己不知道”的内容。
- Always use
uvCLI first to manage Python environments instead of manually editing Python environment config. - 遇到可能由于网络原因导致的报错,应该先重试一次。
- During this rapid iteration phase, use
mainas the default target branch for commits unless the user explicitly specifies otherwise. - Update
AGENTS.mdonly when the user explicitly asks; otherwise keep durable conventions in thedocs/system.
UI styling
- Prefer Tailwind utilities, variants, and arbitrary properties alongside the component JSX. Extract repeated UI structures into components instead of growing shared stylesheet files.
- Keep global CSS for design tokens and base styles. Use component-local CSS only when Tailwind cannot express the requirement clearly; document that reason beside the rule.
- Localize layout as well as text: account for each supported language's writing direction and script. Verify affected locales in the browser rather than limiting coverage to the user's examples.
<!-- BEGIN:docs-system-rules -->This is NOT the docs system you know
This repository maintains project-specific knowledge and conventions in docs/; start with docs/index.md and docs/DOCS.md, then follow links into docs/<domain>/DOCS.md, docs/<domain>/index.md, and docs/<domain>/<subdomain>.md as needed, treat docs/ as the source of durable non-obvious project practices, and use the installed $project-docs-system skill when initializing, maintaining, or updating this docs system.
<!-- END:docs-system-rules -->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.

