agentleFS
laude-institutelaude-institute/harbor/docs/AGENTS.md

harbor

AGENTS.md6.7k starsChanged 24 days agoApache-2.0View on GitHub

This directory contains the Next.js landing page deployed at https://harborframework.com. Documentation is maintained in ../docs-mintlify and deployed at https://docs.harborframework.com. Use Bun for this application: - src/app/(home)/ owns the homepage and its components. - src/app/layout.tsx owns the root layout, metadata, fonts, and providers. - src/app/global.css contains Tailwind CSS and shared Fumadocs styling. - src/lib/layout.shared.tsx owns navigation options. - src/components/ contains shared UI components. - public/ contains website assets. - Use strict TypeScript and the @/* alias for src/*. - Use cn()…

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

7 rules. About 0 are common, 2 are distinctive, and 5 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.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use Bun for this application:

    line 9
  2. Very specific:

    Use strict TypeScript and the @/* alias for src/*.

    line 27
  3. Very specific:

    Use cn() from src/lib/utils.ts to combine conditional classes.

    line 28
  4. Distinctive:

    Search is disabled because documentation search belongs to Mintlify.

    line 31
  5. Very specific:

    Do not edit generated .next/, node_modules/, or next-env.d.ts files.

    line 32
  6. Very specific:

    Keep the permanent redirects in next.config.mjs:

    line 36
  7. Very specific:

    Keep specific legacy redirects before the /docs/:path* fallback.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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

Harbor website

This directory contains the Next.js landing page deployed at https://harborframework.com. Documentation is maintained in ../docs-mintlify and deployed at https://docs.harborframework.com.

Development

Use Bun for this application:

bun install
bun dev
bun run build
bun start
bun lint

Structure and conventions

  • src/app/(home)/ owns the homepage and its components.
  • src/app/layout.tsx owns the root layout, metadata, fonts, and providers.
  • src/app/global.css contains Tailwind CSS and shared Fumadocs styling.
  • src/lib/layout.shared.tsx owns navigation options.
  • src/components/ contains shared UI components.
  • public/ contains website assets.
  • Use strict TypeScript and the @/* alias for src/*.
  • Use cn() from src/lib/utils.ts to combine conditional classes.
  • Preserve the homepage's Fumadocs UI and core dependencies; they provide layout, theme support, styling, and code blocks. Fumadocs MDX is no longer used.
  • Search is disabled because documentation search belongs to Mintlify.
  • Do not edit generated .next/, node_modules/, or next-env.d.ts files.

Redirects

Keep the permanent redirects in next.config.mjs:

  • Known /docs/ pages and historical aliases go directly to their corresponding Mintlify pages. Guides without a current equivalent go to their final pre-removal revision on GitHub.
  • /docs/:path* sends unknown paths to the Mintlify documentation homepage.
  • Keep specific legacy redirects before the /docs/:path* fallback.
  • /news/:path* goes to the corresponding Mintlify news path.
  • /llms-full.txt goes to Mintlify's text export.
  • /registry and /registry/:path* go to Harbor Hub.

The docs/ directory remains the website's deployment root. Add documentation pages to docs-mintlify/, not this application.

Download now (ZIP)

Trending

Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 1 new projectWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Who's talking about laude-institute/harbor

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

See all 38

Talked about on GitHub and Hacker News (38 times).

On GitHub · 37

32 more on GitHub
  • Other versions1 project uses a version of this.

    Word for word · 1

    1. harbor-framework/harbor★ 6.2k100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • 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 28,693 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 repository7 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.