stardance has been extended another month! the new deadline is october 31 :)

You are browsing as a guest. Sign up (or log in) to start making projects!

akiva_yevdayev

@akiva_yevdayev

Joined June 7th, 2026

  • 8Devlogs
  • 1Projects
  • 1Ships
  • 11Votes
Ship Changes requested

What did I make?

I made Sh’elah (shelah.org) — the Torah Encyclopedia, literally. a searchable library of Torah and judaic texts and commentary (all powered by Sefaria’s texts and made to feel easy to use), an AI assistant that answers questions on Jewish law (halachah) by pulling information from primary sources like the Torah and judaic texts instead of just guessing, and the practical stuff people actually need everyday — live prayer times (zmanim), a Hebrew calendar, and how different communities observe different customs. The AI is built to always point you back to your own rabbi for anything that’s actually a different based on community and needs a ruling, and it steps out of the way entirely for anything medical or safety-related, and has safeguards to protect it from answering strange or unrelated questions or from being prompt injected (because we don’t want our site to get hacked lol). The prayer-times/calendar run off of your exact location, and the calendar shows the weekly Torah portion and candle lighting times too.

What was challenging for me?

Getting the AI to have safeguards, not hallucinate, follow judaic law and texts, and all set up took way longer than I had originally expected. It’s easy to make a chatbot that sounds confident; it’s much harder to make one that cites where an answer actually comes from, doesn’t quietly make things up, and knows when to deflect a question or malicious prompt. I also spent a lot of time on things nobody will ever see directly — locking down who can access what in the database, making sure a runaway request can’t rack up a huge AI bill (because this site is made for the public to be free, and not to make me go broke °~°), keeping the site fast and not-broken in English and Hebrew, light and dark mode, and working/looking well on phone or tablet-sized screens. Giving the AI real tool-use so it reaches for live prayer times/calendar/texts itself was its own project, and I found out at one point my login system and database weren’t even linked correctly, silently breaking database reads/writes (was a pain to fix…). There’s also a bug where the page jumped up by 5-10 chapters at once which I fixed (and have been trying to fix that issue for MONTHS!)

What am I proud of?

That it actually exists as an actual product and as a solution instead of just an idea living inside someone’s head. Every page has a real link you can share — a specific judaic text, an AI answer, a specific calendar day— and it opens back up exactly the way you left it. The commentary and translations are genuinely fast now (they were super buggy and slow before), the calendar actually gives candle-lighting times and areas in my app where the torah portions are and had a huge glow-up. I also went from 60% test coverage to over 99%, with nearly 4,000 tests passing cleanly. Keep in mind the whole thing was built by myself (yes ofc was built using ai but without that it would’ve taken years to make), end to end, including a real test suite, real security practices, accessibility support, and full legal documentation and copyright license, and not just a prototype held together by hopes and prayers.

What should people know so they can test it?

Try asking it an actual halacha question (but since most of you guys aren’t Jewish ask it a question you’ve had on the old testament or on Judaism maybe) that you may have wondered about and see if it gives you a real answer with sources instead of a vague and incorrect answer. Open a Torah portion and look at commentaries or a translation of a specific word. Switch it into Hebrew and make sure nothing breaks. Try it on your phone. See the prayer times based on location. Look at the calendar. Go bananas! Just know that if there is any issue at all, contact me through my email [email protected] and I’ll try my best to fix it as soon as I can.

  • 8 devlogs
  • 96h
Try project → See source code →
Open comments for this post

4h 46m 11s logged

Sh’elah — Devlog 8 WE FINALLY SHIP TODAY!!!!!!!!!!!!!!!!!!!!!!!!

