new-setting
Skill400 starsChanged 34 days agoMITView on GitHub
How to add a setting to hegel-rust. Use when the user asks to add a setting, a Settings builder method, a hegel.toml profile key, a HEGEL_* environment variable, or a hegel_settings_set_* C-ABI function. Covers every surface a setting must reach before it counts as done.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Rain-kl/OpenFlaretheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Rain-kl/OpenFlare★ 298same 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- add-library-supportSkill
- changelogSkill
- coverageSkill
- new-default-generatorSkill
- new-generatorSkill
- self-reviewSkill
The file
Files
Adding a Setting
A setting is not done until it is reachable every way the others are. Pick an existing setting (e.g. derandomize) and follow it through each of these:
- Engine builder — a
Settingsbuilder method inhegel-c/src/settings.rs. - Profile key — a
hegel.tomlkey inhegel-c/src/config.rs, with the same name and vocabulary as the builder method. - C ABI —
hegel_settings_set_<name>/hegel_settings_get_<name>inhegel-c/src/lib.rs, thenjust c-headerto regeneratehegel-c/include/hegel.handsrc/ffi/sys/fns.rs. - Frontend —
src/ffi.rsround-trips the value through the new C functions, and theSettingsbuilder insrc/runner.rsexposes it. - Environment variable —
HEGEL_<SETTING>applied inSettings::with_env_overrides_from(hegel-c/src/settings.rs), using the same vocabulary as the profile key. An empty value is ignored; a malformed value is rejected with a message naming the variable. Never add a setting without its variable: libtest owns the command line, so the variable is the only way to change a setting for one run of a#[hegel::test]without editing it. - Docs —
src/docs/settings.md(the settings table and both environment-variable tables) and thehegel_settings_newdoc comment inhegel-c/src/lib.rs. - Tests — in
tests/(frontend) andhegel-c/tests/(engine), never inline: builder, profile parsing, C-ABI get/set round trip, env-var override (empty ignored, malformed rejected). Thecoverageskill applies. - Release notes — a
RELEASE.mdentry per thechangelogskill.
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.

