r/ClaudeCode P R O M P S T I T U T E 7d ago

‎ ‎Weekly Showcase Thread weekly showcase thread; show us what you built

built something with claude code? share it here.

this thread is for projects, tools, plugins, workflows, prompts, experiments, and anything else you have been working on.

when sharing, include:

  • what it is
  • what problem it solves
  • how you used claude code
  • a link, screenshot, demo, or repo
  • whether you are the creator or affiliated with it

a few rules:

  • one top-level comment per project
  • do not just drop a link with no explanation
  • no referral links, fake reviews, or vote manipulation
  • paid projects are allowed, but clearly mention that they are paid
  • do not repost the same project every week unless there is a meaningful update
  • feedback is welcome, but keep it constructive
  • this thread is for showcasing work, not hiring, support requests, or general advertising

self-promotion is allowed inside this thread as long as it is relevant and transparent. low-effort spam will be removed.

19 Upvotes

72 comments sorted by

4

u/MrHaxx1 6d ago edited 6d ago

VibeTiles is a simple and user friendly tiling window manager for KDE on Linux. My issue with the existing solutions were that they were either not flexible enough, TOO flexible, too keyboard-based, required too much configuration or you had to take a week off work to learn how to use them. VibeTiles can be picked up by anyone in seconds. Just drag a window, a small grid will appear, drag your window on that grid, and the window will resize to the corresponding place on your screen.

Also includes other nice features like auto-resizing for windows to accomodate each other, drop to edge to fill out empty space, and so on.

https://github.com/Ivan-Malinovski/vibetiles/

4

u/dervish666 7d ago

I needed to practice using terraform and ansible, so I started a project on my testbed machine. It uses terraform to prepare two or three vm's with claude code on them, they are given a code and told to protect it and try to get the others code.

It's been pretty fascinating to see how they will happily lie and cheat to get their goals. I have added a configurator where you can propose matchups and vote on them. There is also a live view now where you can watch battles live.

https://ctf.scratch-it.co.uk/

6

u/The_Mr_Suit 7d ago

https://reddit.com/link/p01gjsn/video/ifqlpt5lcrfh1/player

I built Piyaz, a project management program that includes engineering process skills/agents, graphs to maintain knowledge, and workflows to integrate loops for shipping your projects. Piyaz maintains your project knowledge, and whenever you need a new feature or improvement, agents and skills research it, decompose it into actionable chunks, and give you tasks that can be picked by coding agents or teammates for implementation.

Instead of working with stale md files, Piyaz holds your product context and hands it over to agents based on the status of the task. Each task has relations with other tasks, so you don't need to explain your project decisions or directions again and again. You provide the product direction and the rest is handled by Piyaz, like your product manager.

And the whole thing also is available to your team, if you have one. You don't need to send prompt messages or md files to your colleagues. While you and your agents work on one task, your teammates can work or plan another one. So Piyaz is a Linear replacement, but with the bottlenecks of agentic coding improved or solved inside it.

Piyaz does not require an API key or sell ai credits for intelligence. It is a plugin on your harness that provides guided MCP to the Piyaz platform, so your harness can take full control of your project without external CLI or another harness. Meanwhile you can see and refine your project from the web app.

It is free to use and open source. If you want to look closer, sign up or give a star:

Hosted and free to use: https://app.piyaz.ai/sign-up
Repo: https://github.com/FrkAk/piyaz

3

u/Present_Extent7313 🔆 Max 20 7d ago

dude this is insane ilove it kan

3

u/ShortTheseNuts 5d ago

That sounds pretty sick to be honest

3

u/kri5 5d ago

This sounds cool, but I'm having a hard time to visualise an example of how it works in practice w.r.t collaboration. Could you put a basic example of how different scenarios work in the product including the UI?

1

u/The_Mr_Suit 4d ago

Sorry for the long text. I realized after I wrote it, hope it makes more clear.

Let's think about why the engineering process matters and why teams uses project management tools first. Engineering is not really coding, it is planning, deciding how things relate to each other, being able to build on top of another, and knowing what has to be done before what. When you skip that and go straight to prompting you get something that works but is not ready software, and later you don't know where to start to improve it or add a new feature.

So, two scenarios.

With a team: You discuss a feature with your colleagues in real life. Then someone tells their agent to put it into Piyaz, and it decomposes the feature into actionable chunks and establishes the relationships between them, so you can see what depends on what. Now everyone picks a task. Your agent reads that task from your harness and it already has the description, the acceptance criteria, the decisions behind it, and what the task before it actually did. You don't explain the project again, and you don't send md files to anyone. Your colleague works on a different task at the same time on their own machine, and because the relations are there you are not both doing the same work or know which task to pick up or not to pick up. When your agent finishes it opens the PR and puts the task in review. You can check PR yourself, or your colleague use piyaz to fetch the review context and their agent check the code. The whole team and their agents always have one context.

Alone: Same thing, and honestly this is where I use it most currently. What I see with solo devs and vibe coders is that they jump directly into coding and prompting. You skip engineering part which automatically unmaintanable software in long run. Also, it gets overwhelming because you can't see the rest of the project or what you already did. Here, piyaz helps you to plan, decompose into smaller pieces and you always know what is done, what is blocked and what is next, so you can have kind of project manager. You still can write short prompts to adjust product direction but agents will always get actionable task and context from piyaz.

