Built by developers
who wanted AI to work better.
Airuleshub is a central hub for AI coding rules. We help developers publish, discover, and install standardized AI rule configurations — so AI assistants behave consistently across every project and team.
It started with a frustration.
AI assistants were helping us move faster. But every project required rewriting the same rule files. Every team had their own version of .cursorrules. Every developer tweaked instructions slightly differently. There was no shared standard.
We kept asking: Why is there no central place to discover proven AI rule configurations?
What started as an internal way to share rules between colleagues turned into something bigger. That idea became Airuleshub.
Five developers, one shared frustration, one repo.
npx @airuleshub/cli ships to npm. Zero config required.
Rules become publicly discoverable and community-curated.
Developers publishing, discovering, and standardizing AI rules.
AI rules had no home.
The tooling for AI assistants evolved fast. The infrastructure for sharing what actually works — didn't. Rules were scattered, rewritten endlessly, and never standardized.
- ✕Scattered across private repositories with no discovery
- ✕Rewritten repeatedly by different teams doing the same work
- ✕Hard to find — no indexing, no search, no community
- ✕Difficult to standardize across projects and teammates
- ✕Not designed for reuse or version control
- ✕No CLI-first workflow for quick installation
One hub. Community-curated. CLI-first.
Airuleshub is a central hub for AI coding rules. It's built for real workflows — not experiments. We believe AI rules should be shareable, reusable, and community-driven.
Publish
Share your rule configurations with the community. Any format, any AI tool.
Discover
Find proven rule sets for your stack. Curated and upvoted by real developers.
Install via CLI
npx @airuleshub/cli@latest add <rule>. One command drops rules into your project.
Community Curated
Upvote what works. Surface the best configurations through collective signal.
Team Standardization
Share one rule URL across your team. No more duplicate configuration drift.
Reusable by Design
Rules are versioned, named, and linkable. Build on each other's work.
Install any rule directly into your project
Five developers. One shared tool.
We are five developers who work as colleagues. We care deeply about system design, developer tooling, clean workflows, and practical AI usage.
This project is fully bootstrapped. No venture backing. No growth-at-all-costs pressure. We're building tools we personally use — and improving them as we go.
- System design
- Developer tooling
- Clean workflows
- Practical AI usage
A few things we won't compromise on.
AI should assist developers, not control them. The developer stays in charge of every decision.
Standardization increases productivity. Shared conventions eliminate unnecessary debate.
Community curation leads to higher quality. Collective signal beats individual opinion.
Developer experience is not optional. Friction is a bug, not a feature.
Good tools reduce cognitive load. You should think about the problem — not the tooling.
We're just getting started.
Airuleshub is one step toward an ecosystem where AI rule standardization becomes as normal as dependency management. We see a future where the configuration of AI assistants is reproducible — not tribal knowledge.
Join the movement.
If you care about improving how AI works in development — explore existing rules, publish your own, install via CLI, and help define better standards. We're building this in the open.