Over the past week or so, I had…

  • Redesigned parts of the ai look again so that it doesn’t look like ai slop :)
  • Gave the whole site links and web addresses whic h means any page or ai chat or settings u have and wanna give someone the link they can open to the same place as you (major issue fixed!).
  • Added /signin and /profile as real pages that layer on top of whatever you’re looking at, so signing in from a legal or help page brings you right back where you started.
  • Found and fixed why the AI sometimes gave no answer at all: the sign-in check between the site and the database was rejecting valid logins, which quietly broke saving your conversations and preferences. (YAY MORE BUGS FIXED)
  • Sped up word/translation lookups. A word Sefaria didn’t recognize used to try several spellings against the dictionary and then several more against translation, one at a time — now it takes a second (maybe 2 if needs more sources).
  • Fixed animation and fading issues, as well as issues when switching reading layout, switching commentary verses, and jumping to a cited passage (which, it turned out, didn’t actually highlight anything yet).
  • Fixed the reader losing its place. Scrolling to load more text, or loading a previous chapter, could silently jump the page’s address to the wrong chapter. It now tracks what you’re actually reading, not just whichever paragraph happened to load first. (I’VE BEEN TRYNA FIX THAT ISSUE FOR MONTHS!)
  • Cleaned up account and privacy details: a smaller profile menu, a delete-account warning that isn’t half-pink in dark mode, and your data export now actually includes your AI chats.
  • Fixed a leftover database error that had been showing up in the logs from a migrations table that never existed — it’s created properly now, with the right access rules attached.

WE SHIP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

0
0
17
Open comments for this post

12h 28m 2s logged

Sh’elah — Devlog 7 — WE SHIP THIS WEEK!!!!!

Over the past week or so, I had…

  • Gave every page of the site its own real address. Any text, prayer, calendar day or AI answer now has its own link that opens straight to that page, even on a refresh. Old-style links still work too.
  • Made AI answers shareable. Anyone can hit Copy Link to send a specific answer, or open it as its own page, and it stays out of search engines unless it’s meant to be public.
  • Went through a 15-item punch list end to end: infinite scroll no longer jumps around, the commentary sidebar loads way faster and lighter, various calendar issues are fixed, parashah and commentary names are now accurate and properly ranked, community pages have full Hebrew translations, the header date now follows your actual location, loading spinners recover on their own when a connection drops, and implemented a bunch of Hebrew translate and bolding fixes.
  • Completely Redid EVERYTHING about the AI:
    • Redid the AI window’s entrance animation so it grows out of the Ask button on desktop instead of just popping in, and rises as a proper sheet on phones.
    • Moved the Ask button onto the phone’s top bar instead of hiding it behind a Search tap, and gave the bottom tabs real icons above their labels with even spacing.
    • Added a new ai small window, new ai fullscreen window, and new ai chat sharing links that legitimately work.
  • Polished motion sitewide: screens fade up, buttons get a proper hover/press/focus feel, every emoji became a matching icon, and calendar hover states got fixed instead of going backwards (the close button used to lighten on hover, now it darkens like everything else).
  • Built a real holiday detail card for the calendar, with accurate clock times and links straight into the reader.
  • Fixed prayer and reader text losing its bold and italic formatting when pulled from the source library.
  • Fixed the reader jumping around when loading earlier text, and gave it a slimmer bar with commentary that preloads before you tap it.
  • Locked down the AI’s spending: the plain (non-agentic) chat route was quietly skipping the budget check, and a bug in the model-calling code could leak the API key. Both are fixed, and every path now respects the daily budget.
  • Added a circuit breaker to the rate limiter so a database lag can’t take the whole site down with it, and made sure static files are never rate-limited.
  • Cleared out SonarCloud’s entire backlog again: dead code removed, regexes hardened against slowdowns, and a chunk of new tests written along the way.
  • Made Turnstile (the invisible spam check) actually invisible instead of showing its widget.
  • Reconciled a stack of parallel work — calendar icons, i18n, reader fixes, security fixes — that had drifted across a few branches, merged clean.
    Let me know if there is anything y’all wanna see on my site in the future

p.s. WE ARE ALMOST SHIPPED, but i still want those hours to count so this is not the last devlog.

0
0
10
Open comments for this post

11h 50m 16s logged

Sh’elah — Devlog 6

