agentleFS
antvisantvis/G6/.cursor/rules/translation.mdc

G6 / rules

Cursor rule12k starsChanged 18 months agoMITView on GitHub

翻译

We split this translation.mdc into the rules it gives an agent

9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    When translating files under the site/docs directory, please adhere to the following guidelines:

    line 8
  2. Distinctive:

    Consistency in Terminology: Ensure that terminology is consistent throughout the document.

    line 10
  3. Very specific:

    When translating from Chinese to English, create or update the .en.md file in the same directory.

    line 42
  4. Very specific:

    When translating from English to Chinese, create or update the .zh.md file in the same directory.

    line 43
  5. Distinctive:

    Full Document Translation: If the entire document is selected for translation, replace the entire content with the translated version.

    line 47
  6. Distinctive:

    Partial Content Translation: If only specific sections are selected, find the appropriate place to replace or insert the translated …

    line 48
  7. Distinctive:

    Contextual Translation: Avoid literal translations.

    line 50
  8. Very specific:

    Preserve Metadata Order: Do not modify the order attribute in the page metadata during translation.

    line 54
  9. Distinctive:

    Add '/en' Prefix to Internal Links: Ensure that all internal links in English documentation have the '/en' prefix to maintain consistency …

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule 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
translation.mdc
---
description: 翻译
globs:
alwaysApply: false
---
# Translation Guidelines for site/docs

When translating files under the `site/docs` directory, please adhere to the following guidelines:

1. **Consistency in Terminology**: Ensure that terminology is consistent throughout the document. Use a glossary if available to maintain uniformity in terms.

   **Glossary**:

   - 画布 (Canvas)
   - 元素 (Element)
   - 节点 (Node)
   - 边 (Edge)
   - 组合 (Combo)
   - 交互 (Behavior)
   - 布局 (Layout)
   - 插件 (Plugin)
   - 动画 (Animation)
   - 数据处理 (Transform)
   - 色板 (Palette)
   - 配置项 (Option)
   - 图数据 (Graph Data)
   - 树图 (Tree Graph)
   - 属性 (Property)
   - 描述 (Description)
   - 类型 (Type)
   - 默认值 (Default Value)
   - 必选 (Required)

2. **Adjust Hyperlinks**: Review and adjust hyperlinks to ensure they point to the correct translated sections or documents. Verify that all links are functional and correctly formatted.

   - **Internal Links**: In the English version, all internal links should have a `/en` prefix, while the Chinese version should not have any prefix. Ensure this prefix is added to all internal links in English documents to avoid any oversight.
   - **Anchor Points**: For anchor points following a `#`, if they contain Chinese characters, they should be adjusted to match the corresponding title in the English version rather than being directly translated.
   - **External Links**: Convert external links appropriately to ensure they align with the language and context of the document.

3. **Direct Writing to Translated Documents**: Translations should be stored in corresponding `.en.md` or `.zh.md` files within the same directory. Ensure that the translated content is placed in the correct location within the document.

   - When translating from Chinese to English, create or update the `.en.md` file in the same directory.
   - When translating from English to Chinese, create or update the `.zh.md` file in the same directory.

4. **Support for Partial Content Translation**: Allow for the selection and translation of specific sections of content. Translated sections should be inserted into the appropriate location within the document, maintaining the logical flow and structure.

   - **Full Document Translation**: If the entire document is selected for translation, replace the entire content with the translated version.
   - **Partial Content Translation**: If only specific sections are selected, find the appropriate place to replace or insert the translated content, ensuring the document's logical flow and structure are maintained.

5. **Contextual Translation**: Avoid literal translations. Ensure that the translation fits the English context and conveys the intended meaning accurately.

6. **Direct Modification**: Translations should be directly modified in the corresponding `.en.md` or `.zh.md` files without returning the translated content separately. Ensure that the changes are saved in the correct file and location.

7. **Preserve Metadata Order**: Do not modify the `order` attribute in the page metadata during translation. This ensures that the document order remains consistent across different language versions.

8. **Add '/en' Prefix to Internal Links**: Ensure that all internal links in English documentation have the '/en' prefix to maintain consistency and correct navigation.

By following these guidelines, translations will be more accurate and consistent, facilitating easier review and integration into the documentation.

Download now (ZIP)

Trending

Less talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 5 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the antvis/G6 repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about antvis/G6

The biggest 5 of 56 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 56

Talked about on GitHub, the web and Bluesky (56 times).

On GitHub · 50

45 more on GitHub

On the web · 5

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 3,978 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.

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.