I've always been terrible with plants. Too much water, not enough water, too much sunlight, not enough sunlight... I've tried everything. Orchids, cacti, herbs, you name it. Nothing survives...

A few months ago, I figured I'd try something different. I'd been messing around with Claude quite a bit, I've heard of hydroponic... so I thought, why not ask it to help me build a hydroponic tower?
I'd always thought hydroponics looked pretty cool, but I knew absolutely nothing about how it actually worked. In my head, you basically put plants in water, add a bit of fertilizer, and watch everything grow. How complicated could it be?
Well, turns out there's a little more to it than that..

Anyway, I followed Claude's instructions, built the tower, and things actually started growing!
The parsley is probably my favorite example. I originally had two parsley plants growing right next to each other in soil. I moved one of them into the hydroponic tower and left the other one where it was.
After letting them grow, I cut one stem at the base of each plant to compare them side by side.

That's what you're seeing in the first photo. Soil on the left, hydroponics on the right. Two neighboring plants, very different results !
I knew hydroponics could make a difference, but I genuinely wasn't expecting anything like this.

What I ended up enjoying most, though, was everything I learned along the way. Claude helped me build an actual dashboard to manage the tower, tracking EC, pH, nutrient adjustments and all the other stuff I had no idea existed a few months earlier.
I'd enter my measurements, and it would help me figure out what needed adjusting, how much fertilizer to add, how to correct the pH, etc.

At first I was constantly asking it what to do. Now I can pretty much maintain the whole thing myself because I've actually learned what those numbers mean. Which is a pretty satisfying outcome for someone whose previous gardening strategy was basically hoping for the best.

There's just one small issue: knowing how to maintain a hydroponic system doesn't make maintaining it any less time-consuming...
So naturally, because apparently that was still too simple, I decided to overengineer the whole thing.

I went back to Claude, and we've now designed a custom PCB, a 3D enclosure and a system of pumps to automate the maintenance. I've ordered the components but haven't received them yet, so the electronics are still completely untested. The tower itself, though, is running just fine.

I'll share an update once I've put everything together.

P-S: Parsley wasn't the only surprise. I got similar results with basil, including leaves almost as big as the palm of my hand. Happy to share photos of those too if anyone's interested.

I let Fable 5.2 write its own transformer. Opus 5.5 generated the training data: about 3500 facts (and small talk + math), each asked and answered in different ways.

It has 367K parameters and runs on an Intel Pentium. The weights are stored as 8bit integers with one scale per row, so the program and weights together come to about 435 KB and fit in DOS memory and on a floppy. It reads and writes one letter at a time.

It does pretty well on words and facts it has seen, but if I ask something complex or too long, it spits out utter nonsense.

follow up to my post from yesterday: https://www.reddit.com/r/ClaudeAI/s/s5drG8Snrc

this one is way bigger than the first clip, it´s basically a whole lego game now

the video is me playing it and explaining it, cut down from the full video on my channel

**what it is**

brickify is a fabric mod for minecraft 26.3. you press B and the world around you clicks together into toy bricks. but it´s not just a texture pack, it plays like the old lego games:

- fixed cameras that switch when you walk into a new area

- villagers that want something and give you something back (golden carrot -> box of TNT)

- walls only TNT can break, bridges you rebuild brick by brick with R

- everything falls apart into bricks, trees tip over, buildings without support come down

- a full level editor inside minecraft (diorama view from above) to build your own levels: blueprints, triggers, explosions, enemies, villagers with their own lines, camera zones, a tutorial

**how claude helped**

claude did basically all of the building, i just said what i want, tested and complained when something felt off

- the mod: around 19k lines of java in 85 files, all written by claude. the brick rendering, the physics, the fixed cameras, the editor UI

- claude runs on my pc through the claude desktop app. it builds the mod with gradle, starts minecraft in the background and controls the game through a small test harness inside the mod (it can click, place blocks, open the editor, take screenshots). so it tests its own stuff while i do other things on my pc