Over the past week or so, I had…

  • Fixed certain dark mode values so they match the overall theme of the site.
  • Added an ai symbol in the shape of a star and added animations to the searchbar when the ai is thinking, adding an ai feedback button, and fixed spacing and other issues with the ai answers.
  • Added a commentary button to the reader’s top bar to show people how to use it
  • Fixed zmanim (prayer/holiday times) on Holidays and fast days, added fast start and end times, and gave the AI Hebrew-date math tools.
  • Finalized the legal pages with real operator info, registered a DMCA agent, and added an age confirmation.
  • Went through every SonarCloud finding and the quality gate now passes, with the security and reliability ratings both at A.
  • Wrote a big batch of new tests. Coverage went from 60% to about 84% overall, and all 3517 tests (yes ik its a lot of tests) pass cleanly. (yes somehow it was 60% before when I explicitly added tests for 93% coverage · ~ ·)
  • Rotated the leaked Gemini key and cleaned it out of the repo history. (correcty this time), and merged two drifting copies of the code, so shared pieces like the AI answer builder now live in one place.
  • Rewrote the README, added a changelog, documented every environment variable, and regenerated the database docs from the live schema.

Let me know if there is anything y’all wanna see on my site in the future

p.s. shipping v1.00 in a day or two!!!!!! FINALLY!!!!! (This may take longer than two days but hopefully not!)

0
0
15
Open comments for this post

14h 16m 31s logged

Sh’elah — Devlog 5

Over the past week or so, I had…

  • Gave the AI real tool-use, allowing it to get live prayer times, calendar dates, and texts as it needs them, instead of having everything be pre-loaded at each request.
  • Finalized the legal pages and filed my site for DMCA Copyright protection for 3 years.
  • Added self-serve privacy controls, where you can now export or delete your own account and data yourself.
  • Added a feedback button on AI answers so people can flag bad ones directly.
  • Added accessibility keyboard/screen-reader support along with their appropriate tests in CI.
  • Fixed a security issue where a malicious AI-cited link could execute code, and added a bot-check in front of the AI endpoint to cut down on abuse.
  • Fixed the caching bug from last devlog this time; pages get served from cache properly now instead of requesting from the server on every load.
  • Fixed a bunch of small little annoying bugs like the page jumping back while scrolling, the wrong section getting highlighted, calendar color glitches, and animations not loading.
  • Fixed a security-check script that had quietly been failing every single scheduled run for over a week.
  • Spent alot of time simplifying complex functions across the codebase to make it more reliable.
    Let me know if there is anything y’all wanna see on my site in the future

p.s. getting closer to that v1.00 site goal every day — planning on achieving it next week!

0
0
14
Open comments for this post

10h 20m 10s logged

Sh’elah — Devlog 4

Over the past week or so, I had…

  • Fixed an issue with RLS in Supabase so that one user doesn’t see another user’s personal info, as well as security issues with Vercel and Clerk (Which was a pain to fix :<)
  • Found out my login system and database weren’t linked to each other correctly, which was breaking authenticated reads/writes, and fixed it
  • Added an ai usage tracker and fixed old usage records so the spending log is correct, and so I don’t go broke when other people use my site’s ai
  • My webhook (discord error bot) was malfunctioning (and still kinda is in clerk :<) and no longer is! YAY MORE ERRORS FOR ME! (at least I’ll know why they happen :|)
  • Fixed a bug where the site was incorrectly caching files in browsers, making things slower and more expensive (yay less money to spend!!!!!)
  • Ran accessibility tests and fixed any issues they found, and made my site more ready for releasing v1.00!
  • Removed old files
  • Fixed some legal documentation issues (like my Privacy Policy and ToS) so I don’t get sued!!!

Let me know if there is anything y’all wanna see on my site in the future
p.s. I’m planning a huge commit soon announcing version 1.00 of my website so if you haven’t seen my first devlog announcing that, go check it out.

0
0
77
Open comments for this post

10h 38m 16s logged

Sh’elah — Devlog 3

