agentleFS
palmcivetpalmcivet/awesome-arknights-endfield/AGENTS.md

awesome-arknights-endfield

AGENTS.md111 starsChanged 6 months agoMITView on GitHub

This is the full repository for Awesome Arknights: Endfield, containing: All commands must be run from the website/ directory: Project data lives in data/LIST.json — the single source of truth for the entire project. Each project entry is typed in website/shared/project.ts:

  • 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 33,315 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 repositoryOne other file it gives its agents.

The file

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

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

  • 2

    Very specific

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

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

    Search: Fuse.js (fuzzy search)

    line 14
  2. Very specific:

    All commands must be run from the website/ directory:

    line 23

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

Overview

This is the full repository for Awesome Arknights: Endfield, containing:

  1. Awesome List (repo root): Markdown-formatted community project lists (LIST.md, LIST.zh-CN.md)
  2. Website (website/ directory): A GitHub Pages showcase site with search, category filtering, and i18n support

Tech Stack

  • Framework: React 19 + TypeScript 5.9
  • Build: Vite 8 + React Compiler (via @rolldown/plugin-babel + babel-plugin-react-compiler)
  • Styling: TailwindCSS 4 (@tailwindcss/vite plugin)
  • UI Components: shadcn/ui (new-york style) + Radix UI + Lucide Icons
  • Search: Fuse.js (fuzzy search)
  • i18n: typesafe-i18n (en-US / zh-CN)
  • Validation: Zod 4
  • Package Manager: bun
  • Deployment: GitHub Pages (auto-deploy on push to main)
  • Base Path: /awesome-arknights-endfield/

Commands

All commands must be run from the website/ directory:

bun run dev              # Start dev server
bun run build            # Build (tsc -b && vite build)
bun run lint             # ESLint check
bun run format           # ESLint auto-fix
bun run generate:i18n    # Generate i18n types
bun run check:list       # Validate data/LIST.json
bun run format:list      # Format data/LIST.json
bun run generate:list    # Generate LIST.md and LIST.zh-CN.md from data/LIST.json
bun run screenshot       # Generate project screenshots

Data Source

Project data lives in data/LIST.json — the single source of truth for the entire project.

  • Imported in the website via Vite alias @data
  • Used by scripts/generate.ts to produce Markdown lists
  • Validated by scripts/check.ts

Project Data Structure

Each project entry is typed in website/shared/project.ts:

interface ProjectProps {
  name: string;
  description: Record<Language, string>;  // { "en-US": "...", "zh-CN": "..." }
  repository?: string;
  website?: Array<{ provider: string; url: string }>;
  author?: { name: string; url?: string };
  category: Category;
  tags: Array<string>;
  relatives?: Array<ProjectId>;
  license?: string;
  screenshots?: Array<string>;
}

// Auto-generated metadata
interface ProjectMeta {
  id: ProjectId;       // Auto-increment ID
  addedAt: string;     // YYYY-MM-DD format
  openSource: boolean; // Based on whether `repository` field exists
}

Vite Path Aliases

  • @ → website/
  • @data → data/
  • @assets → assets/

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.