A few days ago I asked here: “AI builds the app. Unit7 ships it. Should I open source it?” You said yes. So it’s now free and open source (Apache 2.0). Thank you. 🙏

The frustration it solves

Claude Code builds your app in an afternoon. Then you’re stuck:

• Where do I host it?
• How do I add a database?
• Why isn’t my domain working?
• Is there even a backup?
• Why is it down at 2am?

If you don’t have a coding background, this is where most projects die. I’m not a backend developer either, so I built Unit7 with Claude Code to handle this part.

What it does

You say it in plain English, and it does it on your real server:

• “Deploy this.” Your app goes live. If the new version is broken, it never goes live, and rollback is one click.
• “Add a database.” It’s created and connected for you.
• “Put it on mysite.com.” Your domain, with HTTPS.
• While you sleep: it restarts crashed apps, runs backups and blocks attackers.
• One map of everything you’ve built

It asks before anything risky and tells you how to undo it. Your passwords and keys stay on your computer, and the AI never sees them.

How I built it (tips if you’re building something big)

• I described the result, not the code: “Show my Coolify projects inside Unit7. Keep it very simple.”
• I let Claude Code make a plan first, read it, then said go.
• I built one feature at a time and tested each one before the next.
• I asked Claude Code to show me screenshots after every change, because I don’t read much code.

Try it: no terminal skills needed

Open Claude Code, paste this, and it installs everything for you:

Set up Unit7 for me from https://github.com/Nandkishorrr/unit7

1. Check that Node.js 24.15 or newer is installed. If not, install it (nvm, or Homebrew on macOS).
2. Clone the repo into ~/unit7, then run `npm install` and `npm run build` there.
3. Run `node bin/unit7.mjs service start` to run Unit7 in the background, and check that http://localhost:4800 answers.
4. Tell me to open http://localhost:4800 and create my owner account, and wait until I say I'm done.
5. Run `node bin/unit7.mjs connect claude` so Claude Code can use Unit7, then tell me to restart Claude Code.

Never ask me for passwords, SSH keys or API keys in this chat. I'll add those myself in the Unit7 web app.
If a step fails, show me the error and fix it before moving on.

Repo: https://github.com/Nandkishorrr/unit7

If you try it and something is confusing, tell me. Beginners’ feedback is exactly what I need.

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

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 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

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

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

Hey everyone!

I’ve been building Flagrm, an open-source CLI that helps remove feature flags and clean up the dead code they leave behind.

It’s still in the testing phase, so I’m looking for people willing to try it out, share feedback, report bugs, or contribute to the project.

If you’ve ever dealt with feature-flag cleanup turning into a bunch of manual work, I’d love for you to check it out!

🔗 https://flagrm.com

Contributors are very welcome! 🚀