Record what ScarletNX work taught, where the next session will look for it. Use after a bug took more than one attempt to find, when the same mistake happened twice, when a debugging technique worked, or when the user corrects how work is done.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
A lesson left in the chat is gone next session. Put it where it will be read.
| Lesson | Where | Form |
|---|---|---|
| How a console component behaves, proven on the game (a service answer, an SDK expectation, a GPU rule) | A comment at the code that depends on it, saying why | One or two lines, naming the SDK function or Switchbrew page |
| A bug pattern a future change could reintroduce | CLAUDE.md, "Lessons that cost a session" | One bullet: the trap and the rule |
| A step of a procedure that was missed | The skill that covers it (snx-build, snx-run, snx-crash, snx-service) | An imperative line with the reason |
| Something that must never happen | .claude/hooks/guard.py | A rule with the message to show |
| A debugging script that worked | tools/, with a docstring and usage, mentioned in docs/DEVELOPMENT.md | The scratchpad is wiped between sessions |
| Reviewer knowledge (a past bug shape in a domain) | The matching .claude/agents/review/snx-*-reviewer.md, "Known past-bug shapes" | One bullet |
| Status, plan, the user's choices | docs/ROADMAP.md, and the session memory for things not in the repo | Absolute dates |
Prove it first: a rule from one occurrence is written as what that occurrence needed, not as a general rule, until a second case confirms it. When an existing lesson turns out wrong, correct it rather than adding a contradicting one.
Commit lessons with the work that found them, or alone with a subject like "Document ...".
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audits uncommitted changes, branches, or PRs for bugs, edge cases, SOLID/DRY/SRP, architecture, security, performance, and CLAUDE.md violations — then automatically fixes ALL issues and re-audits in a loop until clean. Use when: audit, review, code review, review this PR, check code, look over this, inspect code, or any variation.
The English summary is being prepared. Showing the original description.
Build the ScarletNX runtime and recompile games correctly, avoiding the setups that build "successfully" into something that doesn't work. Covers the CPM.cmake dependencies, the Clang-only presets, the deploy into games/, when a game needs recompiling, and the warnings a plain build doesn't show. Use when building, rebuilding, recompiling a game, after pulling or bumping a dependency, or when a build result looks suspicious.
The English summary is being prepared. Showing the original description.
RFC #142's C rules: strict ISO C99, no redundant state, indices not pointer chains, one allocation per owner, atomics apart, no stored pointers, one global struct per file. Use when writing or reviewing C in src/.
The English summary is being prepared. Showing the original description.
Take a ScarletNX crash report, svcBreak or hang from the log to the mechanism that causes it, using the symbolizer and disassembler on the game's code. Use when the game crashes (signal 11 or 7), calls svcBreak or fatal, hangs, or when a log shows "*** Crash". Also for corrupted data showing up in game structures.
The English summary is being prepared. Showing the original description.
Write and optimize ScarletNX's own compute shaders (astc.comp, vic.comp, future ones) for what the GPU actually executes: constant tables, bit twiddling, uniform branches, fewer fetches, workgroup and subgroup structure, exactness proofs, and the GLSL-as-C++ tests and lavapipe timing that check them. Use when writing, reviewing or speeding up a GLSL shader under src/nx/gpu/, or when deciding whether to split one.
The English summary is being prepared. Showing the original description.
Run a recompiled game unattended and judge the result: scripted button input, timed exit, screenshots, reading the log, and repeat runs for intermittent crashes. Use when verifying a runtime change, reproducing a bug, checking a scene renders, measuring a crash rate, or when the user asks to run or test the game.
The English summary is being prepared. Showing the original description.