# Vibe Coding Tools

![Vibe Coding Tools](./homepage.png)

**Your go-to platform for vibe coders and AI development**

This massive collection gives you access to AI development resources, coding practices, and automation tools for modern software work. You get over **1,200 curated documents** that cover specialized AI agents and proven development practices!

## 🎯 What We Do

**Vibe Coding Tools** brings together AI development resources in one spot. We give **vibe coders** everything they need:

- **🤖 AI Development**: Agents, prompts, and configurations that make AI coding better
- **⚡ Ready Templates**: Templates, rules, and practices that work right away
- **🌐 One Platform**: Discover, generate, and contribute development tools
- **🔥 Community Built**: Made by developers who solve real problems

Solo developer or part of a team? Building something big? Vibe Coding Tools gives you what you need to code faster with AI help.

## 🗂️ What's Inside

| Directory | What It Does | Key Contents |
|-----------|--------------|-------------|
| **`/agents`** | AI Development Specialists | React pros, Vue specialists, API designers, CI/CD experts, test automation specialists, accessibility pros |
| **`/configs`** | Development Environment Setup | Claude Code, Cursor, GitHub Copilot configs; Next.js, React, Vue setups; AWS, Docker, Kubernetes configurations |
| **`/mcps`** | Model Context Protocols | GitHub, GitLab, Jira connections; AWS, Google Cloud, Azure integrations; PostgreSQL, MongoDB, Redis links |
| **`/rules`** | Coding Standards & Practices | Python, JavaScript, TypeScript rules; React, Vue, Angular frameworks; Clean code, SOLID principles |
| **`/templates`** | Project Templates & Scaffolds | Web apps, APIs, microservices templates; CI/CD pipelines; Clean architecture patterns |
| **`/tips`** | Development Productivity Tips | AI prompt writing techniques; Git strategies; Performance tuning; Security patterns |
| **`/tools`** | Development Tools Documentation | GitHub Copilot, Cursor guides; VS Code, IntelliJ setups; Code formatters, linters |

## 🚀 Getting Started

Ready to jump in? Here's how:

### For Developers
1. Browse the `/agents` directory for specialized AI assistants
2. Check `/configs` for your technology stack
3. Look through `/rules` for coding standards
4. Check out `/tips` for productivity boosts

### For AI Tool Setup
1. Copy agents from `/agents` into your AI coding assistant
2. Use configurations from `/configs` for your development stack
3. Import rules from `/rules` for automated code quality
4. Install MCPs from `/mcps` for extra capabilities

## 📝 Content Standards

We keep quality high with these rules:
- **Expert-level accuracy**: Every piece comes from specialists who know their stuff
- **Real-world focus**: We pick what works over what sounds good in theory
- **Code examples**: Working code snippets that show you the context
- **Same structure**: Standard formats across all content types
- **Fresh updates**: Content stays current with latest practices and tool versions

## 🤝 Contributing

Want to help out? We'd love your contributions! Pick one of these two ways:

### Option 1: Use the Platform (Recommended)

Use our **contribution system** right from the web app:

![Contribute Interface](share.png)

Here's how it works:

1. **Visit the Generate Page**: Go to `/generate` in the application
2. **Create with AI**: Use our content generator to make (on the /generate page):
   - Custom cursor rules and configurations
   - AI agents for specific development tasks
   - MCP server connections
   - Development templates and practices
3. **Generate Content**: Make high-quality, structured content with AI help
4. **Submit Form**: Submit your work using the `/contribute` form
5. **Manual Review**: Our team looks at and processes your submission by hand

### Option 2: Fork & Pull Request

Prefer the classic Git approach? Here you go:

1. **Fork the Repository**
   ```bash
   git clone https://github.com/yourusername/cursor-directory-clone.git
   cd cursor-directory-clone
   ```

2. **Create a Feature Branch**
   ```bash
   git checkout -b feature/your-contribution-name
   ```

3. **Add Your Content**
   - Put files in the right directory (`/agents`, `/configs`, `/mcps`, `/rules`, `/templates`, `/tips`, `/tools`)
   - Follow the file structure and naming that's already there
   - **MUST HAVE**: Include proper YAML frontmatter at the start of each `.md` file

   **Required YAML Frontmatter Example:**
   ```yaml
   ---
   title: "Your Content Title"
   description: "Brief description of what this does"
   category: "agents" # or configs, mcps, rules, templates, tips-tricks, tools
   tags: ["tag1", "tag2", "tag3"]
   tech_stack: ["react", "typescript"] # applicable technologies
   ---
   ```

   **Real Example:**
   ```yaml
   ---
   title: "Request API Security Best Practices"
   description: "Get secure API implementations with proper authentication and validation"
   category: "tips-tricks"
   tags: ["api", "security", "authentication", "validation", "jwt"]
   tech_stack: ["any"]
   ---
   ```

4. **Quality Standards**
   - **Expert-level technical accuracy**: Content should be production-ready
   - **Real-world focus**: Pick real use cases over theory
   - **Same formatting**: Follow existing markdown and YAML patterns
   - **Code examples**: Include working code snippets with context
   - **Right category**: Put content in the correct directory

5. **Submit Pull Request**
   ```bash
   git add .
   git commit -m "Add: [brief description of your contribution]"
   git push origin feature/your-contribution-name
   ```

6. **Review Process**
   - All contributions get **manually reviewed** by our team
   - We give feedback and suggestions for improvements
   - Accepted contributions get merged and deployed after human approval

### Community Guidelines

- 🎯 **Focus on Value**: Contribute content that genuinely improves developer productivity
- 🔄 **Iterate and Improve**: We encourage updates and improvements to existing content
- 📝 **Document Everything**: Include clear setup instructions and usage examples
- 🤝 **Collaborative Spirit**: Be open to feedback and suggestions from maintainers
- 🚀 **Stay Current**: Keep contributions updated with latest tools and practices

**Questions?** Open an issue or reach out through our community channels. We're here to help make your contribution successful!