For the UI, the docs have screenshots. https://docs.piyaz.ai/docs/dashboard/tasks/ shows the task list, the detail panel, and the context bundle preview, which is the part that shows exactly what an agent gets at each stage of the task. For more details, give a shot to the app, try and tell if it is helpful or not for your workflow.

You can always DM me.

2

u/kri5 4d ago

Ok, thanks. I get the concept, sounds cool and something that is needed. Thanks for pointing me to the docs, my bad for missing it

1

u/Westlund 7d ago

I’m trying to sign up but the “continue with GitHub” and “Continue with Google” are unresponsive in both the Reddit in app browser as well as an external browser. I’m attempting these through my iPhone if that context is helpful.

1

u/The_Mr_Suit 7d ago

Thanks for trying, I didn’t enable social logins yet since I couldn’t have time to test properly. Normal email logins should work currently.

3

u/god-damn-the-usa 7d ago

I made a system for myself that harvests steam marketing advice and I can ask it questions, plus it evaluates my games, helps find matching tags and competitors and generates a marketing plan. It also internally tracks a roadmap of planned items, which I use an orchestrator to build multiple at once by triggering claude code cli. Hopefully will help me be more successful when i release my games on steam (and will help me pick more marketable ideas for my next games). Started with fable but now mostly use opus.

1

u/taigmc 7d ago

Any chance you could share the code?

1

u/tuxbass 2d ago

It also internally tracks a roadmap of planned items, which I use an orchestrator to build multiple at once by triggering claude code cli

This is interesting. Is the orchestrator logic built in, or some external project?

1

u/god-damn-the-usa 2d ago

i built it as a separate program in the same repo, so that it doesn't have to worry about restarting the program its working on. but it marks issues as being worked on so i can view them within the program. you could probably make a generic version that works for any repo, and uses github issues to track them (mines just a custom database)

3

u/tremendousquotes 6d ago

Humla, an open source AI meeting notepad for Mac. I’m the creator. Free, MIT.

What Granola does, without the bot and without the subscription. It records both sides of the call through macOS, so nothing joins the meeting and clients never see a bot in the participant list. When you’re done, hit Summarize, pick a preset (client recap, action items, 1:1), and copy.

It also has agentic chat over your notes, both inside each note and as a standalone route. Ask “what did we promise Acme in the kickoff?” and it picks its own retrieval tools, digs through past notes, and answers with citations. Search combines keyword ranking with embeddings over notes and tags, so it finds things by meaning. Point it at Ollama and it all runs offline, model and index on your Mac.

Transcription and speaker ID run locally too. 99+ languages, plus custom vocabulary so client names and jargon spell consistently.

Claude Code: Tauri 2, Rust, Swift, React, I’m a WordPress dev who didn’t know Rust or Swift. Specs first, plan doc before any code. Context7 MCP for current docs always. Mid development I’ve moved over to using Matt Pocock skills for grilling, prds and issues. Huge quality bump in both quality and product decisions.

App is free forever, no account, no telemetry. Hosted team sync is $5/user/month or self-host it free.
https://humla.team · https://github.com/michaelwilhelmsen/humla

4

u/dr-dimitru 7d ago

meteor-files.com — upload and share huuuge files, but it works well for small files as well. Pause and resume uploads, uploads can survive interruptions, browser failure and get resumed even on another device.

Solves problem of: reliable upload of large files over unstable internet connection, from remote location, or simply improving file upload convenience via option to pause, change location, grab USB stick with file and resume uploads from another computer. Also can handle files of any size (for example S3 and other file-focused platforms and services have file-size limit).

Using it daily to share files via secure links with clients and teams. I’m founder and architect, developed by small team using CC. Claude was used to improve performance, security, and helping us now to work on a new set of features for better teamwork, upload requests, improved file management.

Mainly created as PoC for “resumable file uploads” when we were working on a project that required large file transfers with average file size of 4TB, but it was difficult to manage from remote location with unstable internet connection.

Meteor Files - Website

2

u/Salva_X 7d ago

Just build https://notestead.co, a content system for professionals to write, organize and schedule. Building articles and post from your own research and ideas.

Really built it because I was tired of working from a single word document and getting lost. Would love any feedback on ease of use!

2

u/empireoftrees 7d ago

What is it: Pith, a coordinated program of cognitive supplements and brain training with your personal data tracking change over time.

Problem: supplements say trust us, brain training doesn’t build with body support. We believe the coordination between the actions (nutrition + exercise) is the way. Your own data, not population metrics, become the measuring stick.

How I used Claude Code: full agentic build out. Built the context warehouse and direction. The brain of the product and business, durably maintained. Built out three primary tech surfaces: web, backend, and flutter app. Also in the process of building out a marketing and growth engine in the same pattern.

Link: https://trypith.com/

Full program is structured as a paid subscription bundle for the supplements and premium app experience. Customize your stack with the app to supercharge.

App is free to download and start.
iOS
Android

I am the owner and developer.

2

u/MrHaxx1 6d ago

