AGENTS.md git:20260928.1e7331dA

Immutable. This exact content never changes and is served at /api/v1/blob/244957ec5167a9c6.

# AGENTS.md for Awesome-AITools

This file provides context and instructions for AI coding agents (e.g., Cursor, Aider, Claude Code, Windsurf) to help them understand this repository more effectively. It follows the [AGENTS.md](https://agents.md/) standard.

## Repository Purpose

A curated, bilingual (EN/CN) "awesome list" of AI tools — chatbots, agents, skills, CLI tools, and more. There is no application code; the repository's product is the two README files and their supporting `docs/` deep-dives.

## Key Files & Directories

- `README.md` — Main tool list (English).
- `README-CN.md` — Main tool list (Chinese).
- `docs/<tool-slug>/` — Longer-form intros for individual tools.
- `CHANGELOG.md` — Monthly log (e.g. `## June 2026`) of additions/removals/renames.
- `scripts/format_readmes.py` — Maintenance/normalization script.

## Architecture

The repo is structured as two parallel, mirrored documents that must stay in sync:

- `README.md` and `README-CN.md` share the same category structure, the same set of tools, and the same 4-column table schema:
  - English: `| Name | Description | Links | Fees |`
  - Chinese: `| 名称 | 说明 | 链接 | 费用 |`
- README entries with a deep-dive link to `docs/<slug>/` via `[Intro](docs/<slug>/...)` (EN) and `[入门介绍](docs/<slug>/...)` (CN).

When adding/removing/editing a tool, the change almost always touches **both** READMEs (and often `CHANGELOG.md` and a `docs/` page). A change in only one language is a bug.

## Commands

- Format/normalize both READMEs: `python3 scripts/format_readmes.py` (run from anywhere — the script resolves the project root itself). This rewrites tables to the canonical 4-column form, strips ` `, converts `</br>` → `<br>`, dedents tabs, and fixes a couple of known broken TOC anchors. Run it after any table edit.
- Local link check (requires [lychee](https://github.com/lycheeverse/lychee) installed): `lychee .` — mirrors the CI workflow at `.github/workflows/link-check.yml`. `.lycheeignore` holds the exclusion list.

There is no build, test, or lint suite beyond the above — CI only runs link checking on `**/*.md`.

## Editing Conventions

- When adding a new tool, follow the existing table format in both READMEs.
- Table format is strict: exactly 4 columns, with the separator row `| --- | --- | --- | --- |`. `format_readmes.py` will rewrite divergent separators, so don't hand-craft 3- or 5-column variants.
- The TOC at the top of each README lists category anchors. The formatter knows about two specific anchor-typo fixes (`#news-information` in EN, `#gpt-llms应用` in CN) — preserve those exact slugs.
- When linking to a deep-dive doc, use the EN/CN phrasing pair `[Intro](...)` / `[入门介绍](...)` so both READMEs stay parallel.
- **Deep-dive placement convention**: For new tools, write the detailed intro as GitHub Discussions (one CN + one EN, e.g. Codex, Kimi Code & Kimi Work, 豆包工作, Google AX, ARTEMIS) and link the README entry to the discussion — do NOT add new per-tool pages under `docs/`. Content that changes frequently (product features, pricing details) belongs in Discussions; only stable, curated reference material goes in `docs/`. (Existing `docs/` pages remain until migrated.)
- Keep tool descriptions concise and factual; ensure links are valid.
- Maintain bilingual consistency between English and Chinese READMEs.
- **Marker conventions**: 🌟 marks tools that are genuinely good to use — the first-choice pick in their category; apply it sparingly. 🌱 marks freshly released / early-stage products whose direction is still uncertain (e.g., developer previews); revisit 🌱 entries periodically and remove the marker once the tool matures — or remove the entry if it stalls.
- **CHANGELOG.md**: Document additions, removals, renames, and notable model updates (e.g., when a chatbot or model entry is refreshed to a new flagship version). Keep entries concise — one line per change: tool/section name, the essence of what changed, and `(both EN/CN)`; spec details and background belong in the README or discussion pages, not the changelog. Minor description updates (e.g., fixing typos, small feature list tweaks), section reordering, and moving tools within a section do NOT require a changelog entry. Neither do link/reference fixes — e.g., repairing dead links, repointing links after a `docs/` page moves to a Discussion, or other changes that alter no tool information.