Skip to content

cursorrules: align output-name policy with the ComfyUI frontend #146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
comfyui-wiki merged 1 commit into from
Sep 14, 2026
Merged

cursorrules: align output-name policy with the ComfyUI frontend #146

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .cursorrules
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ Data types should be represented using plain text, not styled text.
### Translation Principles
- Only translate when explicitly requested by the user
- **Parameter names in Inputs table**: Use ComfyUI frontend translations when available (e.g. FR: `texte`, JA: `テキスト`) — this ensures docs match what users see in the UI
- **Output names in Outputs table**: Keep in English (programmatic identifiers, do not translate)
- **Output names in Outputs table**: Follow the ComfyUI frontend per language (`docs-generation/data/node_translations.json`, `outputs.<index>.name`). The frontend itself localizes semantic outputs (e.g. zh: `正面条件`, es: `positivo`) while keeping technical identifiers English (e.g. `task_id`, `GLB`, `part_names`, `mask`) — mirror exactly what users see in the UI. When the frontend has no entry for an output, keep the English name
- Keep data types in English
- Maintain document structure consistency
- Ensure metaphors are appropriate for the target language
Expand Down
Loading