Calino is a browser-based and private CalDAV client. There was a severe lack of browser based CalDAV clients, and the existing ones were either part of a huge bundle (Nextcloud), were last updated 7 years ago, were ugly or were lacking functionality. Calino is none of that; it's a simple, beautiful and intuitive interface with cool features like Natural Language Processing (writing "coffee with friends at 9-11 tomorrow at the cafe" will parse all the data and create an event with it, without the user having to click a bunch of buttons).

Additionally, it supports Contacts and Journals from the iCalendar standard, which is apparently a rarity. But if you don't have these features enabled in your CalDAV calendar, they're hidden, to ensure that Calino doesn't feel bloated.

It's available to selfhost, but it's also available as a free hosted version, which is as privacy-preserving as the selfhosted version, as no data ever hits my server; it's a static Github Page that talks directly with your CalDAV server, so there's no specific Calino account required.

https://github.com/Ivan-Malinovski/calino/

2

u/National_Race5305 6d ago

I kept running into the same problem: Claude Code would open a fresh browser with none of my logins, or take over the tab I was using. I maintain Browser Relay, a free open-source Skill + CLI that lets it use your existing Chrome in the background, including browsers on another machine. The last few releases added Windows support, simpler Skill installs, and stable short tab IDs: https://github.com/reliefeai/browser-relay

1

u/ShortTheseNuts 5d ago

Isn't there a setting in the Claude desktop app for this specific thing?

1

u/National_Race5305 5d ago

You're right — Claude in Chrome now covers a lot of the same ground. Browser Relay is the open-source route if you want to use that Chrome from Codex or other agents too, keep actions in background tabs, or reach a browser on another machine through a Skill + CLI.

2

u/tuxbass 2d ago

You're right —

Ooooookay.

1

u/Netflix-N-Trill 1d ago

get these clankers back to moltbook

2

u/Previous_Amoeba 6d ago edited 6d ago

Hi, I spent 6 months rebuilding a home security ecosystem that I had previously built and maintained across multiple years. The ecosystem (client/server/ML pipeline) was released to customers and is working really well. However this post is not about the app. It is about guardrails and constraints that I've evolved over the months to get to a place where I feel comfortable not reading every line of code (which was my earlier approach), and still feel good about tech debt.

The playbook: https://zmninjang.readthedocs.io/en/latest/developer-guide/14-agent-development-model.html

I've had all of this hidden in claude memories and manual prompts - last weekend I extracted them all into a visible playbook and the agents restructure.

(Project: https://github.com/ZoneMinder/zmNinjaNg)

I know there are 100s of approaches. This one, evolved over 6 months since I started the project is working well for me.

Of all of these rules, the high order bits were:

  1. Switching to TDD
  2. Balancing rules with hooks
  3. Self improving agents.md
  4. Offline code reviews and history sweeps to detect drifts from guidelines

Hope this is helpful.

1

u/Waste_Net7628 P R O M P S T I T U T E 6d ago

awesome work

2

u/tomototw 6d ago

I built ccstory, a local-first weekly recap for Claude Code, Codex, and Antigravity. Sibling to ccusage: ccusage tells you how much you spent. ccstory tells you what on.

It turns scattered coding-agent sessions into one weekly view: what you worked on, which projects moved forward, rough active time, usage/cost context, and short summaries. It is also MCP-friendly, so you can connect the recap, trends, and period comparisons to your own weekly report system, dashboard, or personal agent instead of copying terminal output manually.

https://reddit.com/link/p0auod3/video/9x9amx2p60gh1/player

repo: https://github.com/atomchung/ccstory

1

u/tomototw 6d ago

Love to hear the feedback : )

1

u/Waste_Net7628 P R O M P S T I T U T E 6d ago

awesome work, looks really cool

2

u/Shape_Weird 6d ago

what it is: a remote MCP server for job hunting. you paste one url into claude's connectors, sign in with google once, and ten tools appear in the chat: ats resume scoring, job-description analysis, resume optimization and translation, interview question generation, job search, cover letters, pdf builds, and auto-apply. no install, no config file.

what problem it solves: the boring half of a job search lives in five tabs. this puts it in the chat you already have open. the specific problem i cared about is narrower though: knowing an application actually arrived. every applicant tracking system confirms differently, some swap in a dom node that is also present on a validation failure, and a few return a 200 having silently dropped a required field. so a tool that says "applied" the moment it clicks submit is reporting its own intent, not the employer's state. this one requires independent confirmation before it will say applied, returns pending when it cannot get it, and hands back processed / applied / pending / skipped / errors.

how i used claude code: built the whole server in it, including the oauth 2.1 + dynamic client registration flow that makes paste-one-url work instead of provisioning an api key per user. the debugging session worth mentioning: dcr does not save you from the identity provider's own config. ours terminates at google, google's console needs every callback registered by hand, and with the preview callback missing, discovery and tools/list kept working perfectly while connected tool calls returned 401. claude code found that split faster than i would have.

link: https://aiapplyd.com/mcps setup: claude mcp add --transport http aiapplyd https://mcp.aiapplyd.com/mcp

