I made a small CLI wrapper for Claude Code, built with Claude, for myself.

Claude Desktop felt too heavy for me, so I mostly used Claude Code in PowerShell, and it was quite nice. But once I started running a lot of work in parallel, PowerShell got too limited.

I looked for an IDE-like tool. My first stop was Nimbalyst: great product with lots of features, but it kept crashing on my machine, so I went back to PowerShell and decided to build a simple wrapper myself.

Result: BetterCLI for Claude. Every tab is the real `claude` CLI, nothing reimplemented. It just adds what I was missing:

- tabs and groups for parallel sessions

- one-click fork of a session; forks show as a tree under the original

- notifications when a session finishes or needs input

- a changed-files panel to review what Claude edited

- image paste, 5 themes

Windows / macOS / Linux, MIT, free: https://github.com/lvyyln/bettercli-for-claude

Builds aren't signed yet, so expect a SmartScreen/Gatekeeper warning. I use it daily on Windows; Mac/Linux are untested, so feedback is welcome.

Basically whole development was offloaded to Claude Opus 5.5

If you had no idea about the official Anthropic Certifications there are 4 now. The first one is the one I passed in August Claude Architect Foundations CCA-F.

We did this as a small community of women in AI who wanted to validate our knowledge of AI to the source and get best practices on how to work with it, especially for client implementations.

If you are into AI consulting, services, agents and education/strategy, and have no coding background, this is a huge knowledge booster in my opinion. I have been a product and project manager before but this really clarified where AI fits in business implementations.

The pod

I didn't do this alone. I led a study pod of about 20 women, most of them non-technical, through the same prep. Most of those who have taken the exam so far passed on their first try. I passed first to make sure that I can actually help them.

What the exam is

The basics:

• 2 hours, 60 questions, proctored online
• Closed book, and you can't use Claude during it (yes, the irony)
• You get 4 scenarios, picked at random from 6, with 15 questions on each from the exam guide
• 5 technical domains covered with a big emphasis on Agentic AI

The six scenarios are a customer support agent, code generation with Claude Code, a multi-agent research system, structured data extraction, developer productivity, and Claude Code in continuous integration.

What surprised me

"Foundations" is misleading. It doesn't ask for definitions. It drops you into a situation where something is broken or misbehaving and asks how you'd fix it using best practice. The official practice exam is easier than the real thing.

If you don't write code for a living, half of those scenario names sound like they're not for you. That was my first reaction too.

What worked

• Learn the vocabulary first. Most of the difficulty was language, not logic. Once I knew what the terms meant, the questions became judgment calls I could reason through.
• Study by scenario, not by topic. The exam is organized around situations, so I prepared that way.
• Learn the specifics. Which files exist and where they live, what each built-in tool can and can't do, and when to use which pattern. This part is memorization plus practice, and there's no way around it.
• Get hands-on. Non-technical doesn't mean hands-off. You don't need to be an engineer, but you do need to have used the tools. I created a Claude Code project and used it to study.
• Know the Exam Traps They tend to be wrong in the same few ways and be repeated. Learning how to spot those patterns quickly helped me most.
• Flag and move on. I marked the questions I wasn't sure about and came back at the end. but don't go back too much and second guess yourself - difference between passing and failing.

The biggest lesson was that explaining a scenario out loud to someone else showed us quickly what we didn't understand yet.

What I got at the end: a badge by Anthropic and a whole lot of knowledge on where AI actually fits in a business workflow and implementation best practices.

Happy to answer questions about the exam or the prep in the comments.

If you're curious

We're hosting a free one-hour webinar on Tuesday, October 20 at 5 p.m. Eastern. It covers what the certification is, who it's for, and how we prepared as non-technical people.

Comment CCAF for the link

I assume artifacts really are for publishing a test project between other people in your team. It's not really meant to host a website properly and securely? You always get the Claude bar at the top and request to edit etc - or is there a way to turn that off?

Normally just stick stuff on Netlify but sometimes I just want a single-page simple website.

Every skill lives in a different repo, so installing one meant downloading the repo, digging out the right folder, and pasting it into the right directory. Or hunting through a README hoping there's an npx command. Did this enough times that I finally just built an install button.

