improve-bottler
Skill0 starsChanged 49 days agoMITView on GitHub
Fix or extend mac-bottler's shared code (core/, tools/, win/) when a problem found while bottling a game belongs to every game, not one recipe - branch, failing test first, fix, re-verify the affected apps, open a pull request. Never merges. Use when the cook or diagnose skill finds a generic bug or a missing generic feature.
- Commits and pushes
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 39
commit anything from a game (make test refuses binaries and game files).
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
/improve-bottler <the problem>
For changes to core/, tools/ or win/. A change that only one game needs
belongs in its recipe instead (AGENTS.md: nothing generic is built ahead of a
recipe's need, and nothing game-specific lives outside recipes/).
Steps
- Branch from an up-to-date
main:git switch main && git pull --ff-only && git switch -c fix/<slug>(orfeature/<slug>). Never commit tomain. - Write the failing test first in
tests/run-tests.sh, hermetic: synthetic PE files (tests/fixtures/mkpe.py), fake app layouts, stub wine, fake displays (bottler geometry --screen …,BOTTLER_TEST_SCREENS). Runmake testand see it fail for the right reason. - Fix it, matching the surrounding code's style. Keep game names out of
generic code:
grep -rniE "<game-specific words>" core tools winstays empty. - Prove it:
make testandmake compilepass (quote the result lines);- break the fix on purpose once and confirm the new test fails (then restore);
- rebuild every project whose app is affected (
make app PROJECT=<name>, never while its game runs) and re-check it with the observe tools; ask the user only for what tools cannot check (sound, feel).
- Document: a new trap goes into
docs/INTERNALS.md; a schema change intodocs/RECIPES.md; a new component intodocs/THIRD-PARTY.md. - Commit with the rulings in the body (what you decided, why, what it costs
if wrong), then
git push -u origin <branch>andgh pr create --base mainwith: the problem, the cause, the fix, the test, what was verified on which apps, and what was not.
Never
- merge, push
main, force-push, amend, or skip hooks; - weaken or delete a test to get to green;
- commit anything from a game (
make testrefuses binaries and game files); - copy code from projects under a different license without the maintainer's
approval (see
docs/THIRD-PARTY.md).
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.

