Skip to content

Cursor MD file for auto generation translation#76

Open
NeonDmitry wants to merge 1 commit intoNeonGeckoCom:masterfrom
NeonDmitry:master
Open

Cursor MD file for auto generation translation#76
NeonDmitry wants to merge 1 commit intoNeonGeckoCom:masterfrom
NeonDmitry:master

Conversation

@NeonDmitry
Copy link

Uploaded MD file for Cursor for generation translation

@NeonDmitry NeonDmitry requested a review from NeonDaniel March 12, 2026 17:10
@NeonDaniel NeonDaniel self-assigned this Mar 12, 2026
Copy link
Member

@NeonDaniel NeonDaniel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a couple minor comments/corrections. Could you also move this to docs/skill_development/language-support/translating-a-skill.md for cleaner organization?


## Repository Structure

Each skill lives in its own `<skill-name>_<lang>_translation` folder (e.g., `skill-name_ua_translation`, `skill-name_de_translation`).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn't be necessary; the skill repository name is generally just <skill-name>; specific translations can be done on different branches

Comment on lines +33 to +34
└─ docx/README.md # project overview
└─ docx/README.en.md # this file (English)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This structure is not used anywhere. I don't think we have per-language README files anywhere; consider adding to the skill repo root instead of nested inside docx subdirectory

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