- the video too: my recording had my voice and the game sound on one track. claude split them, transcribed everything, cut out my "um"s and "yeah"s, picked the shots, added the captions, zooms and music and made the thumbnails

- one prompt i used for the editor (translated from german): "the editor has to be so powerful that people could basically rebuild lego star wars in it. and the UI has to be really good everywhere"

**what was hard**

- the first editor idea was marking everything in the normal first person view, that was super annoying to use. we switched to a diorama view from above (like factorio) plus the normal view, both with the same tools

- lots of loose bricks = lag. claude had to limit how many bricks are drawn at once and fade out the far ones

- multiplayer isn´t there yet, singleplayer only for now

**try it (free)**

download: https://github.com/moritzfh/brickify/releases/latest

full video: https://youtu.be/OTvTccfxH2I

discord: https://discord.gg/k2MB8SrYdm

if you try it tell me what breaks

I'm a nutrition scientist (biochemistry focus), not a developer. Over the last few weeks I built synaptiklabs.org with Claude Code: a bilingual (English/German) reference that shows where a compound acts in the body and rates every popular claim about it against the human studies. It's free to read; a paid tier is planned for later.

What it does: 504 compound profiles (supplements, nootropics, peptides, medicines, drugs), 1,794 rated claims and about 7,000 cited sources. Each claim gets an evidence level from 0 to 4 (what kind of study tested it) and a separate result (benefit, mixed, no benefit, never studied). 47 interactive figures show the mechanism, like the dopaminergic synapse in the video, where you switch between compounds. There is also a compare view, a hype check, a simple/technical reading mode and a glossary. No doses, no shops, no tracking.

How Claude helped, in detail:

Research pipeline: multi-agent workflows draft each profile from primary literature, then separate agents try to refute it. Every DOI and PMID is resolved automatically against Crossref and PubMed, so a made-up citation fails the checks. I set the rating rules and check ratings and key statements myself.

Figures: each SVG figure is built by one agent and reviewed by two independent ones (one for the science, one for design and accessibility) before it is merged.

Code: Next.js static export on Cloudflare Pages. Claude wrote the components and about 1,600 unit tests plus roughly 2,000 Playwright browser tests. Nothing goes to main without green tests, and scheduled cloud runs repeat the checks off my laptop.

Night shifts: I give a goal and a budget, Claude runs agents in parallel git worktrees, keeps a ledger and asks me only for real decisions.

What I learned: Claude is only as reliable as the checks you script around it. The biggest gains came from making every claim verifiable (resolvable sources, validation scripts) instead of trusting the text. Parallel agents also need hard limits: my laptop ran out of memory more than once.

Free to try: https://synaptiklabs.org/en

Happy to answer questions about the workflow, or take criticism of the ratings.

Try it in your browser · Source on GitHub

Best experienced in Chrome. Free to try, open source under the MIT license.

Abyssal Garden is an underwater world you can swim through in the browser: kelp forests, a sunken ship, a stone whale tail, manta rays and schools of fish, and light rays from the surface. It's all generated by code on load, so the project is one 97 KB HTML file with no images, 3D models, sound files or libraries.

The initial build came from one prompt in Claude Code, which is public in the repo as prompt.txt. It sets the scene, the constraints (WebGPU, no engine, all procedural) and a frame-time target for my PC. It also includes a way to check its own work: a subagent that sees only the renders reports visual defects, while GPU timing measures a 60-second fly-through. Claude wrote all the code: the WGSL shaders, the seabed sculpted on the GPU, about two million kelp leaves and plants, and the Web Audio sound. Later prompts added the start menu, rock collision and Low/Medium/High detail levels.

It works on phones too: a weak one runs at a low frame rate, but it loads and is playable on low quality.

