Note: Bookmark-style intro on aogl.cn — not the vendor’s official docs. Features and pricing are on their site.
Cursor is the IDE I use to maintain this static repository: multilang HTML, Node build scripts, and JSON data under data/. I list it under Coding & IDE on the tools directory because it is where edits land in git—not where I browse headlines.
Typical tasks on aogl.cn
- Refactor a build script (
scripts/build-seo-locale-pages.mjs, hub generators) with repo context. - Generate a new multilingual HTML shell, then I hand-tune
lang-*blocks. - Find all nav copies before centralizing them in
scripts/site-nav.mjs. - Run
npm run build-sitein the integrated terminal and fix linter issues file-by-file.
How I keep quality high
I treat agent suggestions as diffs to review, not commits to blindly accept. Rules that saved this project:
- Scope — one script or one JSON hub per task; no drive-by reformat of unrelated HTML.
- Build after change — if
build-hubsorbuild-articlesfails, the task is not done. - No secrets — AdSense IDs and analytics are already public in
js/; still no private tokens in prompts. - Preserve markers — comments like
INDEX_ORIGINALS_AUTO_STARTmust survive automation.
Cursor vs GitHub Copilot
Both appear in my directory. Cursor wins when I need cross-file refactors and chat anchored to the workspace; Copilot wins for single-line completions inside a file I already have open. I link both honestly—pick the tool that matches the grain of the task.
Limits
- Cursor does not replace reading vendor docs for Claude, Gemini, or API pricing.
- It will not run GitHub Actions schedules for me—I still rely on
.github/workflows/. - Generated copy for public articles gets a human pass for facts and tone before deploy.
See also: Claude bookmark notes, GitHub Copilot guide, and WebGL article for the kind of demo this repo publishes.
Last checked: 2026-06-18.