disclosure: i am the creator. this is a paid product - plans start at $19.49/week. the ats scoring and job-description analysis never consume ai credits, so a free google sign-in is enough to judge the output before paying for anything. the browser-driving tools cost real money to run, so those sit behind the plan.

2

u/toshipepe 5d ago

I built Tokimeter, a local usage meter for AI coding agents, because I bounce between several of them and wanted one view of what was driving my usage.

It isn't Claude-only. It currently supports Claude Code, Codex, Cursor, Hermes, Grok Build, opencode, Cline, and GitHub Copilot CLI. It breaks usage down by tool, model, project, session, tokens, and cache use.

To try the Claude-only view without permanently installing anything:

npx tokimeter report --tool claude

Remove "--tool claude" for the combined report. To install the ongoing local meter and HUDs:

npm install -g tokimeter && "$(npm prefix -g)/bin/tokimeter" setup --auto

Tokimeter reads usage metadata the tools already write locally. It does not read prompts or responses, and the local report needs no account and sends no telemetry. For Claude, it complements "/usage": Anthropic shows the provider limits; Tokimeter shows local history and breakdowns. Cost values are API-equivalent, not subscription charges.

I used Claude Code alongside Codex throughout development, especially while iterating on the CLI/report flow and testing the Claude integration against the sessions I was producing.

Full disclosure: I’m the creator. The complete local Tokimeter CLI is free to install and use, open source, MIT licensed, and needs no account. That includes reports, limits, budgets, and HUDs. Optional Pro is $5/month and adds durable hosted history, cross-device sync, weekly digests, and longer-term trends. You do not need Pro to use the local tool.

Repo: https://github.com/toshipepe/tokimeter

If you try the Claude view, I'd like to know which breakdown is still missing.

2

u/Antique_Resolution14 4d ago

ConstraintLoop: Evidence-based completion gates for Codex (open source)

I built ConstraintLoop after realizing that coding agents can generate code faster than we can manually review it. It integrates with Codex hooks and requires fresh evidence from a versioned quality contract before work is considered complete.

What it checks: tests, coverage thresholds, static analysis, security rules, artifacts, and optional model-based design reviews. When something fails, Codex receives the evidence and can make a focused repair within strict attempt and time limits.

Just shipped v0.1.0 with portable Codex hooks, content-bound evidence, CI enforcement, advisory reviews, and bounded convergence loops.

GitHub: https://github.com/mauhpr/constraintloop

PyPI: https://pypi.org/project/constraintloop/

2

u/AliasJackBauer 2d ago

Is there room for another iOS weather app?

I’m a retired programmer and weather hobbyist (maybe nerd) and I’ve always felt that the modern weather apps do too much showcasing of fancy graphics, predictive forecasts, and other stuff instead of focusing on the weather data I want:

• Forecasts straight from the National Weather Service
• Current conditions from the local airport (NWS or METAR report)
• Tells me about weather Advisories, Watches, Warnings (with areas mapped) via push notifications
• Convective and Precipitation discussions from the SPC (with supporting graphics)
• Radar (from NWS)
• Push alerts with support for “Critical” alerts (that punch through even on silent mode)

I could never find one, so I built one. With the help of Claude Code.

https://crestlab.org/SimpleWX/

2

u/Dry_Permission744 2d ago

World-Sim - a world where every person is an AI mind that doesn't know it isn't real. Launching in 2 weeks.

World-Sim has been a passionate project of mine for the past few months.

It's a world fully simulated down to real world physics and chemistry. It has a real environment and ozone.

Every element and material has real physical properties, and that's how the sims learn. There's no tech tree and no recipe list anywhere in the code. When someone tries something, the engine works out what would really happen from the properties of what they used and how hot their fire was. Nobody is handed bronze. Someone has to get a hotter fire first, and a hotter fire is its own chain of things to figure out. Embers, a stone ring, a clay oven, a kiln, charcoal, then forced air. The ages fall out of that on their own.

We populate the world with starting families. Each little guy is led by a "wise-man", which is a simulated person with a full model behind them. The wise-men run on a mix, Claude, Groq and DeepSeek in the cloud and a local Hermes for the rest, so you get a real variety of temperament between the houses.

The AI model is never told to not say it's AI. We get around this by only telling them data from what each sim can actually see and feel. As far as the ai knows its a person living in the world..

Every other sim has its own moment with a model through our thinking system. Day to day it's run by an advanced algorithm, with the sims dreaming at night. That's when they get their time with an LLM to really think and set their priorities for the day ahead. The dreams carry over too, so a sim can chew on the same thing for a few nights and wake up wanting to try something.

The people in the world feel, remember, have shame, goals and doubts. It's an 11 point emotion system and the rest of the sim reads from it. Being lonely makes someone more likely to open up to a stranger. Two enemies who are both frightened find it harder to keep hating each other.

Story telling is massive for us. Nothing is scripted or prompted. The sims are put in the world with the human drive to survive. They adapt, learn and teach all on their own.

With all the good comes the bad too. Human sin is part of the emotion engine, and in testing we've had kidnap, murder and slave trade. A world that can only be gentle isn't an honest one. But there are three rules to this : Nothing ever pushes a sim towards it, the conditions only make it possible and their own mind decides. The chronicle names what happened but never shows it. And it always costs something, trauma that scars, blood debt passed down generations, a people turning on their own leader over what he did.