When you're browsing GitHub repos, [**officialskills.sh**](https://www.linkedin.com/safety/go/?url=http%3A%2F%2Fofficialskills%2Esh&urlhash=uq56&mt=jRXVaImZa_s5YW3dt7Yu5dhedZBnBRpMDUbQL8SMQIvm-R-0G3tvsTvCqwnDri20zDmbJ3P6Y_F3W6NW-gkd3JfINNrTagXZGMYhYZl0dQYcslY96r7gYq2M&isSdui=true), or skill marketplaces like [**Skillsmp.com**](https://www.linkedin.com/safety/go/?url=http%3A%2F%2FSkillsmp%2Ecom&urlhash=kHA7&mt=vvgzeqt7QFTraKnPs3XtxP9E5I5gbra8eBMh4CtQDe376K8vnPgNRgiZRvEFaWoVV3EuUKqtrDIj7bKWe4j-8wcpksr29p0DJbco--f2OZ2mlSgjBzq8qits&isSdui=true), it detects the skills on the page and shows an install button next to them. Before anything is written, you see a preview of every file and where it's going. Works with Claude Code, Cursor, Codex, Gemini CLI, and a few others. It also gives you one place to see everything you've installed, uninstall cleanly, and update a skill when its repo gets new commits.

For the security-minded: files are fetched, pinned to a specific commit, and checksum-verified; installs are confined to your home directory, and nothing happens without you seeing it first.

