mcp-doc-generator: Cursor rule for Cursor

Cursor Rules for MCP Documentation Server

⚠️ DEPRECATED: This file is deprecated. Please use .cursor/rules/documentation.md instead.

This file is kept for backward compatibility but will not be actively maintained. For the latest rules, see: .cursor/rules/documentation.md

Documentation Standards

Bilingual Documentation (EN/PL)

All documentation files must be bilingual (English/Polish) following this structure:

1. Primary Language: English - Write all documentation first in English
2. Secondary Language: Polish - Synchronize Polish version after English is complete
3. Structure Pattern:
   • Use language anchors: <a name="english"></a> and <a name="polski"></a>
   • English section comes first
   • Polish section comes after, marked with <a name="polski"></a>
   • Use separator: --- between language sections

Documentation File Format

# Document Title

**Language / Język:** [English](#english) | [Polski](#polski)

---

<a name="english"></a>
# English

[English content here]

---

<a name="polski"></a>
# Polski

[Polish content here - synchronized with English]

Writing Guidelines

1. Write English first - Always create English version first, ensure it's complete and accurate
2. Synchronize Polish - After English is done, create Polish version that:
   • Maintains the same structure and sections
   • Preserves code examples (they remain in English)
   • Translates all explanatory text accurately
   • Keeps technical terms consistent (use English terms with Polish explanations if needed)
3. Code Examples - Keep code examples in English, add Polish comments if helpful
4. Links and References - Maintain English anchor names, translate link text
5. Consistency - Use consistent terminology across all documents

Files Requiring Bilingual Content

• README.md
• All files in docs/ directory
• USAGE_GUIDE.md
• QUICKSTART.md
• Any new documentation files

When Creating New Documentation