WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Applies general coding standards and best practices for Java development, focusing on SOLID, DRY, KISS, and YAGNI principles, along with OWASP security guidelines.
A free, living knowledge base on vibe coding — building SaaS fast with AI agents, local AI, and agentic workflows.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Applies general coding standards and best practices for Java development, focusing on SOLID, DRY, KISS, and YAGNI principles, along with OWASP security guidelines.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Structure of GlobalExceptionHandler class.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Governs the structure and functionality of repository classes, emphasizing the use of JpaRepository, JPQL queries, and EntityGraphs to prevent N+1 problems.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Specifies standards for RestController classes, including API route mappings, HTTP method annotations, dependency injection, and error handling with ApiResponse and GlobalExceptionHandler.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Defines the structure and implementation of service classes, enforcing the use of interfaces, ServiceImpl classes, DTOs for data transfer, and transactional management.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Governs application logic design in Spring Boot projects, defining the roles and responsibilities of RestControllers, Services, Repositories, and DTOs.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for ensuring accessibility in Astro components, including semantic HTML and ARIA attributes.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for building and deploying Astro projects, including environment variable handling and CI/CD pipelines.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for Astro component development including proper composition and props.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for content management using Markdown and MDX files in Astro.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for data fetching in Astro using Astro.props, getStaticPaths(), and Astro.glob().
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
General rules and principles for developing with Astro framework.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for utilizing Astro integrations and plugins, configured in astro.config.mjs.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for performance optimization in Astro, emphasizing static generation and partial hydration.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Enforce the recommended Astro project structure.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for utilizing Astro's file-based routing system and dynamic routes.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for SEO and meta tag implementation in Astro using the tag and canonical URLs.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for styling in Astro using scoped styles, global styles, and CSS preprocessors.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Key coding conventions for Astro projects including style guide and typescript.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Performance metrics rules including Core Web Vitals, Lighthouse and WebPageTest.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Best practices for using Tailwind CSS within Astro components.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for integrating Tailwind CSS with Astro using @astrojs/tailwind.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for testing Astro projects, including unit tests and end-to-end testing.
WebDevPeterGriffin/The-VibeCode-Bible
Cursor rule Cursor
Rules for proper API usage within Chrome extensions, ensuring compatibility and best practices.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: