Skip to content

Add an AGENTS.md#4246

Open
ewels wants to merge 3 commits into
mainfrom
agents-md
Open

Add an AGENTS.md#4246
ewels wants to merge 3 commits into
mainfrom
agents-md

Conversation

@ewels

@ewels ewels commented Jun 8, 2026

Copy link
Copy Markdown
Member

Minimal AGENTS.md, added after asking Claude to debug phantom CORS errors. Hopefully helps sessions get going a bit faster.

@ewels ewels requested a review from mashehu June 8, 2026 07:16
@netlify

netlify Bot commented Jun 8, 2026

Copy link
Copy Markdown

Deploy Preview for nf-core-main-site ready!

Name Link
🔨 Latest commit f152a3c
🔍 Latest deploy log https://app.netlify.com/projects/nf-core-main-site/deploys/6a26959008524b0009e06739
😎 Deploy Preview https://deploy-preview-4246--nf-core-main-site.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot deleted a comment from netlify Bot Jun 8, 2026

@mashehu mashehu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can't we just symlink this to contributing.md? All this information is there already and we don't need to remember to keep things in sync

@ewels

ewels commented Jun 8, 2026

Copy link
Copy Markdown
Member Author

You mean .github/CONTRIBUTING.md? The two files look very different to me?

That file is mostly about how to add yourself to the list of contributors, and how to fork the repo and make PRs. None of that is relevant to an LLM that will already be checked out on a branch with a task to do (actually it'll make its performance actively worse).

It doesn't include any information about the build architecture, testing, Astro setup etc (arguably most Human contributors don't need to know any of this, as they can just edit a markdown file and see the deployment preview).

@ewels

ewels commented Jun 8, 2026

Copy link
Copy Markdown
Member Author

Side note: playing around with how to get Claude to read AGENTS.md - the cleanest I can figure out is to add .claude to .gitignore and then have the following file in there:

.claude/CLAUDE.md

@../AGENTS.md

I think this should get Claude to automatically read AGENTS.md without cluttering up the repo for folks using other LLMs.

@mashehu

mashehu commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Ah, sorry, was thinking of the wrong repo. For the website the readme has the same instructions as the agents.md

@ewels

ewels commented Jun 8, 2026

Copy link
Copy Markdown
Member Author

That's closer, but it still doesn't mention tests etc. and is 300+ lines instead of 30. Also it's not automatically loaded into context like this file.

This isn't that much to keep updated is it?

Would be a good addition to this file to say read the README.md for instructions on adding events / advisories etc..

Comment thread AGENTS.md

This file provides guidance to AI coding agents (Claude Code and others) when working with code in this repository.

The source for **https://nf-co.re** — the nf-core community website. Built with **Astro** (static site generation), **Svelte** (interactive components) and **Bootstrap** (CSS), managed as **npm workspaces** with **Node 22**.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The source for **https://nf-co.re** — the nf-core community website. Built with **Astro** (static site generation), **Svelte** (interactive components) and **Bootstrap** (CSS), managed as **npm workspaces** with **Node 22**.
The source for **https://nf-co.re** — the nf-core community website. Built with **Astro 6** (static site generation), **Svelte 5** (interactive components) and **Bootstrap 5.3** (CSS), managed as **npm workspaces** with **Node 22**.

if you mention one version, we should mention all, especially because in my experience it keeps producing outdated syntax for svelte. pain to keep updated though

Comment thread AGENTS.md

Tests are **Playwright** (`npm run test --workspace sites/<name>`, or `npx playwright test <file>` within a sub-site for a single test).

**GitHub token:** the data-driven sub-sites (`pipelines`, `pipeline-results`, `configs`, `modules-subworkflows`, `stickers`) hit the GitHub API during the build. Add a `.env` at the repo root with a `GITHUB_TOKEN` (a personal access token with `public_repo` scope) to avoid rate limits.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't think it can add a correct github_token automatically...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants