Building indx.sh - a blog series

#webdev #nextjs #ai #buildinpublic

Introducing indx.sh - The Directory for AI Coding Resources

TL;DR: indx.sh is a curated directory of AI coding prompts, MCP servers, agent skills, and tools. Find what you need in seconds, not hours.

The Problem Every AI Developer Faces

You're using Cursor, Claude Code, or Windsurf. You know a good system prompt would make it 10x better. But where do you find one?

GitHub has thousands of repos with "cursor rules" scattered everywhere
Discord servers have gold buried in chat history
Reddit threads go stale
Blog posts are SEO spam
Prompt directories are not well designed

You end up writing everything from scratch. Again.

What I Built

indx.sh - A searchable, curated directory of:

AI Coding Prompts

Cursor rules for React, TypeScript, Python, Go
Claude Code configurations
Windsurf and Copilot prompts
All tested, tagged, and ready to copy

MCP Servers

Model Context Protocol servers for extending AI capabilities
Database connectors, file systems, APIs
Synced from the official MCP registry

Agent Skills

Reusable skill definitions for AI agents
Synced from the official Anthropic repository
Task-specific configurations

AI Tools

IDEs and extensions
CLI tools
Code review assistants

How It Works

Search or browse by category
Preview the full prompt/config
One-click copy / Download
Copy into your IDE

Free to browse. I'm building this for the community.

I’m a UX designer turned self-taught developer, and I got tired of the treasure hunt.

Every time I needed a solid Next.js prompt—for Cursor, Claude, Groq, Mistral, or whatever tool I was using that week—it turned into the same loop: watching videos, searching threads, reading posts, testing things, breaking things, and sometimes eventually getting it to work. A lot of time spent failing before any real progress.

As an autistic person who values efficiency over chaos, this drove me nuts. I didn’t want to spend half a day just figuring out how to centralize a route so changing a label wouldn’t require editing 500 files.

The frustrating part wasn’t that the answers didn’t exist — it was that they were buried.

Now that more people are getting into development and “vibe coding” is taking off, the ecosystem is exploding. MCP servers, Cursor rules, new tools dropping constantly. But discovery is completely broken. The knowledge exists, it’s just scattered, inconsistent, and exhausting to find.

So I built this to fix that.

indx.sh tries to fixes that.

How I Built It

This is also a dogfood project.

I built FabrkFabrk, a Next.js boilerplate with a design system, and wrote about it earlier. indx.sh is the first real product built on that foundation.

Honestly, both projects have been uphill battles. When I started this journey, I hadn’t built anything in over a decade and the last time I was programming daily, I was still using inline styles and table tags.

Boilerplates are a crowded market. AI tool directories can easily turn into outdated noise. But I needed to build something real to properly stress-test Fabrk, and I kept running into the same discovery problem myself.

So this is where everything came together.

I’m Launching Today

This is v1. It’s rough around the edges.

I’m building in public and I genuinely want feedback what’s working, what’s not, and what’s missing. If there’s a prompt you need, better filtering you’d expect, or something in the UI that just doesn’t work for you, tell me.

This is only the second project I’ve built at this level of complexity, so go easy on me but don’t hold back. I’m here to learn and share.

Thanks