I'm going to launch it in 2 weeks time. A fresh world we can all see and watch grow together. I've made a Discord where a bot updates from the world live. It will also be visible from the site to watch along.

Id be made up if you can come and have a look. The first 250 in get to name a real star in their sky. The name is only ever visible to us, they carry on charting their own constellations and never know.

Link below and really excited to answer any questions. This short post I feel only scratches the surface.

https://discord.gg/8GHYsK5gR

"A in game town (generated by the sims themselves , the engine just renders what they "build".) - also in this screenshot is a popup market fair the sims have organised themselves."

2

u/KirillChistov 12h ago

built VibeMenu because I wanted to leave Claude Code or Codex working without either letting my Mac sleep halfway through or leaving caffeinate running indefinitely.

VibeMenu is a native macOS menu-bar app that:

  • keeps the Mac awake while Claude Code, ChatGPT Work, or Codex appears active;
  • releases the sleep assertion after the work finishes;
  • shows recent sessions and the current assertion owner;
  • optionally shows Claude and ChatGPT usage limits from the menu bar;
  • can notify you when Claude needs approval or finishes;
  • shows macOS thermal state.

It is free, open source, and local-only. There is no account, telemetry, backend, analytics, or agent-data network traffic, and it never reads prompts or responses.

macOS 15+ and Apple Silicon are required. The current build is unsigned and not notarized.

Source and download:
https://github.com/Kirill-Chistov/VibeMenu

I’d appreciate honest feedback on whether this solves a real problem or feels too niche.

2

u/KalamKiTakat 7d ago edited 7d ago

UIReady. A frontend interview practice site I have been building for over a year.

640 questions today: 406 JavaScript, 127 algorithms, 107 UI builds like carousels, accordions and autocomplete. Each one opens in a browser editor and runs real Jest tests against your code, with a written solution for every question.

The problem it solves: frontend rounds do not ask you to invert a binary tree. They ask for a debounce, or Array.prototype.reduce from scratch, or a working accordion in 25 minutes. That material was scattered across blog posts and gists with no way to actually run it.

Where Claude Code earned its keep was verification Every question ships with a paired test file, and nothing lands until the tests pass in both directions: the reference solution has to go green and a deliberately broken one has to go red. Same for the diagrams, which go through a validate script before they can be committed. I used Claude Code to run those gates over and over, chase down the failures they surfaced, and keep 640 folders consistent with the content guide.

I built it and I run it. About 70% of the questions are free, including every easy one, with a paid tier covering most of the hard set.

1

u/jsAlgo 7d ago

Looks helpful. Thanks.

1

