project-config
Skill0 starsChanged 2 days agoMITView on GitHub
Create or check keyturn's project configuration, keyturn/config.json, which holds the client's language and whether the project uses English-only mode. Use when a keyturn project is being set up, when another keyturn role needs a setting, or when someone asks to see or change the project's language settings. Stops and reports when the file is missing or invalid, instead of guessing a value.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ice-lfernandes/claude-spring-architecttheir own version, first seen Nov 1, 2026
- nerviz-ai/nerviztheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ice-lfernandes/claude-spring-architect★ 11same name
- nerviz-ai/nerviz★ 11same name
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.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- conventionsSkill
- designSkill
- implementSkill
- localizeSkill
- qaSkill
- resumeSkill
- reviewSkill
- security-reviewSkill
- specSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Create and check the project configuration, keyturn/config.json, so that every role reads the same settings and none guesses them.
- Distinctive: line 12
Never guess a setting: If the configuration is missing or invalid, stop and report what is wrong.
- Distinctive: line 14
Change the file only on request: Create it when a project is set up, or change it when the client asks.
- Very specific: line 39
Check first: Run project_config.py check.
- Very specific: line 42
Create it when the project is set up: Ask the client which language they read and write, and whether everything published must be in …
≈ “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
project-config
Create and check the project configuration, keyturn/config.json, so that every role reads the same settings and none guesses them. See ADR 0014 in keyturn's docs/adr/.
Rules
- Never guess a setting. If the configuration is missing or invalid, stop and report what is wrong. Do not fall back to a default, and do not infer a value from the conversation without asking.
- Ask the client, then write. The settings are the client's choices. Ask for them in plain words, and write only what they said.
- Change the file only on request. Create it when a project is set up, or change it when the client asks. Every other use is read-only.
Settings
| Setting | Value | Meaning |
client_language | a language code, such as ja, de, pt-BR | The language the client reads and writes. |
english_only | true or false | true: everything committed or posted is in English, and the client reads it through localize. false: client-facing documents are written in client_language. |
There are no other settings yet. A setting is added, with the script and its tests, by the skill that first needs it.
Inputs
- For creating: the client's language, and whether the project uses English-only mode (for example, a public open-source project whose published content should all be in English).
- For checking or reading: nothing; the file is always
keyturn/config.jsonat the repository root.
Outputs
keyturn/config.json, committed with the other keyturn documents.- For a check:
ok, or one line per problem.
Procedure
The helper script scripts/project_config.py (in this skill's folder) does all reading and checking. It needs Python 3.9 or later and Git, and uses only the standard library. Run it from inside the target repository. Below, project_config.py means the script's full path.
- Check first. Run
project_config.py check.ok: the configuration can be used. Read a setting withproject_config.py get <setting>, which checks the file again first.- Problems (exit code 1): stop, show the client or the role that asked every line the script printed, and fix the cause before going on. A missing file is created with step 2; any other problem is fixed in step 3.
- Create it when the project is set up. Ask the client which language they read and write, and whether everything published must be in English. Then run
project_config.py init --client-language <code> --english-only(or--no-english-only). The script refuses to overwrite an existing file. Runcheck, and commit the file. - Change it only when the client asks. Edit
keyturn/config.json(keep it a JSON object with exactly the settings above), runcheckuntil it printsok, and commit it. A change ofclient_languageorenglish_onlychanges the language of client-facing documents from then on; tell the client which documents will be written in the new language.
Notes
- The check always gives the same result for the same file: it lists missing settings, invalid values, and unknown settings, in a fixed order. An unknown setting is an error, so a typo in a setting's name is caught instead of being ignored.
- Scripts and hooks that read the configuration either call
project_config.py get, or runproject_config.py checkand then parse the JSON themselves.
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.

