Add rules for vibe coding directories

[convertscout]

Adds rules.yaml and README for building/maintaining vibe coding resource directories with Cursor AI. Includes platform-specific customizations.

Summary by CodeRabbit

• New Features

  • Introduced Vibe Coding Directories resource for curating and automatically generating vibey coding content including rules, prompts, development tools, and platform-specific customizations.

• Documentation

  • Added detailed documentation with installation steps, usage workflows, and best practices for Vibe Coding Directories.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Adding a new "Vibe Coding Directories" feature with documentation and configuration. Includes a reference in the main README, a new directory structure with installation instructions, and a rules.yaml configuration file to guide Cursor AI in curating and generating coding resources across multiple platforms.

Changes

Cohort / File(s)	Summary
Main README update README.md	Adds new "Vibe Coding Directories" item under Directories section with link and descriptive subtitle
New feature directory rules/vibe-coding-resource-directories-cursorrules/.gitkeep, rules/vibe-coding-resource-directories-cursorrules/README.md, rules/vibe-coding-resource-directories-cursorrules/rules.yaml	Introduces new directory containing installation documentation, purpose/benefits overview, example workflow, and configuration rules for curating vibe coding resources (rules, prompts, MCP, news, jobs) with platform-specific customization and generation templates

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Area of note: The rules.yaml file contains descriptive guidelines and generation prompts that should be reviewed for clarity and alignment with project standards, though no complex logic is present.

Suggested reviewers

• PatrickJS

Poem

🐰 Hop, hop, directories now bloom,
Vibe coding resources in each room,
Cursor's companion, curating with flair,
Rules and prompts floating through the air!
What a delightful addition, I must say,
Let's code with vibes in every way! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add rules for vibe coding directories' directly and concisely describes the main change: introducing new rules configuration for vibe coding directories, which is the primary focus of all file additions in the PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fc2ce04 and 3674cd2.

📒 Files selected for processing (4)

• README.md (1 hunks)
• rules/vibe-coding-resource-directories-cursorrules/.gitkeep (1 hunks)
• rules/vibe-coding-resource-directories-cursorrules/README.md (1 hunks)
• rules/vibe-coding-resource-directories-cursorrules/rules.yaml (1 hunks)

🧰 Additional context used

📓 Path-based instructions (4)

**/*.md

📄 CodeRabbit inference engine (.cursorrules)

Always use Markdown for documentation and README files

Files:

• rules/vibe-coding-resource-directories-cursorrules/README.md
• README.md

rules/*/README.md

📄 CodeRabbit inference engine (.cursorrules)

rules/*/README.md: Refer to the README in each folder for guidance on naming conventions and descriptions
Each .cursorrules file may have an accompanying README.md file in its folder; use this README to provide credit to the original author and a brief description of the .cursorrules file's purpose

Files:

• rules/vibe-coding-resource-directories-cursorrules/README.md

**/*.{md,cursorrules}

📄 CodeRabbit inference engine (.cursorrules)

**/*.{md,cursorrules}: Use clear and concise language in all documentation and .cursorrules files
When adding examples or explanations, focus on practical use cases for Cursor AI users

Files:

• rules/vibe-coding-resource-directories-cursorrules/README.md
• README.md

README.md

📄 CodeRabbit inference engine (.cursorrules)

README.md: Maintain the existing structure of the README.md file
Maintain the following structure in the README.md file: 1. Title and Awesome badge 2. Logo 3. Short description 4. "Why .cursorrules?" section 5. Table of Contents 6. Rules section (with subcategories) 7. How to Use section 8. Contributing section 9. License section
Maintain alphabetical order within each category in the README.md file
Use consistent formatting for list items in the README.md file
Update the README.md file when adding new .cursorrules files, placing them in the correct category
Ensure all links in the README.md file are relative and correct
When updating the README.md, ensure the table of contents remains accurate
When adding new categories, update both the 'Contents' and 'Rules' sections of the README.md

Files:

• README.md

🪛 YAMLlint (1.37.1)

rules/vibe-coding-resource-directories-cursorrules/rules.yaml

[error] 6-6: syntax error: mapping values are not allowed here

(syntax)

🔇 Additional comments (4)

rules/vibe-coding-resource-directories-cursorrules/.gitkeep (1)

1-1: .gitkeep placeholder is fine. Keeps the directory tracked without adding behavior.

README.md (1)

290-294: Verify the directory link path.

The entry added to the Directories section uses the path rules/vibe-coding-resource-directories-cursorrules. Ensure this directory path exactly matches the new directory structure and that the link resolves correctly when viewed on GitHub.

rules/vibe-coding-resource-directories-cursorrules/README.md (1)

1-14: Documentation is clear, but verify credit attribution and example link.

The README follows good structure with clear sections. However, verify:

1. Credit line (line 14): Should [convertscout] include a GitHub profile link (e.g., [@convertscout](https://github.com/convertscout)) for consistency with other contributions in the repo?
2. Example URL (line 8): Confirm the link to https://lovabledirectory.site/ is accurate and will remain accessible.

Also ensure this README structure aligns with other folder READMEs in the rules/ directory.

rules/vibe-coding-resource-directories-cursorrules/rules.yaml (1)

1-26: Rename this file to .cursorrules or .md—it's not YAML configuration.

This file contains Markdown-formatted prose guidelines, not valid YAML. The .yaml extension is misleading. According to the README.md, this file should be copied as .cursorrules (a plain text format matching the rest of the repository) or renamed to .md if kept as documentation.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}