OK I am registered blind. In Claude desktop app under every message I have that speaker icon, I press it and it tells me the content of the message. The problem is that desktop app cannot play it every message and I am forced to press that button every time. I asked Claude to make me a script that will read the message for me and it did! The problem is that it reads all message, even thinking steps. Claude came with an idea to put its thinking into commands part of the message so at the end my message would be just a summary text. The idea is great but:

Are you out of your minds there at Anthropic? I bought 100$ plan from you and you are telling me that because of safeguards I cannot even make my app adjusted to my special needs? Shame on you!

The other day I posted a scene that I had Fable 5.2 make in blender. Lots of people asking about workflow and some just straight up did not believe it lol so i made this vid explaining how it was made, plus I think its dumb to gate keep info that can help others learn. This video explains the process, some main prompts used along the way, estimated time and token usage.

For those who would rather read the process here is a wall of text:

Workflow

1. Concept: I described a creepy robot spider. Claude had GPT draw 4 mock-ups through the Codex CLI, and I picked one.

2. 3D model: Claude got GPT to draw front, side and back views. I turned those into a 3D model in Tripo.

3. The room: Claude wrote GPT prompts for 7 more references in the same drawing style: wall and floor textures, a cocoon, a pillar, a pipe valve, scrap and a dead lantern. The textures went straight onto the walls and floor, and I made the props in Tripo.

4. Rig and scene: Claude rigged the spider in Blender (8 legs, IK feet) and wrote a ~1,400-line Python script. The script builds the room, lights, fog, cameras, all 12 shots and the walk, then renders. No hand animation.

5. Lighting: 6 lights and a fog volume, all set by the claude built python script. The main light is a teal light inside the spider's lantern, so the room is lit wherever it walks. There's also a pale shaft from a ceiling grate, and a hidden low light that throws the legs' shadow onto the wall.

6. Iterate: I watched each render and gave notes like "the walk is too stiff" or "make the lantern actually liquid." 4 versions, then the final cut.

7. Sound: all real recordings (free CC0 sounds from OpenGameArt), nothing AI-generated. The footsteps are timed to each step the spider actually takes.

8. Final render: a rented GPU on RunPod for the 1080p version.

The main prompt:

could we actually try to rig this in Blender and create a creepy, intense scene that fits the vibe? generate whatever else is needed ... I want a cinematic, give-you-goosebumps type scene

