agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/auto-ontology/frontend/CLAUDE.md

auto-ontology / frontend

CLAUDE.md9.9k starsChanged 43 days agoApache-2.0View on GitHub

Trending

More talk lately.about 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: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 64 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the NVIDIA/auto-ontology repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about NVIDIA/auto-ontology

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

See all 64

Talked about on GitHub, YouTube, Bluesky and Hacker News (64 times).

On GitHub · 27

22 more on GitHub

On YouTube · 24

19 more on YouTube

On Bluesky · 12

7 more on Bluesky

On Hacker News · 1

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    API layer: Use the requests wrapper from frontend/api/requests.ts — do not call axios directly.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
CLAUDE.md
<!-- SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 -->

@AGENTS.md

Frontend Rules

  • Next.js 16: Has breaking changes from prior versions. Read node_modules/next/dist/docs/ before writing Next.js-specific code. See frontend/AGENTS.md for details.
  • Formatting: Prettier. After editing ANY frontend file, ALWAYS run pnpm format (or cd frontend && npx prettier --write <file>) to auto-format it. Never rely on manual formatting — always let Prettier handle it. CI will reject unformatted code.
  • Linting: ESLint. Fix all lint errors; do not disable rules without a comment explaining why.
  • Components: Arrow function components. No class components.
  • Styling: Tailwind CSS 4. Do not write inline styles or separate CSS files for component styling.
  • Types: TypeScript strict mode. No any without a comment. Types go in /frontend/types, enums in /frontend/enums.
  • API layer: Use the requests wrapper from frontend/api/requests.ts — do not call axios directly. Base URL and error handling are already centralised there.

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.

Check your setup, free