Skip to content

docs: add agent glossary and AGENTS.md - #1077

Draft
yattias wants to merge 1 commit into
mainfrom
cursor/add-agents-md-and-glossary-8c49
Draft

docs: add agent glossary and AGENTS.md#1077
yattias wants to merge 1 commit into
mainfrom
cursor/add-agents-md-and-glossary-8c49

Conversation

@yattias

@yattias yattias commented Sep 2, 2026

Copy link
Copy Markdown
Member

What

Two new docs aimed at AI coding agents (and new engineers):

  • docs/glossary.md — the domain and architecture vocabulary of this repo, grouped by area, with the defining file named for every entry.
  • AGENTS.md — a short orientation doc that links the glossary and covers commands, repo layout, and the conventions that are easy to get wrong.

Why

A lot of this codebase's vocabulary does not mean what it sounds like, and the mismatches are the kind that produce quietly wrong code:

  • A proposal in the UI is a preregistration in the data model, and an RFP is a Grant with contentType: 'funding_request'.
  • Unified document ids, not paper or post ids, are what many endpoints key off.
  • ContentType, DocumentType, CommentType, Contribution, Author, useComments, and transformUnifiedDocument each mean different things in different modules.
  • The API calls tips purchases, and calls topics hubs.
  • Amounts are dual-currency, and historical totals need rscUsdSnapshot rather than the live exchange rate.

The glossary closes with an "Ambiguous names" section listing every collision found, since those are the ones most likely to cause a bad edit.

AGENTS.md also records a few facts that are not discoverable from the code alone: npm install needs an .npmrc with Tiptap Pro and FontAwesome Pro credentials, CI gates only the smoke suite (not lint, type-check, or build), and a long list of stock ESLint rules is disabled — so a clean npm run lint does not imply idiomatic code.

Scope

Documentation only. No source files are touched.

Verification

Every claim was read out of the source rather than inferred. Two scripted checks back that up:

  • 92 referenced file and directory paths all exist.
  • 214 referenced code identifiers all resolve in the source. The three the docs describe as not existing (BaseService, fetchWithAuth, a lowercase apiClient) were asserted absent.

Both docs are Prettier-clean, matching the rest of the repo's markdown.

npm run type-check and npm run lint could not run in this environment because npm install fails without the private registry credentials, and neither applies to markdown. The pre-commit hook was skipped for the same reason.

Open in Web Open in Cursor 

Adds docs/glossary.md, a reference for the domain and architecture
vocabulary an agent needs to work in this repo: the content model
(Work, unified documents, the ContentType/ApiDocumentType split),
the funding flow (RFP, proposal/preregistration, fundraise,
registered report), RSC and dual-currency amounts, bounties, tips
and comment-backed reviews, the notebook, feeds, the ApiClient and
transformer layers, and the UI/state conventions. Each entry names
the file that defines the term, and a final section lists the
identifiers that are reused with different meanings across modules.

Adds AGENTS.md pointing at the glossary and covering commands,
repo layout, and the conventions that are easy to get wrong.

lint-staged runs eslint and tsc, neither of which applies to
markdown, and node_modules cannot be installed here without the
private registry credentials, so this commit skips the hook.
Formatting was verified with prettier directly.
@vercel

vercel Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
web Ready Ready Preview Sep 2, 2026 9:12pm UTC

Request Review

@sonarqubecloud

sonarqubecloud Bot commented Sep 2, 2026

Copy link
Copy Markdown

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