hashiiiii-locale
Skill10 starsChanged 3 months agoMITView on GitHub
Use this skill to set or change locale preferences for a user, project, or local Git worktree.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hallmarkSkill
- hashiiiii-explain-prSkill
- hashiiiii-gitSkill
- hashiiiii-imagesSkill
- hashiiiii-issuesSkill
- hashiiiii-pull-requestSkill
- hashiiiii-write-enSkill
- hashiiiii-write-jaSkill
- hashiiiii-zigSkill
- show-meSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Write all five locale keys to the scope the user selects.
- Distinctive: line 42
Always write all five keys.
- Very specific: line 46
Use LF line endings and strict key=value lines with no spaces around =:
- Distinctive: line 58
Create the target directory if needed.
≈ “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
Locale Preferences
Write all five locale keys to the scope the user selects. Do not infer the scope from the current directory or plugin installation.
Scope
Accept user, project, or local, either as a bare argument or as scope=<scope>. If the user does not select a scope, ask before proceeding. Before writing, state the selected scope, exact target path, and sharing behavior.
| Scope | File | Sharing |
user | ${XDG_CONFIG_HOME:-${HOME:-}/.config}/rules-for-ai/LOCALE.md | All projects for this user |
project | <repo>/.rules-for-ai/LOCALE.md | Anyone using the repository |
local | <absolute-git-dir>/rules-for-ai/LOCALE.md | This Git worktree only |
For project and local, get the repository with git rev-parse --show-toplevel. For local, get the directory with git rev-parse --absolute-git-dir. Stop if either command fails. Do not commit project files automatically or add local files to Git ignore rules.
Locale Values
A single POSIX-style locale tag, such as ja_JP, sets all five keys. Key-value arguments set individual keys. If no locale values are given, ask which locale to use for each artifact. Reject unknown scopes and keys. Keep each tag as supplied; do not translate or normalize it.
| Key | Applies to |
issues | Issues |
pull-requests | Pull requests |
comments | Code comments |
logs | Log messages |
test-logs | Test log messages |
For a partial update, keep existing target values first. Fill missing keys only from lower-priority scopes:
| Target | Fallback order |
local | Project, user, bundled default, en_US |
project | User, bundled default, en_US |
user | Bundled default, en_US |
Always write all five keys. Never copy local values into project or user settings. Locale resolution uses the first existing file as a whole; project instructions take precedence over locale keys.
Write the File
Use LF line endings and strict key=value lines with no spaces around =:
# Locale
issues=ja_JP
pull-requests=ja_JP
comments=ja_JP
logs=en_US
test-logs=en_USCreate the target directory if needed. Write a temporary file in that directory, then atomically move it over the target.
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.