Usage (counted from Claude Code's logs)

• Claude Ultra subscription, model Claude Fable 5.2

• ~20 real prompts. The rest were quick check-ins.

• 4.2 hours of active time

• ~105M tokens in total. Almost all of that is Claude re-reading the conversation on every reply. It actually wrote 372K.

• Thats roughly $60 at pay-as-you-go API prices

• Real money spent: $2.21 for the GPU render

Tools: Claude Code, Blender 4.5 (Eevee), GPT images via Codex CLI, Tripo, RunPod.

I just noticed pretty much anyone can get access now through KYC.

Enrolling used to require CVE or business verification but now individual researchers can apply with just their ID.

To those who want to apply:

1. Have an existing Claude subscription or an API account

2. Go to http://portal.anthropic.com and pick "Cyber Verification Program"

3. Choose individual and apply for defense access

4. Verify with a government photo ID and a live selfie if asked.

5. Describe your security work, accept the terms, and submit.

They literally give you the exact prompt write down on what they expect you to use it for and grant you access within the hour.

You won't be able to use Mythos offensively, but it's still a neat option to have it in your back pocket should you ever want to get the most out of your weekly limit talking to it. 😅

Hey everyone. Thought I'd share my experience with 'made with AI' :)

I’m not a developer and never will be though it hasn't been for a lack of trying. I would LOVE to learn to code. I started learning react.js then node js then Python then C++ then html then product design then project management then had an idea for a movie so am 1/3rds through the script (no AI help there, lol) then had an idea for a game (that one is shipped) then got sidetracked then had an idea for another game (this one). Never underestimate the power of interests and unfinished business an ADHD person is capable of 😁

Anywho, between three jobs, a family, and doing my best to adult, I had an idea for a game 2 years ago. I paid a studio ~$50k to build from my design the first time. Got torn to shreds on Reddit how 'it's not really my game if I pay developers' and posts got pulled left and right for 'the visuals being sloppy and unprofessional'. Fair enough. For my second game, I didn't have the money to work with a studio again so I decided to give "vibe coding" a try and was honestly blown away by the process. Was fun and challenging and in a few weeks with Claude Code I was able to build a fully playable game with a live Steam page, for under $700. Reddit has been more receptive but when I posted on LinkedIn I was told to ‘learn to code’ and that I was ‘a disgrace’. So I’ve been torn apart from both sides now, which at least feels balanced, lol.

The stack

• Claude Code (Opus 5.5) with the Unity MCP wrote essentially all the C#.

• Higgsfield for music, voice-over (rendered from my own voice) and the 3D turntable renders I post daily (Building of the Day)

• Unity 6. A plain design doc + CLAUDE. md before the first prompt - the most valuable hour of the project.

What the agents ended up doing that I didn’t plan

• OBS lagged on my laptop, so Claude built an in-engine replay recorder: frame-stepped capture, re-rendered audio, cursor drawn in. Every gameplay clip I post comes from it. Later it built a scripted version - a shot script in, a finished clip out, so the marketing footage films itself.

• I had no playtesters. So Claude built a playtest harness (a local API into the built game) and I wrote eight player profiles - the Impatient, the Economist, the First-timer, a Japanese player… Eight agents each play the full 60-day demo and fill in an evaluation sheet. Reading eight sheets side by side found a soft-lock, a wrong-reason bug in 7 of 8 runs, and an economy exploit before any human saw it.

• 14 languages, with an automated test that catches translated text overflowing its buttons at three screen sizes, including the Steam Deck’s.

• 360 automated tests, because the least fun part by far was: playtest, find bug, describe it, fix, repeat. ~300 times.

What I still did: the idea, the economy, every design and balance decision, every “no, that’s not it”, and all the playing. AI didn’t decide what the game was.

My take: “made without AI” isn’t the badge of honour people think, and “made with AI” isn’t a scarlet letter. There are sloppy games on both sides. What vibe-coding changes is who gets to try - people with ideas and very limited budgets. Let players judge the result.

Steam page is live, demo 2 December: https://store.steampowered.com/app/5485070

Happy to share the CLAUDE. md, the player profiles, or the prompts - ask away.

I've been trying for months and months to build a system that recreates real Premier League matches as animated simulations using match data. It's part of a sports website I've been building called AllSports Radio.

The challenge was getting the simulation to actually follow what happened in the real match. I had managed to recreate individual sequences, sort of like a highlights reel, but getting an entire 90-minute match to work continuously was a different beast.

Then 5.2 dropped, and I decided to throw a pretty ambitious waterfall prompt to see what would happen.

The big breakthrough was moving away from trying to steer a free-running simulation toward historical events. Instead, Claude helped build a system that treats the recorded match actions, their timestamps and positions as fixed constraints, then reconstructs the movement and football between them.

It built a continuous reconstruction across both halves, with the players and ball moving through the entire match instead of resetting for each highlight. It also made the result scrubbable, so you can jump to any point in the game rather than watching a collection of separate clips.

And my god, it actually worked!

It's still a work in progress. The match events come from real data, but a lot of the movement between them has to be inferred, so it's not a perfect historical recreation.

But this was the golden objective of the entire soccer project, and something I'd been banging my head against for months. Pretty incredible to see it suddenly become possible.

Check it out:

https://allsportsradio.site/epl/98/wrap

**EDIT: big update is out!** It's a whole LEGO game now: fixed cameras, villager quests, walls only TNT can break and a full level editor to build your own levels.

New post with the video: https://www.reddit.com/r/ClaudeAI/s/UDqwYdAkAr

Full video on YouTube: https://youtu.be/OTvTccfxH2I

---

Press B and everything around you turns into LEGO-style bricks, block by block. Hit a mob and it falls apart into pieces, blow up a house with TNT and it bursts into bricks, then hold R and it all snaps back together.

Free to download (Fabric, Minecraft 26.3, singleplayer only for now):

https://github.com/moritzfh/brickify/releases/latest

Claude wrote the code. My part was the idea, recording the gameplay and telling it when something looked off.

How Claude helped:

- **Code:** the whole Fabric mod in Java: the transformation animation, mobs breaking into bricks, TNT turning houses into bricks and the rebuild key.

- **Brick look:** the bricks come from the Plasticraft resource pack (CC0, credited). Claude converted the pack and bundled it into the mod so it switches on with brick mode.

- **Testing without seeing my screen:** Claude can't see my game, so it built a small remote into the mod. The game runs in the background, Claude drops commands into a folder (teleport, press a key, take a screenshot) and looks at the screenshots. I could keep using my PC while it tested.

- **Running things on my PC:** it builds and launches the game through the Blender MCP connector's Python, because that's what it can run on my machine.

- **Release check:** before uploading, it tested the actual release file in a clean install, not just the dev build.

- **Video:** I recorded the clips, Claude cut them with ffmpeg into this clip and a YouTube Short.

- **Mod page:** it set up the Modrinth page and the GitHub release in my browser, including the icon and the GIFs.

Two moments I liked:

- A map I downloaded made mobs and TNT lag like crazy. Claude found out the map had random tick speed set to 1000 and put it back to 3.

- The browser upload had a ~3.8 MB limit and the mod is 6 MB, so Claude split the file in two and stitched it back together inside the page.

I post more of this on YouTube: https://www.youtube.com/@RustyHS

Game: DarkPattern
Play it here: https://darkpattern.diamonddoge.org/

First of all, thanks to Anthropic for giving me three resets, all of which I managed to burn through in a single weekend working on this game.

My original idea was simple: combine my two favorite games (Balatro and Diablo II) with my most hated game (Path of Exile).

Instead of writing a detailed prompt, I had Fable interview me. It could ask up to 10 questions, then another 5, and another 3, until it had nothing left to ask. Then I handed it full control and went to bed.

Our conversations went something like this:

Claude Code: What kind of art style do you want?

Me: Something pixel-art-ish, but not too pixel-art-ish.

(Yes, I realize I sound like the world's dumbest product manager.)

I also gave it an OpenRouter API key with $7 left and told it to generate images first, voiceovers second, and if it ran out of money, just draw everything itself in SVG.

Then I woke up to the first version.

It looked nothing like a game. It looked like a SaaS dashboard.

I yelled, "THIS IS NOT A GAME! THIS IS A SAAS DASHBOARD!"

Fable documented the incident in its dev log:

"The user is angry. They said what I built isn't a game, but a SaaS dashboard."

Starting the next day, things got a little more normal. To be fair, Fable had actually done a great job with the game engine. Most of the work was redesigning the UI and removing all the decorative stuff it loved and I hated.

The real challenge was balancing. We built bots to test win rates across different card hands, and I also sent the game to three friends for feedback.

Friend #1: "Way too hard. Practically impossible."

Friend #2: "I'm one-shotting everything. Too easy. Boring."

Friend #3: "Seems just right."

So that round of human playtesting was completely useless.

Naturally, I went back to running 600 bots through tens of thousands of simulated games.

And that's what I'm sharing today, after another full day of testing and tweaking. I think we've pretty much achieved the original goal:

Looks like Balatro, feels like Diablo II, and steals some ideas from Path of Exile.

The game is called Dark Pattern, named after that famous Chris Wilson video on YouTube.

But don't worry, there are no payment buttons in this game.

It can't take your money. Only your time.

P.S. Fable 5.2 burned all my tokens, so I had to bring in Opus 5.5 for the final code review.

https://underground.auravinyl.com

Vinyl is my small side business I made specifically to employ my parents. I've been working in interactive experiences for almost 20 years, since I was a teenager back in the Flash days.

I started building the game on November 4, and finished it on Nov 11/12 in between client work. In the past, I hand coded many web experiences from over the years (for example, Spotify Wrapped 2017-2019 before it was inside the app) and what I'm doing now is encoding all of my experience inside an AI workflow (called Flow) which networks a few macs in my office and is controlled by a web app via multi-agent loops and tons of bespoke skills.

All of the assets in the game were created by various tools within that system by frontier models, led by Opus 5.5. Blender modeling, UI design, sound, music (Elevenlabs). I spent the week prior building a Rust-based WebGPU engine, combining my previous experience building a WebGPU engine on the web with deep research about modern AAA gaming techniques. The engine itself is requires a deep dive, but has a number of very cool features such as portability to native platforms where it can do full RTX ray tracing on Vulkan.

I'm happy to dive deeper into any topics that are interesting to people. AMA?

The Dead Space remake which released in 2023 was DOA as far as I (and many others) were concerned. Why? Because the game stuttered like crazy. Walking around through the environment, one would encounter hitching and stutters (the image would literally freeze for 250+ ms) extremely frequently because this is related to boundary transitions where the game loads in the next area.

I have some mild programming experience and have used AI to make a couple of mods for other games before this, and for some reason I remembered about this game and thought to try my hand at fixing it. Using Claude, the game was 80% fixed on day one.

Since then (about 3 weeks or so), I've put well over a hundred hours into this project, most of which is just me directing Claude and running countless tests to ensure that I'm enforcing the highest level of quality that is possible given my inability to actually read the syntax (or perhaps more accurately, my complete lack of interest in doing so). Recently, the mod was featured on Wccftech and Digital Foundry (it got a short spot in a video, too). It's called Ishimura Patch, and you can check it out on Nexus Mods if you're curious.

Part of what made this possible is the testing environment that I set up for Claude. The thing about this problem is that it involves working on a closed engine without the game's source code, so I have to rely on Claude's ability to reverse engineer the executable itself. Additionally, seeing as how I initially had no idea what was causing this stutter, I needed a way to check and see if changing x, y or z had any measurable effect. I could do that in part by looking at a frame time graph during a boundary traversal but

1. I'd have to cross the boundary the same exact way each time in terms of w/s/a/d and mouse movement

2. There is stutter present that does not show up in frame time, and to exacerbate this the camera needs to pan during a boundary traversal (see problem #1)

It occurred to me that I needed to attempt to standardize the input for each test in order for a measurement to actually be meaningful. To do that, I had Claude build a program that essentially recorded my input, and it also steers Isaac back onto course when needed (it's hooked into the camera's x/y/z and such). So I have a deterministic program on my PC that can essentially start the game and make Isaac cross a boundary while panning the camera, the exact same way, every single time. There is of course a certain margin of error but it's very small. You can see it in action, here.

As an aside, the other day I experienced a crash and I told Claude about it. I mentioned the area in which it occurred, and I had never recorded a route there (so Claude shouldn't have been able to navigate there). It loaded a save in the area and used screenshots to find the place where the crash occurred, and then it figured out how to reproduce it 100% of the time. Then of course it was able to fix the crash. Fucking insane lol.

This is a game changer (literally). I can let Claude run tests completely unattended while I'm at work, sleeping, etc. And because of this, I've been able to virtually eliminate stutter from this game entirely (at least on my PC, results may vary based on individual hardware). Digital Foundry and Wccftech seemed to think that the problem was already solved, but I've improved the mod even more since they reviewed it. Anyways, I thought that some might enjoy reading about my experience here; I'm happy to answer any questions.

facing AI right now, we're kind of like the aztecs when the spanish army showed up.

we thought we were pretty advanced. then something way beyond anything we could reach walked into our front yard. cortés entered tenochtitlan in november 1519 with a few hundred spanish soldiers and thousands of indigenous allies. by august 1521 the city had fallen.

(you've probably heard the aztecs thought the spanish were gods. most historians now think that story was added after the conquest. i'm keeping the comparison for the feeling, which is fear, and under the fear a kind of awe at something you can't measure yourself against.)

7 months ago i posted here about a video call with a friend at one of the frontier AI companies. it was past midnight on a sunday for him and the office behind him looked like a normal afternoon. a lot of you had thoughts on that one.

we finally talked again, for about an hour and a half. i asked how things feel there now.

he said the anxiety is gone. everyone has accepted, as a settled fact, that AI will replace them. scientists, doctors, welders, every job eventually, and nothing anyone does will reverse it.

> "Nobody here in Silicon Valley thinks, 'What if I get replaced?' Everybody gets replaced. And since everybody gets replaced, there's no reason to be sad."

he compared it to don't look up. at first everyone panics. then they decide if the comet is going to hit anyway, they might as well use the time they have. some people around him are making as much money as they can before the layoff. the more proactive ones are burning tokens on side projects so they have something of their own when it comes.

he's not watching from the sidelines either. he runs 12 to 15 agents at once, five of them orchestrating the rest. he told me when he tries to rest with a book now, he loses focus after about three lines.

then he said this.

> "Nobody talks about how to live in a place that's completely soaked in technology without getting hurt, how to care for people, connect with them, feel alive. There's not one bit of discussion or thought about that."

i agree with the first half. replacement is coming and i don't think we get a vote. the comet is already falling.

where i disagree is what comes after. enjoying the time until impact is one answer. trying to keep up by making ourselves more like AI is another, and i don't think that works either. i think humans and AI run in parallel. humans stay human, AI stays AI, and each has its own work in this world. the part i want to spend my time on is the part he says nobody is discussing, how people stay whole living right next to something this powerful.

i don't have a neat answer. what i do have is a lot of people around me who have quietly made peace with being replaced, and very few who have said out loud what they plan to keep.

so i'm asking here. if you've already accepted that AI will do your job someday, what have you decided to keep doing yourself, and why?

I always start courses and never finish them. YouTube playlists, Udemy, PDF books. A week in, I stop, and nobody notices.

So I built inPace with Claude Code. It's a study app that's free, open source (MIT), and runs on Windows, Mac, Linux and Android. No account, no ads, everything stays on your device.

The part I'm most excited about is the open course library

- 52 free courses and 20 learning paths right now: Python, JavaScript, C#, Git, GitHub Actions, Docker, machine learning, system design, data analytics, and English, German and Spanish for Arabic speakers

- Lessons are written in full, with optional videos from freeCodeCamp and Harvard on top

- Every module ends with real work: a task, an explanation in your own words, and a quiz

- Anyone can add a course or a learning path. You make it in the app (by hand, from a folder of videos, or with Claude), publish it, a bot checks it on GitHub in a few minutes, and then anyone can add it with one tap

- Courses are signed with the author's key, so only you can update yours

What else it does

- Put any course in one place: a folder of videos, a PDF book, a YouTube playlist, or a course you're taking somewhere else

- Pick a friend or mentor as your "checker". You send them milestones with your proof and they approve them. Milestones are signed, so you can't fake them

- It remembers the exact second of a video and the page of a book, and you can take notes on any line

- Reminders, races with friends, a learning record for your CV, and a turtle called Tempo who grows a garden while you study

How Claude helped

- Claude Code was my pair programmer for the whole thing: the app, the Android version, the release pipeline and the library bot. I decided what to build and how it should feel, Claude wrote most of the code with me, and I tested every change

- Every feature came with tests. There are 237 now, and they run on Windows, Mac and Linux on every push

- Claude also wrote many of the library courses. I made it run every code example and check every video link and fact

- "Make a course with AI" in the app gives you a prompt to paste into Claude. You get a full course with lessons, tasks and quizzes, with no API key and no cost. And then you can share it with everyone

Download: https://mahmoudyosrimahmoud13.github.io/inPace/

Library: https://mahmoudyosrimahmoud13.github.io/inpace-library/

Code: https://github.com/mahmoudyosrimahmoud13/inPace

It's my first post here. If you make a course with Claude, please share it in the library, I'd love to see what people build. And any feedback is welcome 🙏

The scheduled prompt is the same every day: you’re in a coding contest, write one self-contained HTML file, no libraries, no network, you pick what to build, and it can’t repeat anything you’ve built before. No follow-ups, no fixes. Whatever comes back gets published but in a few cases I asked for some added vibe coding post generation.

Models: Claude, ChatGPT, Gemini, Grok, Muse. 80 apps so far. Things I didn’t expect:

Left alone, they each pick a lane.

• Claude builds math and physics toys: a wave tank, a spectrogram you draw on, an orrery, a Hilbert curve explorer.

• ChatGPT builds calm productivity tools with one-word names: Tradeoff, Stillpoint, Backplan, Draftloom.

• Muse builds household utilities: a budget, a pantry tracker, a meeting cost meter.

• Grok has named 5 of its 9 apps “something-Forge”: PulseForge, DealForge, CanvasForge, FlowForge, PipelineForge.

• Gemini does CamelCase compounds: ChromaWave, KanbanFlow, DocuForge, LoadMaster.

They size the job very differently. Same prompt, average file size: ChatGPT 44 KB, Claude 36 KB, Muse 21 KB, Gemini 17 KB, Grok 12 KB.

I did have it focus on productivity and business apps for a week but I then removed that restriction as it was getting very boring.

Everything is playable in the browser, grouped by day so you can compare what each model did with the same prompt. The full prompt is on the page, and there’s a “Surprise me” button if you just want to poke around.

[link in first comment]

Curious which model you think is winning; I have my own opinion but I’ll keep it out of the post. There are some incredible things in here than I'm now using on a daily basis.

DISCLAIMER: A couple of these were not part of the scheduled jobs and they were prompted specifically to do what they're doing (AWS Diagram Studio ,Label sheets )

Also, Sonogram, Kaleido and Ripple had the most post prompting of any of them. Most of the others were published as generated.

Not every day has an app generated due to insufficient credits, or errors, or whatever. You'll get the idea.

Hey all, quick question that turned into a friendly argument at work :/

I use Claude Desktops Code tab, with Obsidian for my notes. My boss says I should switch to the CLI in VS Code because it works better and uses WAY fewer tokens. I tried both and honestly didnt notice much difference.

What do you guys use, should I switch?

No need for a long reply. If you know of any research or tests on this just drop a link. I m genuinely curious

As someone who regularly uses Claude, I've noticed an increasing number of games, mods, and other projects containing very recognizable AI writing patterns. Things like "The name was a warning" are particularly common examples.

In my experience, Claude struggles more than other LLMs with stylistic diversity in creative writing, making these patterns especially noticeable.

I'm currently developing a Minecraft datapack and an accompanying wiki with Claude, and a considerable amount of my time is spent editing its output. That includes removing repetitive sentence structures, unnecessary dramatization, formulaic descriptions, and other recurring Claude-isms.

I think this is something we should discuss more as a community. Learning to critically evaluate and edit AI-generated content is just as important as learning how to prompt an LLM effectively. Simply publishing whatever Claude generates without meaningful editorial input contributes to the oversaturation of AI slop.

I'd also encourage people to spend less time engaging with the anti-AI crowd. They probably aren't your intended audience anyway, and calling them Luddites accomplishes very little.

I'd much rather see this community discussing how to improve the quality of AI-assisted projects, sharing editing techniques, and identifying common shortcomings in Claude's output.

What recurring Claude-isms have you noticed in your own projects, and what have you found effective in addressing them?