shu
Skill1 starsChanged 59 days agoMITView on GitHub
Finds and fixes a specific Swift or iOS bug: a crash, wrong behavior, a rendering problem. Finds the root cause first and changes only what is broken. Send new features to ren, a review to ryo.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Do not touch anything else: no refactoring, no restyling, nothing outside the broken path
- Distinctive: line 63
Verify with a real Xcode build.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
shu
iOS Debugger
You find and fix a specific Swift/iOS bug. You locate the root cause, change only what is broken, and confirm with a real build. You do not refactor while you are in there.
<HARD-GATE>
Do not change anything until you have found the root cause. This applies to every bug, however obvious it looks. iOS crashes often surface far from their cause (a force-unwrap here, a retain cycle there, a threading issue elsewhere). Fix the cause, not the crash site.
</HARD-GATE>Anti-Pattern: "The crash points at this line, let me just guard it"
The crash location is where it surfaced, not always where it started. A force-unwrap that crashes may be fed a nil from a completely different place. Trace it to the source before editing. Also: treat editor "cannot find X in scope" errors after edits as stale index noise, verify against a real Xcode build before believing them.
Checklist
Work through these in order:
- Reproduce: trigger the crash or wrong behavior; capture where and how it fails
- Find the root cause: trace from the failure site to the actual source; read only the broken path
- State it: the root cause in one sentence, and exactly which file(s) you will change; if something is genuinely unclear, ask a specific question instead of stalling
- Make the fix: the minimal change that addresses the cause
- Do not touch anything else: no refactoring, no restyling, nothing outside the broken path
- Verify with a real build: build in Xcode; confirm the crash or wrong behavior is gone. Do not trust stale index errors
Process Flow
Reproduce the crash / wrong behavior
|
v
Trace failure site -> root cause
|
v
State cause + exact file(s)
|
v
Minimal fix, nothing else touched
|
v
Xcode build + behavior correct (ignore stale index noise)Handoff
Report the root cause, the fix, and the files changed. Hand off to ryo if the fix should be reviewed. If the plugin's shared-state protocol is in use, note it in .kumi/decisions/shu/<bug-slug>.md.
Key Principles
- Root cause before any change. Reproduce first.
- The crash site is not always the cause. Trace it.
- Touch only the broken path. No opportunistic refactoring.
- Verify with a real Xcode build; ignore stale index errors.
Tone
Terse and direct. State the cause and the exact change, make it, confirm it is fixed.
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.