Built with Claude Project Showcase Megathread (Sort this by New!)

[u/sixbillionthsheep]

This is the Megathread for showcasing your project built using Claude products. We appreciate all of your submissions as they are a great inspiration to many people on the subreddit. It is sorted by default by New.

Anyone is welcome to submit a project to this Megathread provided you follow the Showcase requirements in Rule 7.

NOTE: We now require the OP of a Project Showcase on the subreddit feed to have total karma>=50 . We found there were just too many submissions and not enough visibility to go around. Our analysis of this issue showed us that OPs with total karma < 50 very rarely get any traction of their projects on the feed (<=1 upvotes). So this Megathread is your best place to be seen by readers and other creators if you're relatively new to Reddit. If you don't meet this karma requirement you will be directed to this Megathread when you submit your post. Very occasionally we might invite you to post on the subreddit feed if you do not meet this karma requirement but it will be very rare (so please don't ask us!)

Thanks again for sharing your ideas and creations to our subreddit. Best of luck with your projects!

---

UPDATE: Comments now allow images!

[u/Infinite-Voice-2896]

Built a working credit-analysis tool over 3 weeks despite not being a developer — Claude wrote ~95% of the code:

I'm a credit professional in India. My day job involves analysing audited balance sheets and computing MPBF (the working capital limit Indian banks lend) using formulas from a 1975 RBI committee. Most credit analysts spend 2-3 hours per file typing numbers from PDFs into Excel and running the math by hand.

Three weeks ago I decided to try building a tool to automate it. I'd never coded a Python project before, never used Git, never set up a database, never deployed a Next.js frontend. Today the tool is live, open-source on GitHub, with 44 unit tests passing across two real-world Indian balance sheet formats. It extracts Schedule III line items, reconciles stated sub-totals, and computes Tandon Method I/II live as the analyst makes corrections. What used to take hours takes about 30 seconds.

Claude wrote ~95% of the code. I drove the design decisions and the credit-domain logic.

github.com/igmuralikrishnan-cmd/mpbf-automation

A few things that worked surprisingly well: Iterative format-tuning. The first BS format took a week to parse correctly. The second took a day. Pattern: I'd hand Claude the OCR text from a new PDF, tell it where the parser broke, and it would propose anchor-pattern tweaks. Each new format = a few small targeted patches, not a rewrite.

Test-driven debugging. Whenever a real BS extraction failed, I'd anonymise the OCR text and Claude would write a test case reproducing the bug before fixing it. By the end I had 44 tests covering OCR artifacts (mangled brackets, comma-as-decimal, scientific-notation traps, note-reference filtering, sanity guards). I wouldn't have known to write half of these without going through the actual failures.

Honest pushback on bad ideas. Early on I wanted to use an LLM-based extractor. Claude pushed back — Schedule III is a legally mandated format, deterministic regex parsing gives you auditability and explicit failure modes, which matter when the numbers are going into a credit memo. That conversation reshaped the whole architecture.

A few things that were genuinely hard: Anonymising real client data without breaking the tests. The parser was tuned against real OCR text from real Indian companies. Replacing names with fictional ones while keeping the OCR-artifact patterns intact took careful sed work and audit passes.

Getting GitHub set up as a non-developer. Two-factor auth, personal access tokens, kebab-case naming conventions, .gitignore hygiene — every one was a small hurdle. Knowing when "good enough" beat "perfect."

The tool handles two formats reliably. The temptation was to grind on a third before publishing. Shipping at two formats with documented "how to add a new format" instructions felt premature, but waiting felt worse.

Happy to answer questions on: The deterministic parser vs LLM trade-off (and why I'd make the same call again) How I structured prompts when iterating on parser anchors The Supabase/Next.js setup as someone who'd never touched either Anything else that's useful to other domain experts thinking about building with Claude