agentleFS
hamzzaqureshihamzzaqureshi/gravidex/AGENTS.md

gravidex

AGENTS.md1 starsChanged 7 days agoMITView on GitHub

These rules are automatically loaded into every conversation turn. They eliminate the need for manual slash commands by enforcing core disciplines autonomously.

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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. Distinctive:

    Standard Library First: Never introduce third-party dependencies or pip/npm packages when native platform capabilities or Python/Node …

    line 9
  2. Distinctive:

    Clean Scope: Do not reformat, rewrite, or touch unrelated functions, comments, or whitespace.

    line 10
  3. Distinctive:

    Zero Hallucinated Completion: Never declare a task, bug fix, or refactor complete until you have executed real verification tests on disk.

    line 15
  4. Very specific:

    Check Evidence: Run python3 -B test_all.py or the specific test suite.

    line 16
  5. Very specific:

    Automatic 429 Cascade: If an external API returns HTTP 429 (Rate Limited) or quota exhaustion, automatically cascade to the next configured …

    line 31
  6. Distinctive:

    Do not output emoji characters in code, documentation, test suites, terminal logs, or git commit messages.

    line 36

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

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

Autonomous Engineering Rules for Antigravity

These rules are automatically loaded into every conversation turn. They eliminate the need for manual slash commands by enforcing core disciplines autonomously.


1. Minimal Diff & YAGNI Principle (Ponytail Engine)

  • Smallest Complete Diff: Choose the solution with the fewest changed lines, fewest files touched, and zero unnecessary abstractions.
  • Standard Library First: Never introduce third-party dependencies or pip/npm packages when native platform capabilities or Python/Node standard libraries suffice.
  • Clean Scope: Do not reformat, rewrite, or touch unrelated functions, comments, or whitespace.

2. Empirical Verification Gate (Rigor Engine)

  • Zero Hallucinated Completion: Never declare a task, bug fix, or refactor complete until you have executed real verification tests on disk.
  • Check Evidence: Run python3 -B test_all.py or the specific test suite. Inspect exit codes (must be 0) and verify that all test assertions passed.
  • Log Proof: Report the exact runtime and test count in your final summary.

3. Anti-Slop Frontend & Typographic Discipline (Anti-VCode)

  • Banned Patterns: Forbid generic AI aesthetics: centered purple/cyan glow effects, gratuitous glassmorphism, floating cards without grid purpose, and generic placeholder copy.
  • Design Foundations: Enforce Swiss grid discipline, restrained motion (< 300ms, standard easing), and accessible contrast (WCAG AAA/AA).

4. Multi-Model Resilience & Automatic Failover (Model Router)

  • Task Specialization:
    • Complex algorithmic edge cases, mathematical reasoning, or race conditions: route to deepseek/deepseek-r1.
    • Fast boilerplate, bulk refactoring, and file transforms: route to qwen/qwen-2.5-coder-32b or Groq.
  • Automatic 429 Cascade: If an external API returns HTTP 429 (Rate Limited) or quota exhaustion, automatically cascade to the next configured fallback provider without halting workflow momentum.

5. Strict Emoji Ban

  • Do not output emoji characters in code, documentation, test suites, terminal logs, or git commit messages.

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.