Pluto.jl / rules
Cursor rule5.4k starsChanged 12 months agoMITView on GitHub
How to localize strings in the Pluto.jl frontend.
1 other project uses a version of this.
Trending
Less talk lately.about the whole repository
Most recently taken up by
- fonsp/Pluto.jlword for word, first seen Oct 9, 2026
Who's talking about JuliaPluto/Pluto.jl
- Paulogcd/MPC_Simulations.jl“Bump Pluto from 1.0.4 to 1.1.0 in /docs”GitHub · Nov 2, 2026
- JuliaPluto/featured“Bump Pluto from 1.0.4 to 1.1.0 in /pluto-deployment-environment in the all-julia-packages group across 1 …”GitHub · Nov 2, 2026
- sosiristseng/gensjulia“Link Checker Report”GitHub · Nov 1, 2026
- sosiristseng/sosiristseng.github.io“Link Checker Report”GitHub · Nov 1, 2026
- JuliaRegistries/General“New version: Pluto v1.1.0”GitHub · Oct 27, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- Nov 2, 2026Bump Pluto from 1.0.4 to 1.1.0 in /docs — Paulogcd/MPC_Simulations.jl0 reactions
- Nov 2, 2026Bump Pluto from 1.0.4 to 1.1.0 in /pluto-deployment-environment in the all-julia-packages group across 1 directory — JuliaPluto/featured0 reactions
- Nov 1, 2026Link Checker Report — sosiristseng/gensjulia0 reactions
- Nov 1, 2026Link Checker Report — sosiristseng/sosiristseng.github.io0 reactions
- Oct 27, 2026New version: Pluto v1.1.0 — JuliaRegistries/General0 reactions · 1 comment
45 more on GitHub
- Oct 23, 2026WebKit: a reload while a websocket message is being read logs "Failed to unpack message" and a page error, failing first-cell.test.mjs — jowch/Ember0 reactions · 1 comment
- Oct 5, 2026Bump the all-julia-packages group across 1 directory with 2 updates — JuliaPluto/featured0 reactions · 1 comment
- Oct 4, 2026New version: Pluto v1.0.4 — JuliaRegistries/General0 reactions · 1 comment
- Oct 1, 2026Link Checker Report — sosiristseng/gensjulia0 reactions
- Oct 1, 2026Link Checker Report — sosiristseng/sosiristseng.github.io0 reactions
- Sep 1, 2026Link Checker Report — sosiristseng/gensjulia0 reactions
- Sep 1, 2026Link Checker Report — sosiristseng/sosiristseng.github.io0 reactions
- Aug 31, 2026[pull] main from JuliaPluto:main — Spencerx/Pluto.jl0 reactions
- Aug 1, 2026Link Checker Report — sosiristseng/gensjulia0 reactions
- Aug 1, 2026Link Checker Report — sosiristseng/sosiristseng.github.io0 reactions
- Jul 27, 2026Update JuliaMono font — JuliaDocs/Documenter.jl0 reactions · 3 comments
- Jul 24, 2026Bump the all-julia-packages group across 2 directories with 4 updates — TuringLang/TuringGLM.jl0 reactions · 3 comments
- Jul 17, 2026Bump the all-julia-packages group across 2 directories with 3 updates — TuringLang/TuringGLM.jl0 reactions · 2 comments
- Jul 16, 2026Bump Pluto from 1.0.1 to 1.0.3 — josealuna/PGA.jl0 reactions
- Jul 15, 2026Update Pluto requirement to 1.0.3 — dillondaudert/UMAP.jl0 reactions
- Jul 7, 2026New version: Pluto v1.0.3 — JuliaRegistries/General0 reactions · 1 comment
- Jul 6, 2026Handle function and macro expressions in explore — JuliaPluto/ExpressionExplorer.jl0 reactions · 7 comments
- Jul 6, 2026[pull] main from JuliaPluto:main — Spencerx/Pluto.jl0 reactions
- Jul 6, 2026New version: Pluto v1.0.2 — JuliaRegistries/General0 reactions · 1 comment
- Jul 3, 2026Bump the all-julia-packages group across 2 directories with 3 updates — TuringLang/TuringGLM.jl0 reactions · 2 comments
- Jul 2, 2026[pull] main from JuliaPluto:main — Spencerx/Pluto.jl0 reactions
- Jul 1, 2026Update Pluto requirement from 0.20.21 to 0.20.21, 1.0 in /notebooks in the all-julia-packages group across 1 directory — abhro/GravitationalPotentials.jl0 reactions
- Jul 1, 2026Link Checker Report — sosiristseng/gensjulia0 reactions
- Jul 1, 2026Link Checker Report — sosiristseng/sosiristseng.github.io0 reactions
- Jun 29, 2026Link Checker Report — sosiristseng/gensjulia0 reactions
- Jun 27, 2026Link Checker Report — sosiristseng/sosiristseng.github.io0 reactions
- Jun 26, 2026Bump the all-julia-packages group across 2 directories with 3 updates — TuringLang/TuringGLM.jl0 reactions · 2 comments
- Jun 22, 2026Link Checker Report — sosiristseng/gensjulia0 reactions
- Jun 20, 2026Link Checker Report — sosiristseng/sosiristseng.github.io0 reactions
- Jun 19, 2026Bump the all-julia-packages group across 2 directories with 3 updates — TuringLang/TuringGLM.jl0 reactions · 1 comment
- Jun 18, 2026[pull] main from JuliaPluto:main — Spencerx/Pluto.jl0 reactions
- Jun 11, 2026[pull] main from JuliaPluto:main — Spencerx/Pluto.jl0 reactions
- Jun 8, 2026[pull] main from JuliaPluto:main — Spencerx/Pluto.jl0 reactions
- Jun 5, 2026Bump the all-julia-packages group across 1 directory with 2 updates — PalmStudio/XPalm.jl0 reactions
- Jun 5, 2026Bump the all-julia-packages group across 2 directories with 2 updates — TuringLang/TuringGLM.jl0 reactions · 2 comments
- Jun 4, 2026[pull] main from JuliaPluto:main — Spencerx/Pluto.jl0 reactions
- Jun 3, 2026Update Pluto requirement from 0.20.23 to 0.20.23, 1.0 — SimonEnsemble/ShortestPathMolecularGraphKernels.jl0 reactions
- Jun 3, 2026Update Pluto requirement from 0.20.21 to 0.20.21, 1.0 in /notebooks in the all-julia-packages group across 1 directory — abhro/MagneticFieldSHTCExpander.jl0 reactions
- Jun 2, 2026[pull] main from JuliaPluto:main — Spencerx/Pluto.jl0 reactions
- Jun 2, 2026Bump the all-julia-packages group across 1 directory with 2 updates — JuliaPluto/featured0 reactions · 1 comment
- Jun 1, 2026[pull] main from JuliaPluto:main — Spencerx/Pluto.jl0 reactions
- Jun 1, 2026[pull] main from JuliaPluto:main — Spencerx/Pluto.jl0 reactions
- Jun 1, 2026Link Checker Report — sosiristseng/gensjulia0 reactions
- Jun 1, 2026Link Checker Report — sosiristseng/sosiristseng.github.io0 reactions
- May 29, 2026Update Pluto requirement from 0.20 to 0.20, 1.0 in the all-julia-packages group — PalmStudio/XPalm.jl0 reactions · 1 comment
Other versions1 project uses a version of this.
Word for word · 1
- fonsp/Pluto.jl★ 5.4k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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 4,243 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.
In this repository3 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/frontend-styling.mdcCursor rule
- .cursor/rules/icon-usage.mdcCursor rule
The file
We split this localization.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
- Distinctive: line 21
Use for plain text strings (button titles, tooltips, etc.):
- Distinctive: line 27
Use for content that contains HTML markup or Preact elements:
- Very specific: line 47
Add new languages following the pattern: {language}.json
- Distinctive: line 64
Always localize user-facing strings: - Never hardcode English text
- Very specific: line 66
Consistent interpolation: - Use {{variable}} syntax for placeholders
- Very specific: line 67
HTML-safe content: - Use th() for any content containing markup
- Distinctive: line 68
Pluralization: - Use separate keys for singular/plural forms when needed
- Very specific: line 69
Fallback coverage: - Ensure all keys exist in english.json (fallback language)
- Distinctive: line 70
Complete sentences: - Always localize complete sentences, not just parts of them.
≈ “Common” is an estimate: at least 1 in 5 of the 6,809 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.
Files
---
description: How to localize strings in the Pluto.jl frontend.
globs: *.js
alwaysApply: false
---
# Pluto.jl Frontend Localization
Pluto.jl uses i18next for internationalization. All user-facing strings should be localized. Always localize complete sentences, not just parts of them.
## Usage
### Import Functions
```js
import { t, th } from "../../lang/lang.js"
```
### Translation Functions
#### `t(key, options?)` - Plain Text
Use for plain text strings (button titles, tooltips, etc.):
```js
alert(t("t_confirm_move_file"), {old_path, new_path})
```
#### `th(key, insertions?)` - HTML Content
Use for content that contains HTML markup or Preact elements:
```js
th("t_newnotebook") // Contains <strong> tags
th("t_welcome_to_pluto", { pluto: html`<img src=${url_logo_big} />` })
html`
<h2>${th("t_something_with_a_number", { count: 5 })}</h2>
`
```
### When to Use Each Function
- **`t()`**: Tooltips, button titles, aria-labels, plain text content
- **`th()`**: Any content with HTML markup, or when interpolating Preact elements.
## Language Files
### Location
Language files are stored in `frontend/lang/` as JSON files:
- `english.json` (fallback language)
- `nederlands_nl.json`
- Add new languages following the pattern: `{language}.json`
### JSON Structure
```json
{
"t_simple_key": "Simple translation",
"t_html_content": "Text with <strong>HTML</strong> markup",
"t_with_interpolation": "Welcome to {{appname}}",
"t_pluralized": "Delete {{count}} items",
"t_pluralized_one": "Delete this item"
}
```
## Best Practices
0. **Always use the `t_` prefix** for all keys.
1. **Always localize user-facing strings** - Never hardcode English text
2. **Use descriptive keys** - Keys should indicate context and usage
3. **Consistent interpolation** - Use `{{variable}}` syntax for placeholders
4. **HTML-safe content** - Use `th()` for any content containing markup
5. **Pluralization** - Use separate keys for singular/plural forms when needed
6. **Fallback coverage** - Ensure all keys exist in `english.json` (fallback language)
7. **Complete sentences** - Always localize complete sentences, not just parts of them.
## Examples
### Simple text:
```js
// ✅ Good
title={t("t_remove_from_recent_notebooks")}
// ❌ Bad
title="Remove from recent notebooks"
```
### HTML content:
```js
// ✅ Good
${th("t_newnotebook")} // "Create a <strong>new notebook</strong>"
// ❌ Bad
html`Create a <strong>new notebook</strong>`
```
### With interpolation:
```js
// ✅ Good
${th("t_welcome_to_pluto", { pluto: html`<img src=${logo} />` })}
// ❌ Bad
html`Welcome to <img src=${logo} />`
```
### Complete sentences:
```js
// ✅ Good
html`
<h2>${th("t_cells_deleted", { count: n })}</h2>
`
// ❌ Bad
<h2>${n}${th("t_cells_deleted")}</h2>
```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
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.