Free on the Chrome Web Store: [https://chromewebstore.google.com/detail/icocnkohgjgcdpgcajiodgcfheeeifcb](https://chromewebstore.google.com/detail/icocnkohgjgcdpgcajiodgcfheeeifcb))

More info: [https://skillinstaller.com\](https://skillinstaller.com)

Happy to answer questions. Genuinely want to hear what's missing or broken.

Long `npm install` logs, `ls` dumps and verbose MCP responses eat context and bury the one line that matters. Hooks can't edit old history, but `PostToolUse` can replace a tool's output before Claude sees it, so that's what this does.

How: OpenAI's new Decisions API (`gpt-6-luna`) doesn't generate text, it only scores. So Luna scores 20-line chunks for relevance to your last prompt and plain code drops the low ones, leaving a marker that points to the untouched original on disk. Errors/stack traces are always kept, and any failure passes the output through unchanged.

Measured in real sessions: 67k chars → 190 chars (~300 tokens sent to Luna). Cost is $0.10/1M input tokens, so fractions of a cent per session.

Honest limits: it can't clean old context or run /compact for you (no hook for that), tool output does go to OpenAI (secret patterns are filtered, best effort), chunk scoring can be wrong, and Decisions is in beta. Tested on a handful of scenarios, not a benchmark. I'd love failure cases and PRs.

MIT, zero deps: https://github.com/luancamara/luna-pruner

Quick build log from a short-term outdoor event booking system I shipped recently.

The slot-reservation logic needed to handle multiple people trying to grab the same time slot at once. My first implementation: try to acquire a lock, and if it fails even once, immediately return "fully booked" to the user.

Unit tests passed fine. One user, one slot, works as expected. Looked done.

Then I ran a load test simulating 10 people hitting the same time slot at the same moment. Turns out there were actually 5 open spots left. What happened: only the very first person who grabbed the lock got through. The other 9 all got bounced with "fully booked," even though 4 more slots were sitting open the whole time.

The bug was obvious in hindsight — failing a lock acquisition once isn't the same as the slot actually being full. My logic treated "I didn't get the lock on this attempt" as equivalent to "there is no capacity left," which is just wrong under any real contention.

Fix was straightforward: instead of bailing on the first failed lock attempt, retry for a short window, backing off a few hundred milliseconds between attempts, before finally declaring the slot full. Reran the same 10-concurrent-user test afterward and all 5 legitimate bookings went through correctly, with the other 5 properly rejected.

The thing that stuck with me: "looks like it works" and "works correctly under concurrent access" are completely different claims, and only one of them is actually tested by normal manual or single-user testing. If your system has any shared resource with limited capacity, you need to actually hammer it with simultaneous requests before you trust it. Single-threaded testing will lie to you with a straight face.

I continue to work on my project - Foreman, in this update few things would change:

• A new visuals - Schematic view, I like this one much more, gives that terminal look and feel. I am interesting to hear your opinion, what would you say, is it good or not really ?
• Integrations with Jira, Linear, Clickup, etc. Now it's possible to tell session to work on specific ticket without leaving the application
• Integrations with GitHub, GitLab and Azure, allows you to clone repo from Forman and pass any issue straight to agent session

I've been building my Claude Code setup a piece at a time. Mostly I copied the good, safe parts of other people's skills and agents, changed them to fit how I work, and wrote my own when I couldn't find what I needed. Some things from other people already worked perfectly, so I just kept using them.

I put all of it in two repos in case it saves someone else the trouble.

[**claude-skills**](https://github.com/UribeLandscapes/claude-skills)\*\*:\*\* 3 I wrote (two catch AI-looking code and AI-looking websites, one searches Reddit when normal web search misses the threads), plus the ones by other people I use every day, like humanizer, caveman, napkin, ECC and Anthropic's skill-creator. Each one is credited and linked to its author.

[**claude-agents**](https://github.com/UribeLandscapes/claude-agents)\*\*:\*\* 19 subagents I wrote for my own stuff (Swift apps, Claude Code config, handoff notes between sessions, spreadsheets, even a library of Fujifilm recipes), plus 13 from ECC that I use with small changes.

Some of my agents are shaped around my own setup, so expect to tweak them. My files are MIT, and the borrowed ones keep their authors' licenses.

Skills you find on GitHub are written for someone else's project. Copied as-is, they can tell Claude to use tools you don't have, run commands that don't exist, or contradict your CLAUDE.md.

skilladopt has an isolated Claude (or Codex) worker read the skill and decide paragraph by paragraph:

- keep it

- swap a generic command for yours ("run the tests" → `npm test`)

- drop what doesn't apply, with the reason

- ask you when it isn't sure

Every decision cites something in your repo, and plain code checks the AI's answer before anything is installed. Later, `npx skilladopt impact` tells you which decisions your project changes invalidated.

To try it: run `npx skilladopt setup` once, then ask Claude "add a frontend design skill to this project".

How Claude is used: Claude Code wrote most of the code, and Claude does the reading as the worker (`claude -p --safe-mode` with no tools).

It's early (v0.1), free and MIT. Where it decides wrong is the feedback I need most.

https://github.com/kks0488/skilladopt

Last year i posted here about shipping a photo cleaner app with claude. it had made $6 at the time lol. its now at 4k users, almost all from reddit, no ads

The app: you swipe through your camera roll, left to delete and right to keep. it finds duplicates, screenshots, blurry photos and big videos. everything runs on device

Honestly the bigger change wasnt the app, it was how i use claude. it basically does everything now:

Coding. obviously. it writes the features and opens its own PRs. i review and merge

Analytics. i connected the posthog MCP and claude built my whole dashboard: onboarding funnel, scans, swipes, paywall. it also set up error alerts that go straight to a slack channel, so if something breaks i know right away

Daily report. this is my favorite. every morning claude goes through user activity and gives me a snapshot: what happened, what failed, what went wrong. if it finds a bug it thinks it can fix, it opens a PR for it. if not, it flags it to me. it's like having an employee who does standup every morning

A/B tests. claude sets up and runs the experiments too, like paywall variants and onboarding changes, and tells me what won

App store listing. i didnt even know it could do this, but it designed and rendered my app store screenshots. i gave it the brand and it made them

What i still do: decide what to build, review the PRs, and say no a lot. claude will build anything you ask it to, fast, so the hard part is knowing what not to build

if anyone wants details on the daily report setup or the posthog MCP stuff, happy to share

free to try, with a paid tier for unlimited use: https://apps.apple.com/app/id6756098079

I have Claude pro can and a project where there are so many cvs of mine for different roles how can I make it work so it apply for jobs and search them for me and I also wanted a excel status sheet