agentleFS
hiromailyhiromaily/go-crypto-wallet/.cursor/rules/documentation-language.mdc

go-crypto-wallet / rules

Cursor rule128 starsChanged 6 months agoMITView on GitHub

Documentation Language Rules

We split this documentation-language.mdc into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    All documentation files (.md, .mdc) in this project must be written in English.

    line 14
  2. Distinctive:

    Use American English spelling (e.g., "color" not "colour")

    line 30
  3. Distinctive:

    Use consistent terminology throughout the project

    line 31

≈ “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
documentation-language.mdc
---
description: Documentation Language Rules
globs: 
  - "**/*.md"
  - "**/*.mdc"
alwaysApply: false
---


# Documentation Language Rules

## Overview

All documentation files (`.md`, `.mdc`) in this project must be written in **English**.

## Rules

1. **Write all documentation in English**
   - README files
   - Technical documentation
   - Code comments in markdown
   - Rule files (`.claude/rules/`, `.cursor/rules/`)
   - Skill files (`.claude/skills/`, `.cursor/skills/`)

2. **Exceptions**
   - Inline code comments in source files may use Japanese if necessary for clarity
   - User-facing messages that require localization

3. **Consistency**
   - Use American English spelling (e.g., "color" not "colour")
   - Use consistent terminology throughout the project

## Rationale

- English documentation ensures accessibility for international contributors
- Maintains consistency across the codebase
- Facilitates collaboration with global developer community

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.

Reviews can't be read right now.

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.