rutagandasalim

we built clawnewz for the claws.

agents can read, post, and debate in real-time. fully autonomous, fully agent-driven. think of it as hacker news, but for lobsters. join the reef, let your agent signal.

https://clawnewz.com

lmao checkout https://runclaw.sh

yo, i’m 17 and been building projects for a while. every “next big boilerplate” i tried either broke, felt outdated, or forced me to rebuild the same stuff again and again. i’d lose weeks wiring auth, payments, seo, and ai just to launch something simple.

so i built my own — shipfree. it’s a modern next.js saas boilerplate made for this new agentic + llm era. built on next.js / bun / drizzle / prisma / tailwind / stripe / polar / Better-Auth /Ai agent skills / Base-ui / i18n / Upstash / Sentry / ai-sdk / tanstack, everything’s wired and ready so you can go from prompt to product in one shot.

you can literally spin up an llm-powered product in hours. no setup hell, no 2019 tech. just clean, fast, production-ready code.

made $1,800 so far from early users and the feedback’s been wild. i’m not tryna make the “ultimate boilerplate,” just one that actually helps indie devs ship fast and make money.

check it out here: https://shipfree.revoks.dev

feedback, ideas, or roast all welcome — i just wanted to build something i wish existed when i started.

Great article bro

Most AI directories feel like ad farms. I wanted something clean, open-source-friendly, and actually useful to developers. So I built AIThings.dev . It’s not perfect, but I focused on clarity, speed, and community. Curious what y’all think — especially if you’ve tried building something similar.

I made aithings.dev because I got tired of chasing random AI links all over the internet. It’s a clean, fast directory where you can find everything AI-related — tools, tutorials, communities, tweets, books, and other resources that actually help you build or learn.

It’s minimal, no ads, no spam, just useful links with short context. Still early, but growing fast — feedback or suggestions are super welcome!

Hey HN,

I built aithings.dev , a curated directory of AI tools, because I was tired of wasting hours digging for quality apps.

In 2 weeks, we hit 10k monthly visitors, purely from organic traffic, no ads. The breakdown:

60% came from Twitter shares

30% from Reddit/HN mentions

10% from SEO

It’s simple: each tool has a mini-review, tags for categories, and a “use case” section so you instantly know if it fits your workflow.

I’m sharing how I built it, grew traffic, and set up the site for potential sponsorships, because I think small AI directories like this are underrated but insanely valuable.

I’ve seen a lot of AI tool lists pop up lately, and most die quietly after launch. I built one myself recently — mostly as an experiment to see what actually drives traffic for small projects like that.

A few things surprised me:

SEO still works if you target low-competition, long-tail keywords.

Submitting to other directories drives better traffic than socials.

People care more about clean UI and fast load times than flashy branding.

Curious how others approached this. What’s worked best for you when trying to grow a small side project or resource site?

Hey folks, Two weeks ago I launched a small AI tools directory for devs — just a side project to collect the most useful tools, books, and communities. Didn’t expect much, but it somehow hit 10k unique visitors in 14 days.

Here’s what worked:

SEO early. Simple keywords, clean structure, and fast load speed.

Hacker News + Reddit. Drove the biggest spike in traffic.

Manual curation. Quality > quantity. No AI auto-listings.

What didn’t:

Social media posts. Vanished in hours.

Skipping newsletter signups early. Big miss.

Not selling anything — just wanted to share what I learned for other indie devs or makers building in public. If you’re curious, here’s the site: https://aithings.dev

Happy to answer questions about traffic, SEO, or the tech stack.

Every AI directory I found was either outdated, stuffed with affiliate links, or just bad UX.

I wanted something dead simple — searchable, tagged, and actually useful for developers.

So I made aithings.dev .

What’s inside:

hand-picked AI tools, all searchable by use-case

Tags for dev, design, marketing, etc.

Clean interface — no login, no spammy popups

I update it weekly, and I’m adding a “discover” tab soon for trending tools.

I’d love honest feedback — what features would make it genuinely valuable for you?

(also open to collabs/sponsor ideas if anyone’s into that kind of thing)

A few days back, I posted AIThings.dev, a curated directory for AI tools and communities. We’ve now grown to [insert number] monthly visitors organically, mostly from devs, indie founders, and AI builders.

I’m now opening up for:

Tool submissions

Newsletter sponsorships

Collabs with other AI/Dev projects

Check it out here: https://aithings.dev

Hey folks,

I’ve been building AIThings.dev — a curated directory that brings together AI tools, resources, books, videos, and communities for developers, founders, and creators.

The site’s getting solid traction from engineers and indie builders exploring AI projects daily, and I’m now opening up a few sponsorship spots for brands and products in the AI ecosystem. got over 3k page views on a day

If you’re building something in AI, dev tools, or productivity, sponsoring AIThings.dev is a chance to reach a focused audience of early adopters and makers.

Check it out here: https://aithings.dev

claude opus 4.5 is an incredible model i just one-shoted https://aithings.dev with it

lmao

I spent weeks building aithings.dev — a directory curating all the actually useful AI tools. Wanted to make discovery simple, clean, human-curated.

Then I got curious and asked Claude 4 Opus to “rebuild aithings.dev from scratch.” It did. In 45 seconds. Pages, search, categories, design; all there.

Not gonna lie, that stung. But it also made me realize something: AI’s moving way faster than our comfort zones, and building with it > fighting it.

Still shipping aithings.dev though

Hi HN,

I’m a software engineer with 3 years of experience, and I’ve just updated my portfolio. It highlights my projects, problem-solving approach, and blog posts on engineering topics.

I’d love your feedback on what works, what’s missing, or any improvements you’d suggest.

Thanks for taking a look!