agentleFS
Sign inStart free
danishashkodanishashko/geo-aeo-tracker/.github/copilot-instructions.md

geo-aeo-tracker

Copilot instructions328 starsChanged 28 days agoMITView on GitHub

Read AGENTS.md at the repo root first. It covers setup, environment variables, the API route map, rate limits, conventions and gotchas for this Next.js 16 / React 19 / TypeScript project. Five rules that matter most:

The file

We split this copilot-instructions.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:

    Read AGENTS.md at the repo root first.

    line 3

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions 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
copilot-instructions.md

Copilot instructions

Read AGENTS.md at the repo root first. It covers setup, environment variables, the API route map, rate limits, conventions and gotchas for this Next.js 16 / React 19 / TypeScript project.

Five rules that matter most:

  1. Commands: npm run dev, npm run build, npm run lint, npm test, and npx tsc --noEmit for a type check. Every environment variable is optional.
  2. Tests run with npm test (node:test through tsx, files in lib/**/*.test.ts and tests/**/*.test.mjs) and are free and offline. Also run the type check, lint and build before saying a change works.
  3. NEXT_PUBLIC_DEMO_ONLY=true (or a missing BRIGHT_DATA_KEY) shows the sample dataset. The flag is inlined at build time, so changing it needs a rebuild.
  4. Most /api/* routes call paid APIs (Bright Data, OpenRouter, Gemini) on the deployer's account. Do not run them, or npm run test:scraper, without the user's keys and consent.
  5. Next 16 uses proxy.ts for rate limiting, not middleware.ts. Validate every route body with zod and route user URLs through assertPublicHttpUrl in lib/server/ssrf.ts.

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