The Registry - Where AI Knowledge Lives
Discover, share, and manage packages for AI-assisted development
100+
Packages
10,000+
Downloads
500+
Community Members
For Individual Developers
Discover & Use
- Browse public packages
- Curated collections
- Search and filter capabilities
- Package details and documentation
Share Your Knowledge
- Publish under your namespace
- Version management
- Download analytics
- Community engagement
For Organizations
Private Registry Features
- Secure private packages
- Team member management
- Access control and permission
- Audit logs
Standardization Benefits
- Enforce coding standards
- Share internal best practices
- Onboard developers faster
- Maintain consistency across projects
Featured Collections
By framework
By purpose
By tool
Community picks
All frameworks
@nmux/rails
Rails best practices and conventions
@nmux/react
React patterns and hooks
@nmux/typescript
TypeScript configuration and types
@nmux/python
Python development workflows
@nmux/node
Node.js server patterns
@nmux/go
Go idioms and best practices
Getting Started
1
Create account
Sign up to publish and manage packages
2
Browse and search
Discover packages in the registry
3
Install via CLI
Use nmux CLI to install packages
4
Publish your own
Share your knowledge with the community
Registry FAQ
What types of packages can I find in the registry?
The nmux registry hosts packages for AI-assisted development including coding conventions, framework-specific best practices, testing patterns, and workflow configurations. Packages are organized by framework (Rails, React, etc.), purpose (testing, deployment), and AI tool.
How do I publish a package to the registry?
Create a mux.yaml manifest in your project, define your package metadata and instructions, then run nmux publish. You'll need to create an account and claim a namespace first. All packages go through basic validation before being published.
What's the difference between public and private packages?
Public packages are visible to everyone and can be installed by anyone. Private packages are only accessible to you or your organization members. Private packages require a paid plan and are ideal for proprietary coding standards and internal best practices.
How does package versioning work?
nmux uses semantic versioning (semver). When you publish updates, you specify major, minor, or patch version increments. Users can pin to specific versions, use ranges like ^1.0.0, or always get the latest with the 'latest' dist-tag.
Can I create an organization namespace?
Yes! Organizations can claim namespaces prefixed with @ (like @mycompany). Organization namespaces allow multiple team members to publish packages, manage access permissions, and maintain private registries for internal use.
How do I report a problematic package?
You can report packages that violate our guidelines by clicking the 'Report' button on any package page. We review all reports and take action on packages that contain malicious code, spam, or inappropriate content.
Install nmux CLI in 30 seconds
Installing and trying out nmux is fast and easy. Try now for free!