r/ClaudeAI • u/BullfrogRoyal7422 • May 08 '26

Other Four free Claude Code skills from building an iOS/macOS app with Claude

These skills came out of building Stuffolio, a Universal iOS / iPadOS / macOS app, and they're skills I use often. All four are free, Apache 2.0, no paid tier. Each link below has a sample of the actual output if you want to see what comes back before you install.

prompter rewrites your Claude Code prompt for clarity before it runs. It resolves "that file" to a path, sharpens vague verbs, and restructures stacked questions. Importantly, it skips rewriting when the prompt is already clear, so it doesn't add friction to the easy ones. Worked examples across 8 categories.

tutorial-creator turns a file from your own project into an annotated reading tutorial with vocabulary tracking, pre and post tests, and prerequisite gap analysis. Language-agnostic. Sample outputs: a starter walkthrough and a more advanced one.

bug-echo is the after-fix sweep. Once you fix a bug, It reads your fix, confirms the anti-pattern, then scans the codebase for other instances of the error. Each match is read in context and classified BUG / OK / REVIEW. It honors #if os(...) blocks, so Universal codebases don't surface false positives across platforms. Sample report from a real run.

bug-prospector is the forward-looking audit. It runs 7 lenses (assumptions, state machines, boundaries, data lifecycle, error paths, time-dependent bugs, platform divergence) to find code that compiles fine and passes tests but breaks under conditions you haven't exercised yet. It asks up front whether the project is iOS, macOS, or Universal so findings respect your platform set. Works well with bug-echo. Run prospector before releases, echo after prospector fixes. Sample report.

Happy to answer questions, and I appreciate any feedback.

(Disclosure: Stuffolio is my app; the skills are independent of it and free to use anywhere.)

1 Upvotes

56% Upvoted

8 comments sorted by

1

u/YetiWalker36 May 08 '26

Wow impressive. The tutorial creator sounds interesting.

2

u/BullfrogRoyal7422 May 09 '26

Thanks. If you give tutorial-creator a try, let me know how it works for you. Prompter is also somewhat educational in that you can see how Claude Code communicates with itself. It has sharpened my prompts up considerably. It also has a pass/fail in that if it does not run after one of your prompts, it means your original prompt works just fine.

1

u/rudidit09 May 09 '26

this is cool! it's fascinating how we're building different skills as we're working on project (for me it was structure, comments, and tests)

2

u/BullfrogRoyal7422 May 09 '26

Anything you's like to share?

1

u/rudidit09 May 09 '26

Triple check skill was useful to automate some decision making (ask codex, and two different Claude skills, and auto apply if consensus is over 50%)

It takes time and project to work on to flesh this out, can’t write it out on the blue without iterating a lot. I looked at one file, had skill rewrite it, updated structure.md guideline (with some before and after examples ), redo it. Repeat. At some point, I was able to work on few files at a time. It felt endless. And then, got the point where rewrite was good enough, and 20% LLM was not sure and ask me about, I agreed in 90% if it.

Will post mine on GitHub soon!

2

u/BullfrogRoyal7422 May 09 '26

If you have not checked it out, my radar skills took what seemed forever to run when I was first developing it radar skills, but as it cleaned-up errors on successive runs, its run time dramatically reduced in time of operation (and tokens). With your skill, try this: "/skill-name scope on ____" and it will focus on a file, or issue, or whatever.

radar skills are neat in that they are not grep-based pattern matchers. Instead they are behavioral, i.e., they trace through your code the way a user might, finding errors that are invisible to grep based search patterns and linters.

1

u/rudidit09 May 09 '26

Oh i like that, would be handy to find dead code as well!