Over the past week or so, I had…

  • Fixed a bug where a malformed cache config could crash the whole app on startup.

  • Split a file that handled AI question-answering into smaller, cleaner, more compact files, and added tests to make sure that both versions (one for gemini and one for claude) always answered the same way with the same guardrails.

  • Sped up busy/resource heavy pages (library, prayers, texts, daily study, and the calendar lookup) by adding a shared caching layer, so they don’t request the database on every single request anymore.

  • Added rate limiting across the whole site instead of having it scattered in different places.

  • Cleaned up a batch of files that were referenced in the code which was uncommitted and caused boot errors.

  • Simplified a few functions that had been made too complex to safely maintain.

  • Sped up cold starts by delaying AI library imports until they’re actually needed.

Let me know if there is anything y’all wanna see on my site in the future
p.s. I’m planning a huge commit soon announcing version 1.00 of my website so if you haven’t seen my first devlog announcing that, go check it out.

0
0
16
Open comments for this post

9h 22m 5s logged

Sh’elah — Devlog 2

Over the past 9 hours or so, I had…

  • Removed a leftover routing rule in Vercel that was returning a 404 error in my production site.

  • Added a server-side daily budget per user, so if someone goes past it and heavily uses the AI past what’s normal, they get rate limited and can’t spam multiple requests at once. Also fixed an issue where AI usage was being reported as $0 when it wasn’t.

  • Updated my site’s README.md on GitHub, fixed a license mismatch, and added a CONTRIBUTING.md and a code of conduct.

  • Old logs and history get deleted on a schedule now, so trash doesn’t build up over time.

  • Built a dark-mode accessibility checker and fixed contrast issues. Also integrated circuit breakers so when an external resource fails the site doesn’t crash.

  • Added About/Help/glossary pages, a sitemap, a feedback widget, and analytics that you can opt into.

  • Added CI checks and Vercel Speed Insights to track loading times.

  • Swapped the GPS permission for zmanim (prayer times) based on location to cookie/IP-based location instead.

Let me know if there is anything y’all wanna see on my site in the future

p.s. I’m planning a huge commit soon announcing version 1.00 of my website so if you haven’t seen my first devlog announcing that, go check it out.

0
0
7
Open comments for this post

22h 8m 53s logged

Sh’elah — First Devlog:

I’ve been working on Sh’elah for a while now and finally uploaded it here. It’s a Jewish learning app that combines a searchable Torah library (similar to Sefaria) with an AI tool designed to actually answer your halacha questions. Instead of just throwing related sources at you that don’t end up answering the question, it walks you through the actual answer, explains the reasoning, cites the sources, and tailors everything based on your community’s specific customs.

What it does today

  • Answers questions across any area of Jewish law using primary sources rather than generic guesses.
  • Allows you to search the library with customs broken out by community (Ashkenazi, Sefardi, Teimani, and others).
  • Calculates live zmanim (prayer times) and a Hebrew calendar based on your exact location.
  • Ends every answer with a clear reminder: this is for learning purposes, not an official ruling, and real questions should always go to your rabbi.

It works right now, but it’s still in the early stages, so I want to be upfront about what still needs work before calling it a complete release.

Making the AI reach for things, not just recite them

  • Right now, the AI only knows what gets put into the prompt ahead of time. I am working on moving it toward real tool use so it can pull zmanim, calendar dates, commentaries, and community customs dynamically as needed.
  • Judaic texts and laws will always remain the main priority, with web searching kept strictly as a last resort.

Getting the safety layer right (in progress)

  • Halacha touches sensitive material, and I want to make sure a younger user doesn’t receive graphic content when the real answer should simply be “ask your rabbi for details.”
  • Any queries related to medical issues, mental health, or abuse will automatically route to real professional resources rather than generating an AI ruling.

Behind-the-scenes technical updates

  • Breaking down a backend file that got way too large so the code is easier to maintain and debug.
  • Securing the caching layer so it handles concurrent load safely.
  • Adding circuit breakers to prevent a third-party outage from crashing the whole platform.

What needs to happen before full launch

  • Verifying every feature works properly while keeping the user experience smooth and simple.
  • Completing a thorough security review (already finished).
  • Setting up error tracking and rate limiting to protect the site from abuse.
  • Performing a full accessibility audit.

Building this isn’t going to be easy, and the order of these steps will probably shift around. However, this is the general direction of the project, and I’ll share more updates as new features roll out.

0
0
15

Followers

Loading…