english-mode
Skill62 starsChanged 2 months agoMITView on GitHub
Toggle English-only mode. Forces English input and provides grammar feedback. Use when: '/english', 'english mode', 'toggle english'.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/AGENTS.mdAGENTS.md
- animation-vocabularySkill
- apple-designSkill
- branchSkill
- codebase-designSkill
- code-qualitySkill
- commitSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- find-skillsSkill
- grillingSkill
- handoffSkill
- improve-animationsSkill
- investigateSkill
- ios-app-designSkill
- nix-darwinSkill
- no-useeffectSkill
- prototypeSkill
- react-best-practicesSkill
- resolving-merge-conflictsSkill
- review-animationsSkill
- rust-design-patternsSkill
- self-reviewSkill
- seo-audit-fullSkill
- seo-auditSkill
- skill-creatorSkill
- slow-is-fastSkill
- ste-writingSkill
- tddSkill
- thermo-nuclear-code-quality-reviewSkill
- thermo-nuclear-reviewSkill
- thermosSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
If argument is "on" → enable
- Distinctive: line 23
If argument is "off" → disable
- Distinctive: line 24
If no argument → toggle (flip current state)
- Distinctive: line 30
After toggling, report the new state concisely:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
English Mode Toggle
Toggle English-only mode for the current project. When enabled:
- Non-English input is blocked — you must rewrite in English
- Grammar and usage feedback appears at the end of each response
Check current state
!jq -r '.["english-mode"] // false' "$CLAUDE_PROJECT_DIR/.claude/features.json" 2>/dev/null || echo "false"
Instructions
Based on "$ARGUMENTS" and the current state above:
- If argument is "on" → enable
- If argument is "off" → disable
- If no argument → toggle (flip current state)
To enable: ensure $CLAUDE_PROJECT_DIR/.claude/features.json exists and has "english-mode": true. Use jq to merge the key without overwriting other keys. Create the file if it doesn't exist.
To disable: set "english-mode": false in the same file. If the file has no other truthy keys, you may delete it.
After toggling, report the new state concisely:
- Enabled: "English mode on for this project. All input must be in English. Grammar feedback will appear at the end of responses."
- Disabled: "English mode off for this project."
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.

