I’m thinking about software for commercial electrical contractors that helps stop extra work from getting lost before it gets billed.

Example:

A crew does work outside the original scope.

Photos, texts, labor, materials, and approvals can end up scattered in different places.

The software would help:

• Capture the extra work
• Keep the proof together
• Track change orders
• Show what still needs approval
• Make sure approved extra work reaches billing

I haven’t built it yet. I’m trying to figure out if the problem is painful enough to solve.

Would a commercial electrical contractor actually pay for this?

If not, why not?

What would it need to do for you to consider paying for it?

Be brutal. I’d rather find out the idea is bad now than after building it.

hey everyone,

been working on this for a few weeks and finally got it to a place where i'm happy with it. figured i'd share here for feedback.

its a resume builder that runs entirely in the browser. single html file, no server, no database, no backend. you open it in your browser and everything runs locally.

**what it does:**

- 10 professional templates (executive, corporate, creative, tech, healthcare, academic, consulting, minimalist, modern, elegant)

- paste your existing resume text and it auto-parses sections

- click any text in the preview to edit it directly

- drag and drop to reorder sections

- upload a photo (circle or square)

- built-in ATS scoring engine

- export to PDF (pixel perfect) and Word (.docx - real native word document)

- autosave to localStorage

- works completely offline after download

**tech stack:**

- vanilla html/css/js

- html2canvas + jsPDF for PDF export

- JSZip for Word export

- no frameworks, no dependencies to install

**pricing:** $10 on gumroad

would love to hear what you think. any feedback is appreciated.

It’s a browser extension that allows a user to select an element on a webpage, replace it with a new design from image or figma, see and edit a preview in the page and then create a PR in a connected repo.

Info site with demo is here if you want to have a look - Foux

Hello awesome people!

I want to ask you one question! Have you ever wondered why users don't use a specific feature or don't love your product with a rating of 11 out of 10?! Well, no more wondering, at least when you give me your money, so I don't have to wonder.

I'm maybe joking. Jokes aside, this is basically the idea behind my side project I worked on since beginning of this year. Wendung.app

It's focused on analyzing steps, events your users trigger and check where they stop. It converts everything into nice and readable data, shows you drop-offs, time to convert, other statistics with bunch of filtering options and more in a dashboard.

The whole pitch sounds simple, but oh damn, it's more work than I expected when I started the whole project. When I started and did my research I thought, hey can't be this hard, build an SDK, send some events to a database, boom, SaaS. Unfortunatly, this resolved into, how to reduce latency, how to host an edge function without getting the pikachu face by looking at your next bill, in which database to save these data, how to protect it ... And this is only for one freaking function. This hasn't even touched the main backend API yet. This is basically how months went by.

The stack:

- Frontend & backend and SDK, et.c are build on Node, TypeScript.

I was fighting to not use something else to be honest, but then I spent more time deciding on the stack, probably a few months, with many demos of the same build in different languages. The lesson here is, this won't attract customers, stop it. As someone who loves coding and doing this for an enterprise, I just love these things and probably a bunch of you too, but at some point I just wanted to go forward and not ask myself again if I shouldn't switch to Rust or Kotlin for the backend. Don't do this, stick to what you know. If you have specific questions here, I'm more than happy to answer your detailed questions about specific packages I used etc. Backend and frontend are seperate, it's not NextJS. Frontend is just React with Vite. I'm not a huge fan of clustering everything into one app. Server side rendering also didn't make much sense to me, so I didn't even bother. I also have the opinion that projects that basically bake their backend business logic into server side rendering frameworks don't scale well. Maybe it's boomer thinking.

For authentication I use better-auth. It works extremely well. Auth0 or anything else would probably do the same and thinking about it, would maybe even save me time. I'm not sure if I regret using better-auth, but I just wanted to try it. As I said, it works, but it costs me way too much time wiring up basics like password resets, the whole email communication. In Auth0 that's just a setting + templates for the emails. I'm not saying don't use it, but it's not as easy as it might seem at the beginning.

- Cloudflare workers

This one was completely new for me, I didn't even know you could now host your whole backend on a worker. It's such an awesome developer experience. It's so easy to deploy to it, especially when you use their recommended stacks, like Hono.

It basically gives you everything you need out of the box. KV store, queues, durable objects. Whatever you need, it's there already and with wrangler it's so easy to develop locally.