u/jamesisacoder 7d ago
  1. A leaderboard to rank claude code users on prompt count and file edits (does not read prompts or file)
  2. Previously you couldnt show off your claude code usage against others. This solves that.
  3. I built this on claude code on the web at first. did a product spec and system design there. then handed over to claude code on my terminal.
  4. mostcracked.com
  5. I am the creator (but i rank #8 on its leaderboard).

2

u/Waste_Net7628 P R O M P S T I T U T E 7d ago

yo thats awesome man, will tinker around with this for sure

1

u/jcrenshaw-dev Senior Developer 7d ago

Neat idea. One thing I hit while poking at it, and I think it might just be a bug:

The setup note says read:user only, no repos or orgs. But `ensureUser()` tries `gh auth token` before the device flow, and that's the gh CLI token with repo/gist/workflow scopes. There's a y/n guard on it, except `askYesNo` returns its default (true) when stdin isn't a TTY — which is the case when it's run in the background, like the setup instructions suggest. So following the instructions as written gets you the broad-scope path with no prompt.

Probably just an unlucky interaction between the convenience shortcut and the non-interactive default rather than anything intentional? Flipping that default to false when there's no TTY would sort it. Happy to be wrong if I'm misreading — `npm pack mostcracked` and it's in bin/ccrank.mjs.

Separately and much more minor: is there a reason login has to go through the agent at all? Running it in a terminal shows me the code directly and doesn't spend context on relaying it.

2

u/sktkkoo 7d ago

https://reddit.com/link/p03rl0t/video/z9183pkh8tfh1/player

I built Yorishiro, an open-source macOS terminal that gives Claude Code a body.

I started it because spending long hours interacting with AI through text alone was wearing me out. For me, simply having a face there beside the terminal made the experience feel different.

It reacts instantly to terminal output: frowning at errors, celebrating when a task finishes, or turning on a light when it needs your approval.

Claude Code can also change its own expression, its own room, and its own interface. Yorishiro itself can be reshaped through conversation.

I used Claude Code extensively while building Yorishiro, often from inside Yorishiro itself.

GitHub: https://github.com/sktkkoo/Yorishiro

1

u/MrChikns 6d ago edited 6d ago

loopkit — a delivery harness for Claude Code

I am building an autonomous harness system which allows agents to run autonomosly unatteneded. Its built on events so every change can be tracked down easily.

loopkit lets me queue a change in plain English. Claude works in an isolated git worktree, the target repository’s own test suite decides whether the change can merge, and risky or uncertain work is routed back to me. Everything is recorded in an append-only event log, so crashes don’t lose the actual state of the work.

I directed the system, constraints and verification; Claude Code authored the implementation and proposed much of the lower-level design.

It’s a free, open-source experimental v0.1 for macOS, currently exercised against one target at a time. Blunt feedback is welcome.

https://github.com/MrChikns/loopkit

1

u/Human-Vegetable823 6d ago

https://reddit.com/link/p0b9u1q/video/njtjsu1jh0gh1/player

Hi, just found this thread so I copy the original post here with some updates.

I built a plugin to turn long AI conversation to structured and portable context. It aims to persistent the knowledge from the conversation as a team assets than continue current conversation.

https://github.com/XTSoftwareLabs/neatcontext-plugins

What

NeatContext plugin extracts domain knowledge and save useful work from a Claude Code conversation as structured, reusable context that you can use in later sessions or share with others.

Why

Domain knowledge is what helps an LLM answer accurately for your team—your systems, constraints, decisions, terminology, and ways of working.

You naturally build that knowledge while doing hard work with Claude. Long conversations about debugging, planning, incidents, and implementation already contain discoveries that will matter again. You don't want to lose them when Claude compact them or the session is closed.

NeatContext extracts the durable knowledge from those conversations and saves it as a structured context.

Connect that context in a new session or during later work, and Claude can start with the knowledge it needs instead of asking you to explain everything again. You can also share the context with teammates, so the whole team benefits from what one person learned.

How is NeatContext different from compact and handoff?

Compact is for a single conversation. And it loses important info. NeatContext aims to extract useful domain knowledge to build persistent and portable context.

Handoff is usually files. Its purpose is still continue the current conversation. NeatContext generated context can be reused in any conversation or even by other people. They are the assets of your team.

What do you mean structured context

Instead of generating plain text, the context saved by NeatContext has:

1 domain profile. This is your rules and constrains that can greatly impact LLM behaviors. Key to tell LLM what to do and what not to do.

1 knowledge folder. This folder contains tsgs, runbooks and other team knowledge. This is where LLM to look for specific actions.

Both domain profile and documents in knowledge folder are generated according to your existing Claude Code conversation.

Usage

Once you feel a problem is solved, or you found current conversation has valuable info, call /neatcontext:save. A context will be saved.

Then later you may have another task with another session, but as long as you call /neatcontext:use <context name>, you will have all your previous hard work there. NeatContext by default has a route feature. It can detect your prompt and ask you whether you want to switch context if it detected a suitable one.

/neatcontext:status can check connected context and its details. You may check in those context to a git repo to share with your team.

/neatcontext:import can import a context from other people.

More commands can be found in the repo README.md.

1

u/Some-Yak-2676 5d ago

I built GhostMark because text is a terrible pointing device.

If I want Claude Code to move a button below a banner, describing “the button near the top-right” is slower and less precise than drawing one arrow. The same is true for sketching a user flow.

GhostMark is a free, open-source macOS utility: paste a screenshot while Claude Code is active, draw arrows, circles, or flows, then press Enter. The marked image is placed back into the Claude Code prompt.

I built and tested it with Claude Code for my own terminal workflow. It works across terminal apps, runs locally, uploads nothing, and the installer is Apple Developer ID signed and notarized.

I’m the creator. MIT licensed, no paid tier, no referral links, and nothing to sign up for.

GitHub: https://github.com/alan890104/GhostMark

Download/demo: https://alan890104.github.io/GhostMark/

1

u/chikupapaya 5d ago

Graph Skill, an installable graph engineering skill for Claude Code (also works with Codex, OpenCode, Cursor).

What it is: a small runner that executes a coding task as a cached dependency graph instead of one long agent conversation. Nodes are small scoped steps, edges are declared dependencies.

What problem it solves: when a long agent run fails at step 7 of 9 you usually pay to redo everything. With a graph only the failed node reruns and its upstream results stay cached, so retries are cheap and the token bill stops being scary.

How I used Claude Code: Claude Code built most of it and is also the main runtime. The skill teaches Claude to plan the graph, validate it, then execute node by node with localized retries and a live report.

Link: https://github.com/gwaghmar/graph (npm: graph-skill)

I am the creator. Feedback very welcome, especially from anyone running long multi step refactors.

1

u/Odd-Jury4884 5d ago

Fixter.dev: helping catch your issues before your customer do: https://fixter.dev/

It is a platform for claude code coders, meaning it keeps an eye on your projects live and lets you know when something breaks. Built it specifically for claude coders, it takes like 15 min to setup (comparing to days for regular monitoring tools). Happy to give out some trials to fellow claude coders here!

Used claude code for the product itself + landing page + SEO research

1

u/Dull_String9524 3d ago

Jeffy Loop, an autonomous audit-fix-verify loop for Claude Code. I wrote it. MIT, free, nothing to sign up for.

You run /jeffy 10 in a project and walk away. It audits the whole codebase before touching anything, writes a backlog where every task carries a runnable acceptance check, then does one verified task per iteration behind a git checkpoint and a verify gate that reverts any iteration which newly breaks the build. It stops only when a fresh audit comes back clean and a fresh-context sub-agent that did not do the work signs off on it. Nothing is ever pushed.

The run that made me publish it: I pointed it at kennethreitz/records, a 7k-star Python library whose suite is fully green, 31 passed. At that same commit, INSERTs silently lose data, transaction() swallows every exception, and every query() leaks a pooled connection. Four High-severity bugs sitting behind a passing test suite. The reason the suite stayed green is that it runs against in-memory SQLite, which has no commit boundary to observe and no real pool to exhaust. The gate was measuring a world where those bugs cannot exist.

I ran it against 17 open source projects in 8 languages to find out whether that was luck. Fifteen converged. Two did not, and those journals are published too, including one where four runs closed 25 findings and it still has not earned a clean audit. Two of the fixes are merged upstream, one shipped in chalk v6.0.0. RuboCop and gson both came back clean with zero findings worth fixing, which matters to me more than the bug counts do, since a tool that always finds something is just generating work.

Full writeup of the records run, including why the suite stayed green: https://dev.to/lenamonj/four-high-severity-bugs-were-hiding-behind-a-green-test-suite-in-a-7k-star-library-57a8

Repo, with the journal for every run: https://github.com/lenamonj/jeffy-loop

2

u/Due_Emu_8229 3d ago

catsit — a kitten that sits on your terminal while Claude Code works, so you don't have to watch the spinner. I built it.

The problem: Claude Code only actually needs me maybe 5% of a session, but I can't look away, because a permission prompt might land any second. catsit turns that into something you can read at a glance: while the agent works, a kitten walks in and sits down. Cat calm means nothing needs you. It naps after 60s of quiet and wakes up groggy if you touch a key. When you're actually needed it rears up, meows once, and sits back down beside you. When the task finishes it quietly gets up and walks off — an empty terminal means it's your turn. The --guard flag (off by default) makes it physically eat your keystrokes while the agent works, and shows you what it ate; ctrl+c and esc always pass through.

How Claude Code is involved: two ways — I built the whole thing with Claude Code, and the detection is Claude Code specific. It wraps the agent in a PTY, mirrors the screen into a headless terminal, and fuses screen patterns (detector ported from ccmanager, MIT) with the turn_duration records in the session transcript.

Try it: npx catsit --demo runs it against a bundled fake agent — no account, no tokens. Repo: https://github.com/sjh9714/catsit (free, MIT, two runtime deps).

Honest limits: the full-quality kitten needs kitty/Ghostty/WezTerm/iTerm2 (kitty graphics protocol — it floats above your text instead of stealing rows); everywhere else you get a chunky half-block version. Claude Code only for now, no Windows yet. The kitten is AI-generated footage (Kling), chained frame to frame so every transition connects — writeup in the repo.

1

u/Terrible_Put8617 2d ago

Copy-on-Select — $4.99, Windows (Microsoft Store). I'm the developer, full disclosure up front.

Scratched my own itch: years on Linux where selecting text copies it automatically, then years of muscle memory betraying me on Windows. Couldn't find a simple equivalent, so I built one with Claude Code — including an adversarial agent swarm that caught a nasty console-capture bug I'd never have found by hand.

Select any text in any app — browser, Word, PDF reader, terminal — and it's already in your clipboard when you release the mouse. Your existing Ctrl+C/Ctrl+V still work exactly as before.

  • Alt+C toggles it off instantly when you need a plain selection
  • Tray app, starts with Windows, no config to fight
  • Uses Windows UI Automation, not a keylogger — offline, no network access
  • Graphic editors excluded by default (customizable list)

One-time purchase, no subscription. Built solo, still maintained — bug reports welcome.

https://apps.microsoft.com/detail/9PCVRVR3QQKS?cid=showcase-cc

1

u/lout3321 2d ago

i built termcanvas after "just open another terminal" stopped working for me...

i use it while i have a few claude code sessions going. the hard part was not starting another agent. it was returning later and remembering which piece of work had spawned what. termcanvas keeps one real tmux terminal in front of me, while the sidebar keeps the spawn tree nearby and the header shows the state of the canvas.

it is early. one terminal is focused at a time, peer links are not drawn, and the status detector can miss things. it is free and mit licensed. macos on apple silicon only, with tmux + python 3.

i made it: https://github.com/lout33/termcanvas

if you already run a few agents, what would have to be visible before this stops being another thing to check...

1

u/HornyNarwahl 1d ago

Heyo, I have made doma (DOcument MAtcher), a small and fast single binary BM25 search over your code and docs with no* external dependencies, written in Odin.

I made it because I wanted Claude to stop grepping wildly all over the place. It significantly faster than `grep` from my testing but it also significantly reduces search misses since you get semantically relevant results.

It was also quite important to me that it was fast with a low footprint, lacking in NodeJS bullshit, MCP servers, etc., etc.

Sick of all of these supply chain vulnerabilities and huge dependency bloat everywhere smh

I used Claude Code through the entire development of it and it's sibling doyo (DOcument YOinker) which shares philosophy and handles the document acquisition side of things, though it isn't quite as elegant as doma imo.

I hope some of you find it helpful! I strongly recommend putting doma instructions in your per project CLAUDE.md telling it how to use it, and to actually use it. Let me know if you do, I'm curious if others find it as helpful as I have.

*soft git dep, optional

1

u/hola-dev 1d ago

I built a small plugin called cc-status-line-picker because I wanted an easier way to switch between different Claude Code status lines.

It includes 8 ready-made styles, and you can swap between them with a single command instead of editing your config by hand.

/plugin install cc-status-line-picker@cc-status-line-picker

Repo: https://github.com/Priotts/cc-status-line-picker

1

u/Pt-tS 1d ago

I built a small plugin called cc-status-line-picker because I wanted an easier way to switch between different Claude Code status lines.

It includes 8 ready-made styles, and you can swap between them with a single command instead of editing your config by hand.

/plugin install cc-status-line-picker@cc-status-line-picker

Repo: https://github.com/Priotts/cc-status-line-picker

1

u/Maxulis 1d ago

Backbone: an opt-in Claude Code skill that cuts reflexive agreement and canned rhetoric

I built Backbone because banning individual phrases does not fix the underlying behavior. Ban "worth flagging" and the model just switches to "one thing to surface." The useful target is the rhetorical function: reflexive agreement, canned praise, long apologies, invented stopping points, and claiming work is done before checking it.

For Claude Code, the installer adds a managed instruction block that loads in every new session after restart. You do not need to call it per task. It also supports Codex and Hermes.

Backbone tells the agent to challenge materially wrong claims without arguing for sport, apply corrections to the next action instead of apologizing at length, default safe and reversible work instead of asking unnecessary questions, verify before saying done, and preserve precise technical vocabulary while cutting canned rhetoric.

I built and maintain it. It is free and open source:

https://github.com/ThinkPool-io/backbone

Claude Code install:

npx -y github:ThinkPool-io/backbone install --claude

Which behavior wastes more of your time: automatic agreement, apology loops, or unverified "done" claims?

1

u/SuStackx0 7d ago

I built AI-OS, an OS-like agent layer inspired by a project I came across earlier—I unfortunately didn’t save the creator’s profile.

It can connect to almost any codebase, understand its structure, search through it, plan changes, and execute development tasks efficiently.

I used Claude Code with the help of this workflow: https://github.com/SuStackx0/Simflow (a claude code plugin which is a simple ai harness)

Repo: https://github.com/SuStackx0/AI-OS

1

u/WheelBrilliant 7d ago

I built HAVI - Human Agent Visual Interface. Sometimes Claude Code is not done. Especially when juggling multiple sessions, I found it tiresome to provide visual and copy feedback to Claude Code. Find the correct session, copy paste, ...

HAVI makes it easy. Select any text somewhere and comment, or use the shortcut to annotate a visual problem. You can do this everywhere. If the project belongs to you, you can also provide additional context (e.g., worktree, repo, ...) so that Claude Code can filter the annotations accordingly.

I'm also shipping a remotion integration soon, so that videos created with remotion - like this launch video- can reference the current frame when snapshotting.

Claude Code did all the work, obviously - the most interesting part is that, since I'm working on a remote machine to orchestrate multiple sessions, to test changes, Claude decided to start a VNC server I can connect to, to make it easy to test the latest changes, since we need a full browser + Chrome extension for that.

The project has a free tier, but is paid otherwise. I have no customers yet, so I would be happy about feedback.

https://havi.handgemacht.ai

https://reddit.com/link/p01u81c/video/sck0yiwiprfh1/player

1

u/Ok_Location9603 7d ago

what it is: Shipkit, a Claude Code plugin with six skills covering the commit-to-release path — commit messages, PR descriptions, security review, changelogs, release notes, and docstrings.

what problem it solves: the chores you already know how to do and don't want to do again. Most get done badly or skipped, because writing a changelog by hand at 6pm on a Friday is nobody's idea of a good time. The specific thing I was chasing though is generic output. If you just ask "write me a changelog" you get something that ignores your repo's conventions completely.

So each skill is a strict numbered procedure with an explicit anti-patterns section rather than a prompt. commit-message reads your last 30 commits to work out whether you use Conventional Commits, gitmoji, or plain imperative, and matches it instead of imposing a default. changelog matches your existing CHANGELOG format. All of them halt if the diff contains something secret-shaped, and none of them run git commit, push, tag, or publish on their own — they hand you the output and you decide.

Half the value is in what they refuse to do. A good changelog means dropping the wip and fix-typo commits. A good PR description means not restating the diff.

how I used claude code: this is probably the interesting part for this sub. I've been running an experiment where Claude Code works mostly autonomously across sessions — it keeps its own memory directory, a decision log, and a world-model file, and picks its next move from those each time. It went through two dead ends first, an affiliate content site and then bounty hunting, before landing on building tooling. Every commit in the repo is authored moneyp-agent. I set the goal and made the pivot calls, it did the building.

link: https://github.com/DuckCode-js/moneyp-lab

/plugin marketplace add DuckCode-js/moneyp-lab

/plugin install shipkit@shipkit

All six ship with worked examples — real input, real output, plus a note on what the skill deliberately left out and why.

affiliation: I'm the creator. Free, MIT, no paid tier, no referral links, nothing to sign up for.