Skip to content
Prompt

Cursorrules-Database — Cursor Rules

by alpgul

AI Summary

Cursor Rules for Documentation establishes clear guidelines on where, when, and how to create project documentation, helping teams maintain organized, non-redundant docs in a `/docs` folder. Developers and technical leads benefit from standardized documentation practices that reduce clutter and improve code maintainability.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to add the "Cursorrules-Database — Cursor Rules" prompt rules to my project.
Repository: https://github.com/alpgul/Cursorrules-Database

Please read the repo to find the rules/prompt file, then:
1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type)
2. If there's an existing rules file, merge the new rules in rather than overwriting
3. Confirm what was added

Description

This application allows users to efficiently search and analyze code across various repositories. It integrates with CSV databases and automates processes using GitHub Actions, making it a powerful tool for developers.

Documentation Location

• All documentation files MUST be placed in the /docs folder • Never create markdown documentation files in the project root • Keep the root clean with only essential files (README.md, package.json, etc.)

When to Create Documentation

Documentation should be created and kept in source control ONLY if it meets these criteria:

✅ CREATE DOCUMENTATION FOR:

• Complex Integrations - Thirdweb, Supabase, external APIs • Architecture Decisions - Why certain approaches were chosen • Setup Guides - Required environment variables, configuration steps • User Guides - How end-users should use major features • Cross-Cutting Concerns - Authentication, caching, deployment • Known Gotchas - Issues that future developers will encounter (e.g., smart account auth)

❌ DO NOT CREATE DOCUMENTATION FOR:

• Simple Bug Fixes - These are documented in commit messages • Feature Implementation Details - Code should be self-documenting • Debugging Sessions - Temporary troubleshooting notes • Implementation Changelogs - Use git history instead • Duplicate Information - If it exists elsewhere, link to it • Prototype Summaries - Once feature is complete, document the final version only

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 3mo ago
Stale
AdoptionUnder 100 stars
1 ★ · Niche
DocsREADME + description
Well-documented

GitHub Signals

Stars1
Forks4
Issues0
Updated3mo ago
View on GitHub
No License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Any AI assistant that accepts custom rules or system prompts

Claude
ChatGPT
Cursor
Windsurf
Copilot
+ more