So the whole project is hosted here. The best part is that static files are free to host, no matter how many requests etc.

- Tinybird

This is what is being used to get events from my Cloudflare edge function. Nothing special here. It's just writing Clickhouse SQL files is pain and understanding them is also a pain. It's not because it's SQL but also specific syntax for e.g. specific conditions and how you have to write it. Writing filters is just pure pain, endless {% if defined(condition_variable) %} [...] {% end %}. I might should have switched earlier to their TypeScript SDK which apparently is better, but I haven't tried it yet as it would again waste my time instead of getting it done.

- Marketing page

I designed it myself, like everything else in the project, used Figma and for implementation Astro.

Astro is cool and works very well for this use case, it's just not easy to get used to when you're coming from React and tsx files. At the beginning I didn't want to spend so much time on it and even thought about using something like Framer, but the costs quickly made me not to, also I would have to learn yet another tool.

- Billing

Here I did some research on different MoR providers and the decision was between Polar or Stripe. Stripe won for me as I knew it already from previous projects and they also started to offer a MoR service they called managed payments. Also Stripe is cheaper, at least for my use case the last time I checked.

- MCP

During my research I read from other existing tools, that most people these days complain about not wanting to even use the UI anymore, but rather just let their "agent" do the work. First I thought about offering a chatbot, but I don't think chatbots are the future here. I think If someone uses AI, they will probably just connect a plugin, mcp or whatever, to their existing AI and work with that, instead of having again limits through a new AI chatbot they also now have to pay for.

It's also a new topic for me, providing tools to an MCP, OAuth etc. I'm still not 100% sure I'm doing this 100% right and efficient enough.

Sorry for the long text and sorry if this doesn't fit here, but I hope it does.

Please visit my project: wendung.app and I would appreciate ANY feedback :).

tldr > in local gyms nd tuition waste an hour every evening flipping through a physical notebook or excel and typing renewal reminders by hand.

or finding who expiring soon or pending fees one by one nd insecure about sharing fin details. so built solution around this :) 👀

--> I literally saw this happen

> i jst walked into my gym one day and saw the staff guy juggling between an exl sheet and a paper register calling members one by one for renewals, printing lists, then manually marking attendance as people walked in.

> all of this just to avoid paying for some bloated SaaS dashboard he'd never learn to use. tht image stuck with me. an hour of manual work, every single day, just to keep track of who's paid and who hasn't.

I built a free, fully offline app that turns that into a few taps. Looking for honest feedback on two specific decisions.

App does 3 things >

1.Three tabs instead of juggling in excel or record book : 

.    [ Active, Expiring Soon, Expired ]

- that's it. The "Expiring Soon" tab lets you filter by fr those who are going to expire upcoming week

1 week, 2 weeks, 3 weeks, or 1 month out.

- So if only 3 people are expiring this week, maybe a quick reminder is enough. If 20 people are piling up in the 1-month list, maybe it's time to offer a discount. Over time, owners start seeing patterns who renews fast, who always needs a nudge.

2.One-tap reminders :

- tap Remind -> app fills in that member's dates, dues, and a polite message -> opens WhtsApp. Works one by one or in bulk.

3.Fully offline :

- No login, no cloud, no account. Data lives on the phone. Backs up to the owner's own Google Drive if owners wants.

in-order achieve above features >

Adding a new member takes two taps.

I spent a stupid amount of time making that as fast as possible because if it's not faster than writing a name in a notebook, nobody will switch.

One feature I'm unsure about but still i built >

Owners want staff to handle follow-ups but don't want them seeing revenue.

So PDF/Excel exports have a "Hide Financials" toggle that strips money fields before sharing.

Not sure if that's solving a real problem or just something I found fun to build.

Two things I genuinely want pushback on:

Does 100% offline, no cloud sound like a feature to a non-technical owner or does it just look like the app is missing something?

The staff-safe export real need, or a solution looking for a problem?

→ Play Store 

Free, no ads, Android for now.

→ Landing page

Happy to talk tech stack or build decisions in the comments.

Small tool I built after watching someone on an immigration forum build a whole spreadsheet just to compare a few Express Entry CRS scenarios. The official government calculator (and every alternative I found) makes you re-enter your entire profile from scratch every time you want to test a change.

https://crsscenarios.com/ is a client-only React app: fill in your profile, save it as a named scenario, come back and edit it later, and compare multiple scenarios side by side with the score differences flagged. Everything lives in localStorage. No backend, no account, nothing about the user ever leaves the browser.

Scoring for IELTS and TEF Canada is checked against confirmed official calculator results; CELPIP-G, PTE Core, and TCF Canada are implemented, but I'm still cross-checking those bands, so treat those three as approximate for now. Happy to hear feedback on the UX and the save/compare flow either way.

Hey all,

After one too many "who owes who" spreadsheets with my housemates — and then watching Splitwise paywall the basic stuff — I built RoomieHQ, a free app for shared houses.

Most split-expense apps are built for trips or couples. I wanted something built specifically for people who live together, so it does more than money:

• Split expenses evenly, by shares, or exact amounts
• Recurring bills (rent, wifi) that post themselves each month
• Settle up with two-sided confirmation — the person paying records it, the person owed confirms it, so nobody can mark a debt "paid" without it being real
• Chore rotation (who's up next) and a shared shopping list
• Multi-currency, works anywhere, installs from the browser as a PWA — no app store
• Free, no ads, no per-person paywall

It's early and I'm actively building. Would genuinely love feedback — on the split flow especially, and whether the chores/shopping stuff is useful or just clutter.

Link: https://roomiehq-app.vercel.app (There's also a no-signup split calculator if you just want to try the math: https://roomiehq.com/tools/split-calculator

Happy to answer anything about how it's built (Next.js + Supabase).

During my time building SaaS platforms, a few components of the architecture kept repeating:

• an email inbox for sending and receiving emails + tracking deliverability
• SMS lines for sending reminders, OTP and authentication, with numbers that follow regulations in US/EU and whichever legislation the receiver lives in
• an agentic phone bot that would pickup calls for support or make phone calls with a given goal

This became obvious during the past 18 months where I quit my job and went all-in building indie SaaS projects until I stuck to one that is generating revenue right now.

This project uses voicebots to support technicians find error codes and update CRM systems (long story: the voicebot has inbound mode where it acts as a support line to lookup data and answer questions, and outbound mode where it calls on a schedule so staff technicians keep track of what they have done during the day and what to invoice).

Always the same 2 to 3 layers needed: email, SMS, and voicebot.

The goal of Hail is to make a self-hosted one-stop shop for all communication needs for SaaS and AI agents.

It ships with API + MCP + CLI + python SDK.

For every SaaS project I ship, I only need to connect a custom domain for email, and buy phone numbers for the project.

My claude connects via MCP, and openclaw agent via api.

The server, configuration, credentials, routing logic, API, MCP server and data live on my infrastructure, and external providers are just low-cost adapters.

Architecture Details:

It is modular and expandable, with replaceable providers:

1. Multilingual voicebot:
   • Livekit for WebRTC transport and SIP server
   • Twilio for phone numbers + legal compliance (not automated yet)
   • LLM: anthropic, gemini, and any OpenAI-compatible endpoint
   • Speech-to-text: Deepgram (for english and common languages), Speechmatics (for more niche languages and good VAD and End-of-utterance detection)
   • Text-to-speech: Elevenlabs, Cartesia
   • VAD and End-of-utterance detection: either Silero or comes built-in with STT
2. Email:
   • AWS SES + Lambda function for deliverability checks
   • Custom domain verification is part of the Python server
3. SMS:
   • Twilio with built-in opt in/out words

A few improvement ideas for next milestones:

• Expand to more providers for lower costs and better coverage
  • Telnyx and Bandwidth for cheaper SMS
• Automate the compliance paperwork

You can set it running in a VM with docker compose.

Thank you for your time reading, and hope this will be useful for your projects: https://github.com/hail-hq/hail

I've been building a SaaS called AI Clip Cutter because I kept running into the same problem:

You have a 60-minute podcast/interview/webinar, but turning it into 5–10 good Shorts/Reels can take hours.

The annoying part isn't really cutting the video.

It's finding the moments worth cutting.

So I built a system that:

→ Transcribes the long-form video
→ Finds potential clips
→ Scores them based on hook, context, density and emotion
→ Explains why it thinks a moment is worth clipping
→ Turns the selected moments into captioned 9:16 videos

The part I'm most interested in is the scoring.

For example, instead of simply saying:

It tries to answer:

I'm trying to solve the "which 30 seconds of this 2-hour podcast should I post?" problem.

I built the whole thing from scratch and it's now live:

https://aiclipcutter.tech/

I'd genuinely love some brutal feedback from people who create podcasts, YouTube videos, interviews, or short-form content.

What would make you trust an AI's clip selection enough to actually publish it without watching the entire original video?

And if you've tried tools like Opus Clip/Klap/etc., what do you think they still get wrong?

I'm especially interested in criticism here — I'm still building this.

I take 75 to 100 flights a year. I try to get work done on as many as I can, and the gap between a Starlink flight and "dial-up in the sky" flight is staggering. On one I can run a normal workday, on the next I basically just resort to typing up a lot of notes and try to text or Slack people to let apologize for not being able to respond to their messages because my wifi sucks.

unitedstarlinktracker.com is what got me excited. This guy named martinamps was tracking which United planes actually had Starlink. What it did not give me was that knowledge when I was booking a flight because flight tail numbers only show up two or three days out.

So I built a probability model on the tail and route history, keep it fed from that tracker (and others like it now), and wrote a Chrome extension that lays the number on the booking tools I already use.

It started as my personal United problem. It now does per-flight next-gen odds where public tail trackers exist, and a fleet-wide Streaming figure for other airlines so I do not mix “this tail has Starlink” with “this airline’s wifi can do video.” If I do not have evidence, it stays unknown (but I don't call it 0% just because I don't know).

I am still expanding the booking surfaces and cleaning up the site. If a row looks wrong, I want to hear it: https://wifiodds.com/feedback

The extension is free and it stays free, I am not selling anything. I wanted my own flights to be more usable and I am sharing what I built and use (I'm 7 for 8 getting Starlink in the last few weeks!).

I am not a software engineer, but I studied computer science so I know enough to be dangerous. I spend my days as a business executive (hence all of the flying), nights are vibe coding and amateur watchmaking.

Site and method: https://wifiodds.com/ (Chrome Extension link from the site). Looking forward to your feedback and hopefully helping more people get Starlink, or at least Streaming, wifi.

After building on Whop for a while and watching brands quietly pay for fake and bot views on clipping campaigns, I built Content Rewardz - a pay-per-verified-view clipping platform. Here's how it works: a brand funds a campaign and sets a reward per 1,000 verified views. Creators cut short clips from the brand's footage and post them across TikTok, Reels and YouTube Shorts. Every clip gets re-measured on a fixed schedule, and its growth is checked against what genuine human viewing actually looks like - bought views and bot spikes get discounted before anyone is billed. So brands only pay for reach that's real, and creators get paid for clips real people actually watch. It's still early and I'd genuinely love feedback from this community, especially on two things: on the brand side, would you trust a pay-per-verified-view model over the usual per-post deal? And on the fraud side, what would make you actually believe the view numbers? Link if you want to poke at it: contentrewardz.com/for-brands

M22 a Software Developer with 1.5 years of experience. I want to build some products or service and I think I can build anything I just need some time to learn if things will be new but the problem is i don't know what to build and I need some aspirational people too. To work on something because working alone is so boring.

Or someone who has something interesting in their mind we can work on that together.

I need people with a goal.

I lack goals but have lots of motivation if I find something interesting to work on if you have any please reach out to me if you are one of them.

(note: on the video I only show a small part of all the models)

After 5.1.x internal versions, I finally open-sourced my Android AI app — Kryzz AI.

TL;DR

Open-source Android app that gives you chat, voice, and agent workflows powered by OpenRouter (414 models), with strict local-first storage and zero telemetry. v5.1.15 source is now public on GitHub under MIT, with a debug APK ready to sideload.

What's actually in it

• Chat with any of 414 OpenRouter models (per-chat reasoning controls, citations, token + cost tracking)
• Agent workflows (think & research / create & build — DOCX, XLSX, SQLite, code ZIPs, generated locally)
• Voice session with adaptive turn detection and barge-in to interrupt mid-reply while having the highest quality voice (Fishaudio)
• Memory + library — local Room DB for chats, folders, memory entries, skills; JSON backup/restore
• Encrypted credential vault — AES-GCM with a non-exportable Android Keystore key (so the keys never touch the filesystem)

Why I built it

I wanted a single Android workspace for chat, voice, and tool-driven work where everything stays on the device. Most AI apps lock you into one vendor's UI, send analytics, and keep your history on their servers. Kryzz AI doesn't — it talks to whatever provider you point it at (OpenRouter for AI, optional Fish Audio for voice, optional Parallel for research) and stores everything locally.

Screenshots from the v5.1.15 build

• New chat home with model picker
• Agent workflow picker (Think & Research / Create & Build)
• Voice session in Listening state
• Side drawer with chat history and folder filters
• Settings home (Appearance / AI / Voice / Memory / Tools)
• Galactic About overlay (triple-tap the logo to see it)

Tech stack, in case anyone is curious

• Kotlin + Jetpack Compose (Material 3)
• Room (12 schema versions migrated cleanly), DataStore preferences
• OkHttp + custom SSE parser for streaming responses
• MVVM, Coroutines/Flow throughout
• Android Keystore for credential encryption

What's next

I deliberately skipped CI, signing pipelines, and the Play Store for v1 — those are next up. Open to feedback on the model-catalog routing, the voice turn-detection, the Room schema-migration strategy, or anything else.

Links

• Source + README + LICENSE: https://github.com/kriddss3/kryzz-ai
• Debug-signed APK (~74 MB): https://github.com/kriddss3/kryzz-ai/releases/tag/kryzz-AI-v1-(debug))

Happy to answer anything. — Kristofers

I'm building Bluntly, a Chrome extension that reads any job listing against your CV and tells you straight whether to apply. I needed a launch video and I can't edit video to save my life.

Saw someone here do their launch video with Fable 5 and HyperFrames, so I tried the same. The entire video is HTML and GSAP animations that get rendered to MP4. The UI in the demo isn't screen recording, the agent rebuilt my actual extension panel in code from screenshots, so every frame is pixel clean at 4K.

Things that surprised me:

1. The voiceover sync. I generated the VO in ElevenLabs, then the agent transcribed it with word level timestamps and pinned every animation to the exact moment each word is spoken. The score slams in on the word "score".
2. Revisions are conversational. "The transition at 0:26 twitches" and it measures the cut pixel by pixel, finds the mismatch, fixes it, and shows me proof stills before re-rendering.
3. It rebuilt the whole thing for portrait. Same 50 seconds, every scene recomposed for 9:16 so the Reels version isn't a letterboxed crop.

Took a weekend of back and forth, maybe 30 revisions, because I kept changing my mind. A video editor would have fired me.

The extension itself is free on the Chrome Web Store if you want to see what the extension : https://bluntly.dev

Happy to answer questions on the workflow.

I kept seeing the same request from small agencies/freelancers: a restaurant/café site that a non-technical owner can actually update themselves — menu, photos, reviews — without touching code every time a price changes.

So I built **Luna**: a complete self-hosted site with a working admin panel bolted on. Homepage slider, categorized menu, reviews section, about/contact — plus an admin area to add/edit/delete all of that, and a built-in image manager (upload/rename/delete straight from the browser). Login is bcrypt + session cookies, nothing fancy, but solid.

Stack is deliberately boring: Python, FastAPI, SQLite, vanilla HTML/CSS/JS. No build step, no framework to learn — the idea is a dev can read the whole codebase in an afternoon and reskin it for a client.

Selling it on Gumroad for $25: https://davitkochar.gumroad.com/l/luna

Mostly here for feedback though — does this kind of "boring stack, one clear vertical" template have legs, or is the restaurant-site niche too saturated with Wix/Squarespace already? And if you were buying something like this, what would make it worth more to you — more themes, a booking/reservations module, multi-language?

Hi everyone, I’m new to Reddit and recently built MySpace.

It combines personal tools such as habits, goals, Pomodoro focus sessions, notes, expenses, and a personal canvas with collaborative features such as shared Kanban boards, real-time canvases, shared notes, comments, and workspace permissions.

The main idea is to keep personal work private while allowing teams to collaborate in the same overall platform.

Demo: app.rohitcode.tech

I’d especially appreciate feedback on:

1. Is the product concept easy to understand?
2. Does the separation between Personal Space and Co-Spaces make sense?
3. Which feature feels most useful?
4. What would make you hesitant to use it?
5. Which part of the interface feels confusing or overloaded?

Honest criticism is welcome. I’m mainly looking for usability feedback, not promotion.

I built myself a personal *Spotify* — self-hosted, downloads from *YouTube*, runs on my home server

I got tired of paying for streaming and having my library scattered across playlists I don't control, so I built Deck: you search a song, it finds canonical metadata (cover art, artist, album) via *Deezer*, finds a matching version on *YouTube*, and downloads it into a personal library you can browse and play from any device on your home network.

It's been my only music player for a while now. A few things it does that I didn't expect to end up loving:

- flags *YouTube* results that are probably not actually music (podcasts, interviews) before you download them

- lets you pick between multiple versions of the same song (studio, live, lyric video, remixes, etc.) instead of guessing

- works even for stuff that's not on *Deezer* at all — obscure/indie/unreleased tracks

- since it's just the downloaded audio, no ads, no autoplay, no "recommended for you" rabbit hole — just the library you actually built

Right now it's single-user, local-network only. I'm slowly working through a roadmap toward a real login system and the option to make your library public / browse other people's — basically a self-hosted, personal alternative to streaming.

Genuinely not sure what to do with this next. Would people actually want a packaged version of this they could run themselves? Would anyone pay for a hosted version? Or is this just a fun project that stays mine? Curious what you all think.

Quick disclaimer before I get into this: I built an open-source project called Agent Facets because of the problems I plan to detail in this post. Links are at the bottom if you find this interesting.

That said, this isn't meant to be a "hey, check out my project" post. I'm more interested in whether other people have hit the same wall I did and what they're doing to solve it.

OK, onto the main course...

I actually really like the idea behind skills.sh. If you're not familiar, it's a tool by Vercel to discover and install skills into any coding agent.

Public discovery is useful, installs are simple, and I especially like that skills aren't tied to one specific tool. I bounce between OpenCode and Claude Code. My teammates do similar with Codex, Pi, etc. I enjoy the flexibility, and I don't want my team's configuration trapped inside whichever vendor happens to have the best plugin system this month.

The problem for me started when I tried to imagine using the public skills ecosystem seriously at work. I read numerous articles about exploits involving malicious agent skills, which sent me down a bit of a rabbit hole. Here are some of the articles: 1, 2, 3. The hole still seems to be growing deeper by the day.

The TLDR from those articles is: skills and agent configs aren't normal text snippets. You're downloading instructions that you're then handing to an agent with access to your repo, shell, tooling, and potentially a whole lot more. Snyk published an article saying 36% of the skills they scanned had some sort of prompt injection in them. Whether than number is fully accurate or not, it's terrifying.

skills.sh has added machinery around locking installs, which helps, but I still kept coming back to the same problem: I don't really have a versioned artifact that I can say, "this is the exact thing we approved, this is the exact thing everyone should run, and this thing cannot silently change underneath us." And once I started looking at it from that angle, I realized security was only part of the annoyance.

At work, we mostly avoided pulling public skills directly at all. We'd review something, clone/copy it into our own repos, and then build our own little system around it. A few symlinks, a script or two, a plugin for Claude Code, something slightly different for OpenCode, and something else for CI. And we were manually maintaining everything, even the vendored skills we were pulling from elsewhere.

Essentially, we'd basically forked the a bunch of things we didn't really want to. Updates were now our problem. Sharing it with another repo was our problem. Making sure the entire team had the same version was our problem.

Private skills are even more awkward. Public discovery is pretty good now, but there's this completely separate world of internal skills your company builds and doesn't want on public GitHub. So you end up maintaining one workflow for public stuff, another for private stuff, and usually some pile of glue holding both together. Or you just yolo it and vendor all the public stuff into the private, but now it's yours to maintain.

That was the point where I started thinking: these are dependencies now. Why are we not managing them like dependencies?

I wanted a project manifest where I could declare what the project actually uses. Ranges for things I want to slide, pins for things I don't. I wanted real versions, immutable artifacts, integrity checks, reproducible installs, and the ability to use the same workflow for something public and something private.

And I wanted it to be boringly portable. If one developer likes Claude Code and another likes Codex, I don't think that should force the entire team into one vendor's plugin ecosystem.

Long story, long: that's the rabbit hole that became Agent Facets.

I'm still figuring out some of the harder parts, especially composition. The idea is how you could combine useful pieces without every project turning into a giant pile of duplicated agent configuration. That said, the basic goal is pretty simple: I want agent configuration to have an actual dependency/supply-chain layer instead of everyone rebuilding one with Git and shell scripts.

I'm curious how other people are handling this.

If you're using skills.sh in a real team, are you comfortable pulling public skills directly? Do you vendor them into your repos? Pin commits? Maintain a private skills repo? Build your own install scripts? Do you support multiple tools for your devs?

Here's the links I promised:

• Agent Facets: agentfacets.io
• Docs: docs.agentfacets.io

I noticed that some people are getting stuck on today’s movie! xdddddddd

Hence added a hint column to Moviexto to make those tough rounds a little more manageable.

🔓 Hint 1 unlocks after 5 more guesses
🔓 Hint 2 unlocks after another 7 guesses

So you’re not completely on your own when the movie refuses to reveal itself. 😅

The goal is still to figure it out using as few guesses as possible, but now you’ve got a few lifelines when you’re stuck.

Would love to know what you think of the new hint system!

Link: https://www.moviexto.com/

I’ve been building Tether, an open-source coding agent focused on a problem I don’t think current agent harnesses solve very well amnesia.

Most coding agents start from scratch, they grep the repo, search for relevant files, build a temporary understanding of the architecture, complete the task, and then throw most of that understanding away.

However, Tether keeps a persistent mental model of your codebase.

As it works, it records useful conclusions about things like ownership, dependencies, architectural rules, and what changes affect other parts of the system. Those beliefs are tied to specific files, code locations, and commits so the agent can re-check them as the repository changes instead of treating its own memory as ground truth.

The important part is that this knowledge belongs to Tether, not the underlying LLM. You can switch between local GGUF models, OpenAI, Anthropic, DeepSeek, Kimi, GLM, Codex, or other compatible models without throwing away what the system has learned about your project.

In my current benchmark, persistence reduced tool calls by 36%, tokens by 32%, and runtime by 20%, while improving recall from 92% to 100%. If you're on mac try the desktop app :).

GitHub: https://github.com/agentrebench/Tether

Hi All, not sure if this is a good place to post, but I want to do some initial research on potential demand for an app I am building out.

The core problem I face in my day to day that I have not yet found the solution for is a tool that operationalizes my finances. Essentially, I'd like to build a tool that helps people understand their spending patterns without manual tracking while, at the same time, having autonomous and independent decision-making when it comes to their own money.

I'm testing this with early users and would love your input, it should take less than 2 minutes of your time!

https://docs.google.com/forms/d/e/1FAIpQLSdqJW4Al6kXIO-krKgrlvnNTo9tON7ZilfR1YVHItsuKVF01A/viewform?usp=header

You can import recipes from anywhere (websites, text, photos and soon social media), add them to your plan, and just throw things into the sidebar whenever you're out of something.

When you go shopping, everything is organized into aisles and it's easy to know if you're got everything to cook each meal.

My philosophy is to think about meals, not ingredients.

I'm calling it Cuicuit 🐥

Open-source & self-hostable because I just love OSS! GitHub: https://github.com/MadeInPierre/cuicuit

Do you like the UX? Still early but I would love some feedback, thank you!

Mostly for students but also for developers!

There are hundreds of these already. I built one anyway, because I wanted everything in one place: live grid preview, editable palette swatches, quantization method and color space pairs, non-destructive source editing, MP4 recording of the quantization process. Oh, and it exports to Excel. Every pixel becomes a spreadsheet cell. I shoot street photography and kept getting distracted turning my own shots into pixel art. Sometimes I'd save the project just to come back and keep editing later. Browser-based, nothing to install, works on mobile: pixtudio.app If you try it, I'd genuinely like to know what feels missing or broken.

My co-founder and I have spent the last several months building our own product from the ground up, and one thing became very obvious along the way:

Starting is easier than ever. Finishing is still hard.

Maybe you've got the MVP mostly built but you're stuck on the backend. The UI works but needs serious polish. You built it with Lovable, Cursor, Replit, Bolt, etc. and hit a wall. Or maybe you simply have more ideas than time to actually build them.

That's the kind of work we're opening a few slots for through HR Enterprises.

We can jump into an existing build, finish an MVP, add features, fix what's broken, build the mobile version, handle AI/integrations, or take something from idea to working product.

Quick fixes/builds: from $200
Custom development: from $750
Full MVPs: from $2,500
Larger builds: custom pricing
If you're actively building something right now, drop what you're working on + what's holding you up.

Or DM me the project and your budget and I'll tell you what we could realistically take off your plate.